3 months ago
Hi Railway team,
I'm experiencing an issue with my backend deployment where it's stuck in the "deploying" state. The deployment has been running for over 7:21 minutes and appears to be in an infinite loop of mounting the same volume repeatedly.
Issue description:
The logs show continuous volume mounting attempts with the same path occurring every minute:
```
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/e795ad49-8e1d-43c9-b768-87f5ba5681f4/vol_52xq90xd05pkkvlg
```
This appears to be happening in a loop, with timestamps showing repeated mounting at 15:41:38, 15:42:12, 15:42:46, 15:43:22, etc.
Additional context:
- The previous deployment was working fine
- Last successful deployment was approximately 10 days ago
- No code changes were made, only added a few new collections in Strapi
- Nothing in the application configuration has changed
I've tried:
- Waiting for the deployment to complete (over 15 minutes)
- Checking for any changes that might affect storage/volumes
Has there been any change to how Railway handles volumes? Or is there a known issue with the volume mounting process currently?
Any help resolving this would be greatly appreciated!
```
Would you like me to modify anything about this message before you post it?5 Replies
3 months ago
it failed after a while:
............
h] sharing credentials for asia-southeast1.registry.rlwy.net
0ms
Apr 16 15:40:47
=== Successfully Built! ===
Apr 16 15:40:47
Run:
Apr 16 15:40:47
docker run -it asia-southeast1.registry.rlwy.net/cdcba971-268d-4c51-96c0-4d86cba926d5:511fd3a9-6bb7-4402-a790-a37af76a12da
Apr 16 15:40:47
Build time: 53.37 seconds
Apr 16 15:52:42
Apr 16 15:52:42
=========================
Apr 16 15:52:42
Container failed to start
Apr 16 15:52:42
=========================
Apr 16 15:52:42
Apr 16 15:52:42
Failed to start deployment.
Apr 16 15:52:42
If this error persists, please reach out to the Railway team at https://station.railway.com.
Apr 16 15:52:42
3 months ago
please help
3 months ago
No, this doesn't appear to be an issue with how Railway is mounting a volume. Did you happen to update your Strapi version?
Status changed to Awaiting User Response railway[bot] • 3 months ago
3 months ago
no, I didn't.
these are the build logs:
2 | "lockfileVersion": 1, ^ error: Unknown lockfile version at bun.lock:2:22 InvalidLockfileVersion: failed to parse lockfile: 'bun.lock' warn: Ignoring lockfile
Apr 16 19:22:26
Resolving dependencies
Apr 16 19:22:30
Resolved, downloaded and extracted [1644] warn: incorrect peer dependency "typescript@5.8.3"
Apr 16 19:22:46
Apr 16 19:22:46
+ @types/node@20.17.30 (v22.14.1 available)
Apr 16 19:22:46
+ @types/react@18.3.20 (v19.1.2 available) + @types/react-dom@18.3.6 (v19.
Apr 16 19:22:46
1.2 available)
Apr 16 19:22:46
+ typescript@5.8.3 + @strapi/plugin-cloud@5.12.1 + @strapi/plugin-users-permissions@5.12.1
Apr 16 19:22:46
+ @strapi/provider-upload-cloudinary@5.12.5 + @strapi/strapi@5.12.1 + better-sqlite3@11.3.0 + react@18.3.1 (v19.1.0 available) + react-dom@18.3.1 (v19.1.0 available) + react-router-dom@6.30.0 (v7.5.0 available)
Apr 16 19:22:46
+ styled-components@6.1.17
Apr 16 19:22:46
1256 packages installed [19.73s] Blocked 3 postinstalls. Run bun pm untrusted for details.
Apr 16 19:22:46
[stage-0 6/10] RUN --mount=type=cache,id=s/cdcba971-268d-4c51-96c0-4d86cba926d5-/root/bun,target=/root/.bun bun i --no-save 20s
Apr 16 19:22:46
[stage-0 7/10] COPY . /app/.
Apr 16 19:22:46
[stage-0 7/10] COPY . /app/. 354ms
Apr 16 19:22:46
[stage-0 8/10] RUN --mount=type=cache,id=s/cdcba971-268d-4c51-96c0-4d86cba926d5-node_modules/cache,target=/app/node_modules/.cache bun run build
Apr 16 19:22:46
$ strapi build
Apr 16 19:22:48
- Compiling TS
Apr 16 19:22:50
Compiling TS (1916ms)
Apr 16 19:22:50
- Building build context
Apr 16 19:22:50
Apr 16 19:22:50
[INFO] Including the following ENV variables as part of the JS bundle: - ADMIN_PATH - STRAPI_ADMIN_BACKEND_URL - STRAPI_TELEMETRY_DISABLED
Apr 16 19:22:50
Building build context (340ms)
Apr 16 19:22:50
- Building admin panel
Apr 16 19:22:50
Apr 16 19:23:12
Building admin panel (21849ms)
Apr 16 19:23:12
[stage-0 8/10] RUN --mount=type=cache,id=s/cdcba971-268d-4c51-96c0-4d86cba926d5-node_modules/cache,target=/app/node_modules/.cache bun run build 25s
Apr 16 19:23:12
[stage-0 9/10] RUN printf '\nPATH=/app/node_modules/.bin:$PATH' >> /root/.profile
Apr 16 19:23:12
[stage-0 9/10] RUN printf '\nPATH=/app/node_modules/.bin:$PATH' >> /root/.profile 92ms
Apr 16 19:23:12
[stage-0 10/10] COPY . /app
Apr 16 19:23:12
[stage-0 10/10] COPY . /app 70ms
Apr 16 19:23:21
[auth] sharing credentials for asia-southeast1.registry.rlwy.net
Apr 16 19:23:21
[auth] sharing credentials for asia-southeast1.registry.rlwy.net 0ms
Apr 16 19:23:25
=== Successfully Built! ===
Apr 16 19:23:25
Run:
Apr 16 19:23:25
docker run -it asia-southeast1.registry.rlwy.net/cdcba971-268d-4c51-96c0-4d86cba926d5:3d0de7c9-1fc9-4748-a7bf-20376115abfb
Apr 16 19:23:25
Build time: 60.09 seconds
Apr 16 20:54:21
Apr 16 20:54:21
=========================
Apr 16 20:54:21
Container failed to start
Apr 16 20:54:21
=========================
Apr 16 20:54:21
Apr 16 20:54:21
The container took too long to start.
Apr 16 20:54:21
If this error persists, please reach out to the Railway team at https://station.railway.com.
I don't see any information in the Deploy logs. Literally I don't have any hint or message to understand why this is happening
Status changed to Awaiting Railway Response railway[bot] • 3 months ago