docker-autocompose VS runlike

But there is this little tool docker-autocompose that can read the configuration of your current containers and export that into a docker-compose.yml. It probably wont work 100% perfect for every possible container config, but its worth a try and it might save a lot of time when making the switch from run to compose. Good luck!

You can try to use docker-autocompose to read the configs of your currently deployed containers and write them into a compose file for you.

There are different registries, Docker Hub, Quay (quay.io), GitHub (ghcr.io), Linuxserver (lscr.io). Then there is the image name and then the tag (//:; for example lscr.io/linuxserver/plex:latest). The tag and the registry won't matter too much for you (tag I guess you use latest), because most maintainers like Linuxserver push the same image to different registries. So it doesn't really matter if you use lscr.io/linuxserver/plex:latest or just linuxserver/plex:latest or ghcr.io/linuxserver/plex:latest. What does matter is if you use the linxserver or the plexinc image. If you run docker container ls in your terminal, you can see which image you are using. You could then run docker container inspect to get a json config of your plex container and volume mounts etc. to use that to create a docker compose file for it. There are also tools that do that automatically for you, like this: https://github.com/Red5d/docker-autocompose/blob/master/README.md This way, you can use docker compose to start/stop/update and have a permanent config which you can easily migrate to a new NAS/server.

Run this https://github.com/Red5d/docker-autocompose

Here is the link to docker-autocompose for those that might be able to help. https://github.com/Red5d/docker-autocompose

I converted existing docker run via https://www.composerize.com/ (since I had them written down in text file) , you can also use https://github.com/Red5d/docker-autocompose (examples on very bottom) to convert existing containers to YML file.

You can use this tool to figure out how to run again any currently running container https://github.com/lavie/runlike

Issue for podman support: https://github.com/lavie/runlike/issues/71

I had started out the same way, especially if it was a new app and I wasn't familiar with how I really wanted to run it. Some containers expect a fair number of environment variables and multiple mounts. Once I got everything working, I would create a script /svcs with the corresponding docker run command. There's even a cool tool called "runlike" which can create a well formatted command for any running container.

https://github.com/lavie/runlike/

But I've got those migrated to docker-compose files these days and I try to start with the docker-compose file instead of going directly into testing out docker run commands.