a month ago
I'm reposting this question in English as requested.
We tested the original Codex CLI Linux sandbox inside a Railway Sandbox with the following configuration:
- Linux: 6.18.46-railway x86_64
- Codex CLI: 0.162.1
- Sandbox: 1 vCPU, 1 GB RAM
- networkIsolation: ISOLATED
Running:
codex sandbox linux --help
returned:
bwrap: No permissions to create a new namespace, likely because the kernel does not allow non-privileged user namespaces.
Could you please clarify:
-
Does Railway Sandbox support the user namespaces and bubblewrap functionality required by Codex's built-in Linux sandbox?
-
If supported, what configuration is required? We want to keep Codex's sandbox protections enabled, without using unrestricted execution or globally disabling security protections.
-
If Railway Sandbox does not support this, do Railway Cloud Agents support it? How do these environments differ regarding these permissions?
The disposable test sandbox and project have already been deleted. We are asking about compatibility before creating any new resources or repeating the test.
Thank you.
Pinned Solution
a month ago
Railway sandboxes are VMs, not containers. The issue was caused by a bug in a VMs setup. It is fixed now and codex sandbox should work.
2 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
Thank you for the explanation. We have not tried any further configuration changes, and the original issue remains unresolved. The disposable test sandbox and project were deleted after the failed check.
Our only confirmed diagnostic result is that codex sandbox linux --help returned:
bwrap: No permissions to create a new namespace, likely because the kernel does not allow non-privileged user namespaces.
We did not inspect the effective capabilities, seccomp policy, or AppArmor configuration, so the exact cause remains unverified.
Our requirement includes preventing agent-executed commands from accessing authentication credentials and controller data. Relying solely on the outer Railway boundary would require a design that also protects those resources from commands running inside it.
Could Railway confirm whether its Sandboxes support Codex's built-in bubblewrap sandbox without disabling its protections? If not, do Cloud Agents differ on this point, and what supported architecture would meet the separation requirement above?
a month ago
Railway sandboxes are VMs, not containers. The issue was caused by a bug in a VMs setup. It is fixed now and codex sandbox should work.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved brody • about 1 month ago