a month ago
I’m checking whether a standard Railway service supports non-root Chromium with its sandbox enabled.
A small isolated probe fails during browser launch, before rendering any page. The probe has been stopped; this is not a production outage.
Runtime:
- Playwright 1.62.1 with the official v1.62.1-noble image
- Node 24.21.0
- UID/GID 1001
- Chromium headless shell revision 1234 (package pin 151.0.7922.34; browser.version() was not reached)
- chromiumSandbox: true, with no --no-sandbox in the actual launch arguments
Error, with the timestamp removed:
FATAL:sandbox/linux/services/credentials.cc:131] Check failed: . : Permission denied (13)
Process exited: exitCode=null, signal=SIGTRAP
probe-fail: retry=false, sandboxDowngrade=false
The matching upstream source places this check in the new-user-namespace error path. Node host diagnostics reported Seccomp:2 and unprivileged_userns_clone=1, but I have no syscall trace or evidence identifying the denying host policy.
Does a standard Railway service support non-root CLONE_NEWUSER and sandbox-enabled Chromium in this runtime? If yes, which documented setting or platform-side correction addresses this denial while preserving least privilege?
Requirements exclude root browser execution, --no-sandbox, privileged mode, broad SYS_ADMIN capability, and seccomp=unconfined.
This is a platform compatibility and diagnosis question only. Please do not restart, redeploy, modify, or delete resources.
Reference: https://raw.githubusercontent.com/microsoft/playwright/v1.62.1/docs/src/docker.md
3 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 2 months ago
0x5b62656e5d
I’d look into using Railway Sandboxes instead.
a month ago
Thanks for the suggestion. Can you confirm whether Railway Sandboxes support Playwright Chromium running as a non-root user with chromiumSandbox: true and unprivileged user namespaces, without --no-sandbox, privileged mode, SYS_ADMIN, or unconfined seccomp? If supported, is there a recommended image or configuration? The docs position sandbox public URLs for previews and recommend normal services for production traffic; is a private, API-driven rendering worker an intended production use case? We have not started a new probe or changed the existing service.
li-chang-168
Thanks for the suggestion. Can you confirm whether Railway Sandboxes support Playwright Chromium running as a non-root user with chromiumSandbox: true and unprivileged user namespaces, without --no-sandbox, privileged mode, SYS_ADMIN, or unconfined seccomp? If supported, is there a recommended image or configuration? The docs position sandbox public URLs for previews and recommend normal services for production traffic; is a private, API-driven rendering worker an intended production use case? We have not started a new probe or changed the existing service.
a month ago
Can I ask what your use case is for the sandbox mode with the very specific requirements? If it's just about security why not just create a separate service that you just treat as untrusted? E.g.
Maybe I'm missing something though