deploy docker image failing with no logs or build logs. Container build and runs fine locally
"No deployment logs. All output sent to stdout will be displayed here"
"No build logs associated with this deployment."
19 Replies
Project ID:
001efb46-b92f-4a5f-935d-49a81a52755ewhat docker image are you trying to deploy?
001efb46-b92f-4a5f-935d-49a81a52755e
Hey @Brody its a custom one I have on GHCR
I can see the download incrementing so it is pulling it from GHCR (as far as I can tell)
I just identified if I make up a GHCR image link it has the same exact outcome... So maybe it's not pulling the image correctly
Just found out only public images are supported at the time <:FacePalm_Picard:987023095690834041>
that was going to be my next question
unfortunately private images aren't supported yet
any reason you don't let railway build your project?
No major reason. Am I able to build the dockerfile, and deploy that image from there?
you have a Dockerfile in the root of your repo? then yes
https://docs.railway.app/deploy/dockerfiles
I'm testing with another image right now. What is the default port set for the image deploys?
is there a way to configure that?
not quite how it works, preferably the app would listen on the automatically generated
PORT variable, but if your app listens on a fixed port you can set it via a PORT service variableI tried this, no luck :/
Am I doing it incorrectly?
does the app listen on port 80?
image for reference
yes it does
expose doesnt mean the app listens on port 80
hardhat node --hostname 0.0.0.0 --port 80
I run it locally and its listening on port 80what is the script behind
run-node-live "run-node-live": "hardhat node --hostname 0.0.0.0 --port 80"
same as the one I posted above, sorry for the lack of context πchange 80 to
$PORT and remove the port service variable from railway@Brody same same π¦
OH wait its working now!
just took a second... Thanks for your help π
happy to help