0 building with "builder-wS6v" instance using docker-container driver

1 [internal] load build definition from Dockerfile

1 transferring dockerfile: 910B done

1 DONE 0.0s

2 [auth] docker/dockerfile:pull token for registry-1.docker.io

2 DONE 0.0s

3 resolve image config for docker-image://docker.io/docker/dockerfile:1

3 ERROR: failed to authorize: failed to fetch oauth token: unexpected status from GET request to https://auth.docker.io/token?scope=repository%3Adocker%2Fdockerfile%3Apull&service=registry.docker.io: 401 Unauthorized

resolve image config for docker-image://docker.io/docker/dockerfile:1:

Dockerfile:1

1 | >>> # syntax=docker/dockerfile:1

2 |

3 | # Stage 1: Build the Go application

ERROR: failed to solve: failed to resolve source metadata for docker.io/docker/dockerfile:1: failed to authorize: failed to fetch oauth token: unexpected status from GET request to https://auth.docker.io/token?scope=repository%3Adocker%2Fdockerfile%3Apull&service=registry.docker.io: 401 Unauthorized

View Deploy details

ⓘ Deployment information is only viewable by project members and Railway employees.

Solved

6 Replies

brody

EMPLOYEE

a year ago

It seemed to be a minor issue with Dockerhub - we don’t see anything on the status page, but will keep monitoring.

Status changed to Awaiting User Response Railway • about 1 year ago

scalhoun

HOBBY

a year ago

I'm getting a similar error, assuming they are having issues:

ERROR: failed to solve: node:20.11.1-alpine: failed to resolve source metadata for docker.io/library/node:20.11.1-alpine: failed to authorize: failed to fetch oauth token: unexpected status from GET request to https://auth.docker.io/token?scope=repository%3Alibrary%2Fnode%3Apull&service=registry.docker.io: 401 Unauthorized