2 years ago
Here's the issue we're facing:
I generated a template from our docker-compose.yaml file using https://railway.app/compose
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 🙂
26 Replies
Side note but our docker compose file is an abomination, lmk if you want to see that, or the generated template
2 years ago
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
2 years ago
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
2 years ago
are you selected on your team
2 years ago
are you the owner of the team
2 years ago
are you able to deploy other templates that you didn't create
i was able to deploy a version of this template with a few of the containers commented out, that's also worth noting
2 years ago
then I assume the compose file is generating a bad template
i do see the start command is misformed for some containers, but i wouldn't imagine that would cause a failure to deploy entirely
2 years ago
not the biggest loss, creating a project manually and following the platforms best practices is always going to result in a better outcome