Same problem here.

Full build logs please - https://bookmarklets.up.railway.app/log-downloader/

There you go :)

Jul 22 16:59:45

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

Jul 22 16:59:45

Container failed to start

Jul 22 16:59:45

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

Jul 22 16:59:45

Jul 22 16:59:45

An unknown error occurred.

Jul 22 16:59:45

Jul 22 16:59:45

If this error persists, please reach out to the Railway team at https://help.railway.app.

Screenshot?

Excuses. check the updated message

I've cleared the cache on this thread and there is no attached files anywhere.

I copied the error logs here for you, attaching files isn't working for me now.=========================

Container failed to start

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

An unknown error occurred.

If this error persists, please reach out to the Railway team at https://help.railway.app.

Please use the bookmarklet.

I did so, and that was the result. Not very informative unfortunately.

If it helps, this is the deployment id: ea0f30f9-6389-4c8e-8c3b-101c04ea2e49

I'm sorry but are you saying the resulting .log file was only 5 log lines?

yes, this correct.

Are you on the V2 builder or V2 runtime?

I don't have the new builder enabled if that's your question. Don't really see the version

Are you getting the exact same error as they are?

yes

I tried both legacy and v2 runtime: same error. The builder is not shown.

Can you try deploying into a new service?

No success. same error

Is this happening to all your repos?

only this one, the only that tries to load a docker image from ghcr.io.

Are you able to share the repo?

Unfortunately, not. It is private.

Is the image that it tries to deploy private?

yes

So you have a Dockerfile with a FROM line and the image on the FROM line is private?

yes, the Dockerfile uses the FROM line to build the image and this image is stored in the GitHub registry in a private repository.

That would not be supported as there's currently no way to authenticate for that. You would need to deploy the private image directly and provide the authentication in the service settings.

I changed my repo to public but I still have the same error

That's not the issue, the issue is the private image on the FROM line, please read my previous message.

sorry, the FROM line does not use a private image because it uses eclipse-temurin:17-jrethis is my Dockerfile:FROM eclipse-temurin:17-jre WORKDIR /home/app COPY --link layers/libs /home/app/libs COPY --link layers/app /home/app/ COPY --link layers/resources /home/app/resources EXPOSE 8080 ENTRYPOINT ["java", "-jar", "/home/app/application.jar"]

@brody, in my case, there is no dockerfile to be built. It is simply a docker image hosted privately on ghcr.io . Fyi, the docker file of such image looks likeFROM continuumio/minicopnda3

WORKDIR /app

COPY environment.yml ./environment.yml

RUN conda env create -f environment.yml

# Make RUN commands use the new environment:

SHELL ["conda", "run", "-n", "files", "/bin/bash", "-c"]

COPY ./app/entrypoint.sh ./entrypoint.sh

COPY ./app ./app

# ENV FLASK_APP = "app"

EXPOSE 5000

RUN chmod +x ./entrypoint.sh

# The code to run when container is started:

ENTRYPOINT ["./entrypoint.sh"]

alvarin, how big is the image you are trying to deploy?

vladovsiychuk, similar question, how big is the image once built?

@brody, we are talking about an image size on disk of 1.74GB.

Could you try with a smaller image?

@brody, I fixed it. The token I used expired...replacing it with a new one worked. This was a waste of time. Can you guys be working on improving the error messages?

@alvarin, Which token and where did you set it up?

I've solved it. The image in the GitHub registry must be public, which can be set in the GitHub image settings. Otherwise, you need to set up an authorization token, but this is only available for the pro plan.