getting 403 from docker hub thus railway build failing

a year ago

not sure if its due to docker hub being down or something?

0 Replies

a year ago

context: e44e11bcbcdb456854af44eea10f8e05

#0 building with "default" instance using docker driver



#1 [internal] load build definition from Dockerfile



#1 transferring dockerfile: 320B done

#1 DONE 0.0s



#2 [internal] load metadata for docker.io/oven/bun:latest



#2 ERROR: failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://auth.docker.io/token?scope=repository%3Aoven%2Fbun%3Apull&service=registry.docker.io: 503 Service Unavailable



-----

> [internal] load metadata for docker.io/oven/bun:latest:

-----



Dockerfile:1

-------------------

1 | >>> FROM oven/bun

2 |

3 |     WORKDIR /app

-------------------

ERROR: failed to solve: oven/bun: failed to resolve source metadata for docker.io/oven/bun:latest: failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://auth.docker.io/token?scope=repository%3Aoven%2Fbun%3Apull&service=registry.docker.io: 503 Service Unavailable

a year ago

is full error


a year ago

prev build worked for me, i didn't touch any tokens or anything in railway


a year ago

redeploy breaks too

1253472052246089700



a year ago

does railway use docker hub only for containers?


a year ago

i assume all builds are down for railway users?



getting 403 from docker hub thus railway build failing - Railway Help Station