#getting 403 from docker hub thus railway build failing

10 messages · Page 1 of 1 (latest)

cold heart
#

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

image.png
crude narwhalBOT
#

Project ID: N/A

cold heart
# 


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
#

is full error

#

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

#

redeploy breaks too

image.png
#

does railway use docker hub only for containers?

#

i assume all builds are down for railway users?

quasi mirage