Resolved by deleting the container and recreating it.
I thought I solved this by restarting xvfb? Might be something to do with a lingering pid or socket or something.
Steps to reproduce
Enable Modsync by setting USE_MODSYNC=true in container
Start up dedicated client container in detached mode (docker-compose up -d), and wait until it stabilizes (starts pinging /fika/dedicated/status)
Restart the container by docker-compose restart or similar. Do NOT stop the container, that doesn't seem to have the same effect
See that the X server stops becoming available, and the client fails to start with error Failed to create batchmode window: Success
Resolved by deleting the container and recreating it. I thought I solved this by restarting xvfb? Might be something to do with a lingering pid or socket or something.
Steps to reproduce
USE_MODSYNC=true
in containerdocker-compose up -d
), and wait until it stabilizes (starts pinging/fika/dedicated/status
)docker-compose restart
or similar. Do NOTstop
the container, that doesn't seem to have the same effectFailed to create batchmode window: Success