Container failed to start

Hi, it seems the :latest tag on your image is causing a manifest error.

I was able to confirm this locally by attempting to pull the image: docker pull docker.io/brenthoover/wolf-server -> Error response from daemon: manifest for brenthoover/wolf-server:latest not found: manifest unknown: manifest unknown.

I'd suggest fixing the image, trying to pull it locally, and trying again.

Yes, because I do not use a latest tag, I use a tag based on the commit hash. I don't think I put in latest as a tag when I entered the DH image name

Could you add a tag ? We default to pulling latest unless specified.

Also, do you have any reason for not building your dockerfile on our build system ? this would solve your tagging issue and keep it linked between a commit->deploy.

Docs for this are here: https://docs.railway.app/guides/dockerfiles

I don't think I can build on your platform because my project includes both the client and the server and so the Dockerfiles are not at the root they are in server and client directories respectively.

Please check out the Docs Nico linked, they show you how to define a RAILWAY_DOCKERFILE_PATH variable for when you don't have the Dockerfile in the root.

That doc outlines how to use a non-standard path, but I don't see where it defines how I can build multiple docker images from a single project?

You would simply deploy multiple services for that, they would all deploy from the same GitHub repo.

Each service would have the applicable Dockerfile path set via that environment variable.

Ok, will take a look at that. For now just adding a 'latest' tag seemed to fix my issue and that fits better with my standard flow. Thanks