2 months ago
My whatsapp-service deployment keeps failing with a recurring builder infrastructure error that appears to be unrelated to my code or configuration.
The Error:
fsutil.NewFS(/var/lib/builder/build-sessions/1365b18a-d567-4f45-9334-7ea3ee4cfd28/snapshot-target-unpack/whatsapp-service): resolve : lstat ... no such file or directory
The builder successfully fetches the source snapshot but fails during the unpack process when trying to locate the rootDirectory.
Pattern: This error has recurred across at least 4 of the last 6 deployment attempts:
Deployment IDs with this error: 1365b18a, 1c86decb, 5ec1ead3, 683a4166, fa930941
A previous deployment (75b7ca64) succeeded with the identical rootDirectory and service configuration
Since the same source has built successfully before and my configuration hasn't changed, this appears to be an internal builder or infrastructure issue rather than a problem with my code, Dockerfile, or Railway configuration.
Service Details:
Service Name: tdis-whatsapp
Service ID: 4ea8c94f-4bec-4c24-b456-4a438bc59c2b
Project ID: a3385df3-0a34-437f-a9a8-0b140cbe5568
Environment ID: 27bf597f-baaa-47a5-beae-e5b6b923c525
rootDirectory: whatsapp-service
Build stage: BUILD_IMAGE
Can Railway investigate why the snapshot-unpack process is repeatedly failing for this service?
1 Replies
2 months ago
The latest deployment failed during the BUILD_IMAGE step in about 2 seconds, before any of your own build steps would have run, which rules out your application code and Dockerfile as the cause. The rootDirectory is set to whatsapp-service and your service configuration looks correct, consistent with the previous successful build you mentioned. We were not able to retrieve build logs for the failed deployment to narrow it further. Since the failure is intermittent and occurs in the builder's own snapshot-unpack path rather than in your build, retrying the deployment is worth trying if you have not already.
Status changed to Awaiting User Response Railway • about 2 months ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago