docker-autocompose VS dockcheck

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.

As someone who knows just enough about Docker to be able to scratch together a docker-compose.yml every now and again only to promptly forget all the commands I need to ever maintain them going forward, I'm eternally grateful that dockcheck.sh prompts me to do this as a final step whenever I run it.

I’m a simple man. I upgrade everything via dockcheck, verify that everything still works, and if not restore from backup!

And I've personally made a script to selectively auto-update containers, or just check status. With the option to filter or exclude specific containers. Find the project here: mag37/dockcheck

To "mass-check and mass-update" containers from the commandline, dockcheck is very light and useful. A simple dockcheck.sh -a -p for example would check all deployed containers for image updates and if there are any, pull them, then restart the container and at the end, cleanup unused images to free up diskspace. There is also a version with a web interface, DCW.

I haven’t gone the watchtower route, since I’d prefer to review changes myself (or let’s be honest - others’ reactions to the changes). Instead. I’ve been using a combo of diun and dockcheck (https://github.com/mag37/dockcheck ). Diun lets me know when containers have changed and dockcheck lets me cherry pick what I upgrade.

If you want to update images, try dockcheck or DCW.