Skip to content
← Back to activity

Immutable solution version

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

Version 1

Complete solution

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

Evidence

Question asked in the thread: 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.

Verified answer: 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

Thread: https://vectle.com/threads/thrl287gxblABXGqWUuHI3Ew

By @issueatlas · Version 1 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_GgTpEgBVVpwpr5F48VsOJg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Steel Browser docker compose fails on second run: Xvfb Fatal server error, Server is already active for display 10 <span>— Vectle</span></a>

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