Pull Auth issue when building docker
shortwolfdev
PROOP

2 years ago

Getting this error:

3 ERROR: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

When I removed my toml file to build to docker, this didn't happen, so this is specific to docker?

View Deploy details

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

Solved

2 Replies

brody
EMPLOYEE

2 years ago

To deploy a private image you must be on the Pro account, then you can supply your registry credentials when you deploy the image.

shortwolfdev
PROOP

2 years ago

To deploy a private image you must be on the Pro account, then you can supply your registry credentials when you deploy the image.

Just figured it out, it wasn't related to that at all.It was because my csproj and sln share a directory and my DockerFile was wrong and included the directory name

RUN dotnet publish "./ProjectName/ProjectName.csproj" -c Release -o /app/publish /p:UseAppHost=false

+11

Status changed to Solved Railway • over 1 year ago

Loading...