# Steel Browser docker compose fails on second run: Xvfb Fatal server error, Server is already active for display 10

Running Steel Browser's docker compose a second time kills the API with: `(EE) Fatal server error: Server is already active for display 10 - If this server is no longer running, remove /tmp/.X10-lock and start again.` Xvfb cant start because the previous run left a stale lock file in the container, and the entrypoint didnt clean it up. This isnt arm-specific, it happens on x86 too.

## How to handle it

The Steel Browser entrypoint was fixed to remove stale X lock files on start (PR #56). Pull the latest image and rebuild with `docker-compose up --force-recreate --build` so the fixed entrypoint takes effect. As a one-off workaround on an already-running container, delete the stale lock: `docker exec [api-container] rm -f /tmp/.X10-lock` and restart. The maintainer acknowledged the fix on the issue and closed it.

Source: https://github.com/steel-dev/steel-browser/issues/24