Skip to content
Supported executor contract for a one-shot Linux qualification
btheorystartups
OP

a month ago

We are assessing Railway Sandboxes for a short, credential-free Linux qualification before a separate private database proof. No sandbox has been provisioned for this work. We inspected the public railway SDK 3.16.0 source at commit 97fdb4f61d351319d5633c2c92a86ca2ff0062d8.

Could you identify the supported platform/API contract for:

  1. Your June 12 changelog documents Docker inside Sandbox VMs. Is a root helper inside that guest supported in creating one private cgroup v2 domain subtree, setting/read-back of CPU/memory/PID limits, dropping its fixture child to an unprivileged UID, installing seccomp and terminating the subtree with cgroup.kill, without host permission changes?
  2. Immutable guest image/checkpoint identity, known kernel/libc/Python versions, and a read-only artifact mount with a supported guarantee against alternate writers. Is there an immutable image/checkpoint identifier, rather than a replaceable name or build recipe alone?
  3. An independently enforced absolute VM lifetime that remains effective if the controller disconnects or a command creates descendants outside its process group. Which destroy/status contract confirms the entire exact VM is terminal?
  4. Recovery from a lost create response without creating another VM: supported idempotency or request identity and a bounded way to identify/stop only that attempt.
  5. A command transport that can disable automatic reconnects/legacy fallback, bound setup and response bytes, and use narrowly scoped external controller credentials. These credentials must stay outside the guest fixture.

Documentation links or supported API details are sufficient. We do not want resources provisioned, account settings changed or privileges enabled as part of this inquiry.

$10 Bounty

1 Reply

Status changed to Awaiting Railway Response Railway • about 1 month ago


Railway
BOT

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


dreamalchemy

a month ago

Finding: Railway exposes useful primitives, but I cannot verify a supported public contract satisfying all five mandatory requirements. Two of them—absolute VM lifetime and exactly-once creation recovery—remain critical blockers.

  1. Guest cgroup v2 and seccomp

Docker is preinstalled in Railway Sandbox VMs, making an inner-container executor a plausible approach.

However, Docker support does not establish writable cgroup v2 delegation for a guest-local root helper.

The required confirmation is that an authorized helper can create its own domain subtree, enable and read back "cpu", "memory", and "pids" controllers, move the child into that subtree, and terminate it using "cgroup.kill", without requiring additional host privileges.

Non-root execution with "no_new_privs" and seccomp can be provided by an appropriately configured Docker container, but that alone does not prove the requested direct cgroup contract.

Status: not certified by the public documentation.

  1. Immutable identity and artifacts

The Railway CLI documents "--base-image-digest" for template builds. This is useful for pinning a base image.

The TypeScript SDK v3.16.0 template interface does not expose an equivalent option in the public types inspected.

Named checkpoints are replaceable; recapturing under an existing name overwrites the stored checkpoint.

A pinned base-image digest does not, by itself, guarantee an unchanged VM kernel, libc/Python versions, or immutable artifact mounts across fresh boots.

Status: partial image reproducibility, but the full identity and artifact guarantees remain unconfirmed.

  1. Independent absolute VM lifetime

The documented "idleTimeoutMinutes" is activity-based. Active sessions and heartbeats can defer destruction. Hobby and Pro plans may disable idle expiration altogether.

"exec" timeouts terminate the command's process group, not the complete VM.

An external watchdog is useful for cleanup but does not satisfy a requirement that destruction remain guaranteed when that controller disconnects.

Status: no documented platform-enforced absolute maximum VM lifetime found. Blocking.

  1. Recovery from a lost creation response

The SDK supports "Sandbox.list()", "Sandbox.connect(id)", and explicit destruction.

The public "sandboxCreate" path in "src/sandbox/engine.ts" does not expose an idempotency key or caller-assigned creation ID.

A timeout after receiving the sandbox ID is recoverable using that ID. Losing the initial create response before obtaining an ID is different: listing can help reconcile resources, but does not establish exact-attempt recovery.

Status: no documented exactly-once creation contract found. Blocking.

  1. Transport and bounded execution

For one-shot operations, I would specifically evaluate "sandbox.execHttp()" rather than WebSocket "exec".

"execHttp" uses a single GraphQL HTTPS request, without WebSocket negotiation or the SDK's WebSocket legacy-fallback behavior. It has a server-side execution timeout (two minutes by default, ten minutes maximum) and caps each output stream at 16,000 bytes.

It does not provide stdin, streaming, or direct cancellation. Client-side HTTP request timeouts and server-side command termination must also be treated separately.

The Railway API credential can be retained exclusively by the external controller. Whether the required narrow permission scope is available still needs confirmation.

Status: a promising supported alternative for a bounded one-shot command, subject to those limitations.

Qualification decision

I would currently return NOT QUALIFIED against the full mandatory contract, rather than weakening any requirement or claiming undocumented guarantees.

The two highest-priority questions for Railway engineering are:

  1. Is there a supported platform-enforced absolute VM expiration that remains effective independently of controller connectivity and guest activity?
  2. Is there a supported idempotency key or exact-attempt recovery mechanism for "sandboxCreate" when the initial response is lost?

After those, confirmation of cgroup delegation, immutable guest provenance, read-only artifact mounting, and the required credential permissions would determine whether qualification can proceed.

References:

Disclosure: AI-assisted technical research. The conclusions are based on public documentation and source-code inspection; no live Sandbox or platform-internal compatibility test has been performed.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...