Build Failing with Docker Error
andreirtaylor
PROOP

2 years ago

Region: us-west1]

=========================

Using Detected Dockerfile

=========================

context: fdd84a3538caeb414dce9055fa622aaf

#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

2 years 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 over 1 year ago


scalhoun
HOBBY

2 years 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


Status changed to Awaiting Railway Response Railway over 1 year ago


2 years ago

This time Dockerhub does have an issue - https://www.dockerstatus.com/


Status changed to Awaiting User Response Railway over 1 year ago


andreirtaylor
PROOP

2 years ago

I was able to deploy last night. I would consider this well resolved.


Status changed to Awaiting Railway Response Railway over 1 year ago


andreirtaylor
PROOP

2 years ago

Oh I guess there is a new incident. Close this as you see fit.


Yup, Docker having a not a great time. We'll keep you updated.


Status changed to Awaiting User Response Railway over 1 year ago


Status changed to Solved angelo-railway over 1 year ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...