Railpack Build Error
jwaltz
PROOP

a year ago

Had a Railpack-based build error that I wanted to report. It ended up being a one-off as I was able to successfully deploy using the "redeploy" option but wanted to report it:

[Region: us-west1]



╭─────────────────╮

│ Railpack 0.0.56 │

╰─────────────────╯



↳ Detected Node

↳ Using bun package manager



Packages

──────────

bun  │  1.2.5  │  railpack default (latest)



Steps

──────────

▸ install

$ bun install --frozen-lockfile



▸ build

$ bun run build



Deploy

──────────

$ bun run start





Successfully prepared Railpack plan for build





context: h4rp-i

[internal] load build definition from railpack-plan.json

[internal] load build definition from railpack-plan.json  ✔ 0ms

[internal] load build definition from railpack-plan.json

[internal] load build definition from railpack-plan.json  ✔ 7ms

resolve image config for docker-image://ghcr.io/railwayapp/railpack-frontend:v0.0.56

✕ resolve image config for docker-image://ghcr.io/railwayapp/railpack-frontend:v0.0.56 
failed to do request: Head "https://ghcr.io/v2/railwayapp/railpack-frontend/manifests/v0.0.56": dial tcp: lookup ghcr.io on 169.254.169.254:53: read udp 172.17.0.3:38355->169.254.169.254:53: i/o timeout


ERROR: failed to solve: failed with build-arg:BUILDKIT_SYNTAX = ghcr.io/railwayapp/railpack-frontend:v0.0.56: failed to resolve source metadata for ghcr.io/railwayapp/railpack-frontend:v0.0.56: failed to do request: Head "https://ghcr.io/v2/railwayapp/railpack-frontend/manifests/v0.0.56";: dial tcp: lookup ghcr.io on 169.254.169.254:53: read udp 172.17.0.3:38355->169.254.169.254:53: i/o timeout

Thanks

1 Replies

jwaltz
PROOP

a year ago

7440ea60-c734-47cc-ba5d-e8cabf480488\


Loading...