Clem c736d5863b fix(docker): give each VNC node its own X display ...

When a project is opened, Docker nodes are created in parallel. The free
display was found by checking whether /tmp/.X11-unix/X<n> exists, but that
socket only appears once Xvnc has started, so several nodes got the same
display. Only the first Xvnc started; the others exited with "Server is
already active for display N" ("The vnc process has stopped with return
code 1"), and their containers drew on the screen of another node.

- reserve the displays given to the nodes of this server, and also skip a
  display whose lock file belongs to a live process
- restart a crashed Xvnc on the display the container was created with,
  after removing its stale socket, instead of picking a new display the
  container cannot reach (black screen)
- on close, only remove the X socket of our own Xvnc, never the socket of
  the node that owns the display

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-16 09:29:19 +02:00

..

test_docker_kernel_datapath.py

style: apply ruff format to the files this branch touches

2026-10-14 22:13:58 +08:00

test_docker_vm.py

fix(docker): give each VNC node its own X display

2026-10-16 09:29:19 +02:00

test_docker.py

fix(docker): accept the pinned image id when the stores report different ids

2026-10-13 17:10:17 +08:00

test_iol_docker_kernel_datapath.py

test: cover the kernel-datapath review fixes

2026-10-06 19:55:31 +08:00

test_iol_docker_vm.py

feat(iol): anchor IOL runner containers on persistent TAPs

2026-10-06 00:21:09 +08:00

test_vendor_docker_vm.py

fix: repair imports lost in the 3.1 rebase and meet the new lint baseline

2026-10-06 00:21:11 +08:00