[Region: us-west1]

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

Using Detected Dockerfile

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

context: 90e90d5c0249ad88a5ac0ae09c252279

0 building with "builder-6Zn7" instance using docker-container driver

1 [internal] load build definition from Dockerfile.prod

1 transferring dockerfile: 812B done

1 DONE 0.0s

2 [internal] load metadata for docker.io/library/python:3.11-slim-buster

2 …

3 [auth] library/python:pull token for registry-1.docker.io

3 DONE 0.0s

2 [internal] load metadata for docker.io/library/python:3.11-slim-buster

2 ERROR: failed to authorize: failed to fetch oauth token: Post "https://[auth.docker.io](auth.docker.io)/token";: dial tcp: lookup auth.docker.io on 127.0.0.53:53: server misbehaving

[internal] load metadata for docker.io/library/python:3.11-slim-buster:

Dockerfile.prod:1

1 | >>> FROM python:3.11-slim-buster

2 |

3 | RUN apt-get update && \

ERROR: failed to solve: python:3.11-slim-buster: failed to resolve source metadata for docker.io/library/python:3.11-slim-buster: failed to authorize: failed to fetch oauth token: Post "https://[auth.docker.io](auth.docker.io)/token";: dial tcp: lookup auth.docker.io on 127.0.0.53:53: server misbehaving

View Deploy details

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