2 months ago
Docker layer caching issue: GitHub has updated entrypoint.sh but Railway is still running the old cached version. Need force rebuild or cache clear. 24+ hours troubleshooting.
- Service: FlowiseAI-Railway
- Repo: leonardosilveriovera-source/Flowise-teste
- Issue: Old entrypoint.sh still executing despite GitHub update
3 Replies
2 months ago
The Dockerfile change didn't trigger a rebuild yet. Contact Railway Support immediately through the Help Station chat. This needs their direct intervention to clear the Docker cache.
Tell them the deployment ID: 435bb1c1-bac0-4cf7-88ca-8ef6beceb1ad
They can force a full rebuild from their backend, which is the only way to bypass this cache issue at this point.
2 months ago
We don't manually clear Docker build caches from the backend. You can force a full rebuild without cache by setting the environment variable NO_CACHE=1 in your service variables, then triggering a new deployment.
That said, your latest deployment did pick up your updated entrypoint.sh — it rebuilt with your latest commit and produced a new image, so the caching wouldn't be the issue.
It looks like there's a runtime error — your app is crashing because Flowise tries to create /data/flowise/logs but the logs subdirectory doesn't exist inside your volume yet.
Your entrypoint.sh should create the required directories before starting Flowise mkdir -p /data/flowise/logs
Best,
The Railway Team
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
It is working how. Thanks!
Status changed to Awaiting Railway Response Railway • 2 months ago
Status changed to Solved leonardosilveriovera-source • 2 months ago