a month ago
My service (bank) keeps serving a stale Docker image. New commits on main are fetched with the correct SHA, but the built image never contains the new code.
Build logs show only 2 lines — "scheduling build on Metal builder" and "image push" — with NO npm run build output at all. A working earlier build showed "Generating static pages (66/66)", so the build step is simply not re-running; a pre-built image is being reused.
Things I already tried, all with no effect:
- Multiple empty commits to retrigger auto-deploy
- Adding a cache-bust file (build-nonce.txt) COPYed before COPY . .
- Disconnecting and reconnecting the GitHub source
- Setting dockerfilePath to ./Dockerfile (my repo has a Dockerfile)
- Setting nixpacksConfigPath to null
Despite setting dockerfilePath, the deployment info still shows "builder":"RAILPACK" — the explicit Dockerfile config is being ignored.
Please clear the build cache for this service at the infrastructure level and confirm which builder is actually used. Project ID: 4021ca4d-e952-4755-a7c3-a85f2adb8d9b
Repo: github.com/iloveelsa528-png/bank (branch main)
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 1 month ago
a month ago
Try setting the builder to Dockerfile in the service settings, then press Cmd/Ctrl + K and deploy latest commit.
a month ago
Update — this is not a cache issue, and I've now hit a hard wall.
Current state: every deploy fails with "Railway can't access iloveelsa528-png/bank. Reconnect the GitHub repository under Service Settings → Source, or reinstall the Railway GitHub App and grant it access to this repo."
But the Railway GitHub App IS installed on my GitHub account with "All repositories" access, and the Railway dashboard shows the repo connected (iloveelsa528-png/bank, branch main, auto-deploy on, no error shown in Settings). So GitHub says access is granted, Railway says it can't access.
Before this, the symptom was different but equally broken: deploys reported "successful" while serving a stale image. Evidence:
- Three independent deployments (original project, a new service, and a brand-new project) ALL produced byte-identical output: turbopack runtime chunk
turbopack-1f1e3yddbhtmz.js, none containing my new code. - A clean local build (rm -rf .next, fresh npm run build) of the same commit produces
turbopack-0_fl1_2monou4.jsand DOES contain the new code. - Separate projects cannot share a build cache, so Railway was fetching a source that isn't origin/main.
- Verified via
git show origin/main:src/app/grammar/page.tsxand on github.com: main contains the new code. - An earlier ACTIVE deployment showed commit 3c40e335, which does not exist in my repo at all (orphan).
Things I've tried, none of which changed the served output: empty commits, a cache-bust file COPYed before COPY . ., a FORCE_REBUILD file merged via PR to change the commit SHA, disconnect/reconnect the GitHub source, explicit Dockerfile builder + dockerfilePath, nixpacksConfigPath null, new service, new project, uninstall/reinstall the GitHub App, Suspend/Unsuspend.
Also: my repo has NO webhooks at all under Settings → Webhooks (github.com/iloveelsa528-png/bank/settings/hooks is empty), and I stopped receiving push notifications at some point.
Please look at this from your side. Project (new): balanced-gentleness. Original project ID: 4021ca4d-e952-4755-a7c3-a85f2adb8d9b. Repo: github.com/iloveelsa528-png/bank, branch main (current tip contains the code).
a month ago
Resolved on my end — this turned out not to be a Railway issue.
The code was deploying correctly the whole time; the UI element I was
looking for was rendering inside a collapsed section on the page.
No action needed from anyone. Closing this out — thanks!
Status changed to Solved 0x5b62656e5d • 7 days ago