Skip to content
Builder change recorded as applied, but dashboard and serviceInstance still show Railpack
novanehk
OP

34 minutes ago

Please help investigate a Streamlit builder configuration discrepancy. Please do not change configuration or deploy any service.

Observed sequence:

  1. We staged exactly one setting: Builder RAILPACK -> DOCKERFILE. The existing RAILWAY_DOCKERFILE_PATH variable is Dockerfile.streamlit.
  2. We called environmentPatchCommitStaged once with skipDeploys=true. CLI exit was 0 and the mutation data field was present; the scalar response value was not retained.
  3. Environment history records the patch as applied on November 17, 2026 at 17:40:51 UTC. Its dashboard detail explicitly shows Builder RAILPACK -> DOCKERFILE under "1 change applied".
  4. After refreshing, Settings still shows Railpack. An environment-specific serviceInstance query also returns builder=RAILPACK and dockerfilePath=null.
  5. No staged changes remain, autodeploy is disabled, and the deployment list did not change. Streamlit remains offline; our API and Cockpit services are online and must remain untouched.

Questions:

  • Does skipDeploys=true defer updating serviceInstance build fields until a later deployment, or is this an apply/readback discrepancy?
  • What supported non-deploying method can confirm or correct only the committed builder and Dockerfile path?

We have not repeated the mutation or staged the change again. We are avoiding retrieval of the entire EnvironmentConfig or patch body because they may contain variable values.

We can provide project, environment, service and patch IDs privately to Railway staff. Our target is a two-user beta on November 18 at 15:00 CET. Please advise on the minimal safe next step. No credentials, connection strings or raw logs are included.

Awaiting Railway Response

2 Replies

Railway
BOT

32 minutes ago

Our read of the Streamlit service's current configuration matches what you're seeing: the committed builder is Railpack, so the Dockerfile builder change is not in effect on that service right now, even though the environment history records it as applied.

We can't confirm that skipDeploys=true defers the builder change to a later deployment, so a deploy from the current state would build with the Railpack configuration committed today. Your RAILWAY_DOCKERFILE_PATH variable is still the documented way to point a Dockerfile build at Dockerfile.streamlit (Dockerfiles), but it only applies once the builder itself reads Dockerfile.

Before relying on a re-apply for the beta, we'd recommend validating the builder change in an isolated test environment first, so your API and Cockpit services stay untouched.


Status changed to Awaiting User Response Railway • 32 minutes ago


novanehk
OP

30 minutes ago

The issue remains unresolved. Please escalate to a Railway engineer. We need to understand why the patch records Builder RAILPACK -> DOCKERFILE as applied while the committed configuration remains Railpack. Please provide a concrete, supported way to save this setting without deployment. We do not authorize infrastructure changes or deployments.


Status changed to Awaiting Railway Response Railway • 30 minutes ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...