a year ago
This worked perfectly about a week ago, came back to deploy due to Magic Ports (super pumped btw!):
docker run -p 443:443 -p 30303:30303 go-marscredit:latest
Using a custom Dockerfile and entrypoint_node1.sh file. App deploys fine without custom run command, but never officially starts.
=========================
Container failed to start
=========================
crun: executable file docker not found in $PATH: No such file or directory: OCI runtime attempted to invoke a command that was not foundⓘ Deployment information is only viewable by project members and Railway employees.
4 Replies
a year ago
Please close! By removing the run command I was able to deploy the app with zero issues! Coding issue.
a year ago
Actually, may still need some help. I need to map the volume to the app data folder for consistent data storage, and I did this in the past using the run command. Will continue to test.
a year ago
docker run would have never worked as a custom start command, Railway has never allowed you to directly modify the docker command that gets ran internally.
Mount the volume to your desired location, this is not something you do via commands.
Status changed to Solved railway[bot] • 12 months ago
a year ago
Copy. Thank you @Brody. I may not remember my setup correctly.
The app is now running great, I'm now trying to understand the magic ports! I will create another thread.
FYI - You guys are so fast to respond. Much appreciated.
