Deployment Fails after Import from docker-compose
Here's the issue we're facing:
1. I generated a template from our docker-compose.yaml file using https://railway.app/compose
2. I try to deploy using the generated template, but it gives me the message: "Oh No! Looks like something went wrong and the train derailed" (see attached image)
Side note: it was very hard to bring our docker-compose.yaml file up to compliance with the template generator. Many compose features seem not to be supported, and the error messages were not helpful so I had to bruteforce the issues (essentially) until I got us deploying. That's not currently an issue, but it would be good to see better user feedback π
Solution:Jump to solution
not the biggest loss, creating a project manually and following the platforms best practices is always going to result in a better outcome
17 Replies
Project ID:
e5f23f8e-350c-4346-92c3-a62744516ef3e5f23f8e-350c-4346-92c3-a62744516ef3
Side note but our docker compose file is an abomination, lmk if you want to see that, or the generated template
I want to see both, though personally I would always create a template manually because a compose file will never follow the best practices of what a template should be
k sec
and your train derail issue is because you are on a limited trial because your GitHub account wasn't verifiable, you would need to be on a paid plan
oh?
i upgraded us though
and i'm oauth'd in from github
let me check our plans just to make sure
yeah, we're definitely on the pro plan for the team
hmm... unless it's not deploying the template under our team...
are you selected on your team
appears so
and the template itself is owned by the team
are you the owner of the team
I created the account, let's see though
(and the team)
yup, i'm an owner
are you able to deploy other templates that you didn't create
trying now
i was able to deploy a version of this template with a few of the containers commented out, that's also worth noting
yup, i can deploy public templates
then I assume the compose file is generating a bad template
hmm, yeah maybe it relates just to these containers i added back in
i do see the start command is misformed for some containers, but i wouldn't imagine that would cause a failure to deploy entirely
Solution
not the biggest loss, creating a project manually and following the platforms best practices is always going to result in a better outcome