Chromium sandbox fails with Permission denied

luisacev

HOBBYOP

25 days ago

Hi Railway team,

I’m trying to run Chromium with Playwright as a non-root user (UID 1000), with the browser sandbox enabled. It exits at startup, even when opening only about:blank, with:

FATAL:sandbox/linux/services/credentials.cc:131 — Permission denied (13)

Running unshare -U true as the same user also returns Permission denied.

Is there a supported Railway configuration that allows Chromium’s sandbox to work? I’d like to keep it enabled rather than use --no-sandbox.

Thanks for your help!

$10 Bounty

2 Replies

Railway

BOT

25 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • 25 days ago

darseen

HOBBYTop 5% Contributor

25 days ago

Try to set the variable RAILWAY_RUN_UID=0, it should run the main process as root.

luisacev

HOBBYOP

25 days ago

Thanks for the suggestion! Would RAILWAY_RUN_UID=0 let Chromium run with its sandbox still enabled, or would it require --no-sandbox? If it requires disabling it, is there a supported way to keep the browser sandbox enabled on Railway?

Welcome!