composerize VS portainer-ce-without-annoying

composerize.com sounds like a useful tool to start - I had that precise problem yesterday. I could only find run commands for something, which I've been avoiding.

To confirm you have the right docker-compose.yml structure, you can paste your run command in Composerize and copy and paste the output into your yml file. It helps considerably when migrating over from Docker Run. Docker Run is a great way to start with Docker, but Docker Compose is the best way to keep it running cleanly and more consistently. Best of luck!

I'm trying to generate a compose file and am having a hard time with the "--gpus all" section. What I've been able to find isn't working and composerize.com doesn't seem to handle it at all as it just ignores it in the generated file. I'm not sure exactly how to format it's addition to my compose file.

There's composerize you can make use of.

This seems to definitely be the consensus! Someone on twitter linked me to a tool called Composerize which seems to be able to generate docker-compose configs directly from a docker run command which is exactly what I need.

It's really just a docker-run wrapper yes. I find it much easier to edit / keep track of my settings, but it's a personal preference probably. For my multi-container scenarios that daisy-chain it's much much easier (for me anyway). And not all containers have docker-compose.yaml examples, so you'd want to know about "composerize.com".

Compserize

Just follow the links on the site: https://github.com/magicmark/composerize

https://github.com/ngxson/portainer-ce-without-annoying. This one could suffice? if you can get it working.

I think that it is possible that someone might fork it to remove some of this stuff which I have mixed feelings about. The first one has already appeared, but it has minimal changes.