a month ago
Issues with builds.
I've seen this issue come up a bunch of times in regards to like the loading secrets and the failure of loading secrets. I don't think this is something in my control.
I have been able to get around this at once by switching from the new Rail pack to the old one.
load build definition from railpack-plan.json
0s
Jun 30 19:44:29
[railpack] secrets hash
0s
Jun 30 19:44:29
[railpack] loading secrets
failed to authorize: Canceled: context canceled: context canceled
0s
Jun 30 19:44:29
loading .
rpc error: code = Canceled desc = rpc error: code = Canceled desc = context canceled: context canceled
0s
Jun 30 19:44:29
docker-image://ghcr.io/railwayapp/railpack-builder:latest
0s
Jun 30 19:44:29
docker-image://ghcr.io/railwayapp/railpack-runtime:latest
Cached
Jun 30 19:44:30
[auth] library/alpine:pull token for registry-1.docker.io
0s
Jun 30 19:44:30
mkdir /etc/mise
Cached
Jun 30 19:44:30
create mise config
0s
Jun 30 19:44:30
install mise packages: node
secret DISABLE_BACKGROUND_PROCESSES: not found
0s
Jun 30 19:44:30
copy /mise/shims
mount callback failed on /tmp/containerd-mount2535588047: context canceled: context canceled
2 Replies
a month ago
Hi there, I saw you are still on Railpack so tried redeploying the latest commit to see if we could reproduce this.
How often are you seeing this error pop up? Is it every time you use the Railpack builder?
I just re-deployed your latest commit and the build seems to have crossed that stage (broke at application logic in src/components/inbound/inbound.service.ts which you may already be aware of).
Could you please give us any steps to recreate this on our end and the frequency that you are running into this so our team can investigate the issue?
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
We've recently fixed a race with Railpack where there was a rare chance Buildkit would fail to mount the secret properly if you add environment variables prefixed with NODE. This is the PR if interested. The fix is now live so you shouldn't see the error anymore. If you do, please reach out to us again.
Status changed to Solved jr • 27 days ago