docker-autocompose VS Diun

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.

Thanks, I used to use it. I moved to using diun to just notify of updates but not apply them though.

https://crazymax.dev/diun/ and docker compose

Similar to Watchtower but without the option to auto-update containers, just notifying is diun. But imo it does that better and more reliable than Watchtower does. You can get notified by Email, Discord, Pushover, Telegram and many more options.

If your apps are container images, then there are tools like diun, watchtower and whatsupdocker, those can watch the image repository (like Docker Hub) and notify you if a new/updated image has been found. Some can even download and auto-update for you, but that comes at some risk of course.

You might want to have a look at https://crazymax.dev/diun/ which is purpose built for what you're trying to do (notify when an update is available, but not install).

Watchtower is inferior to a project like DIUN this way. Because with double you can actually be notified by newer image versions and act accordingly. But automatic updates (which latest is aswell) are bad practice.

diun is very similar to that, but it doesnt auto-update, just notifies but does that very well imo.

I use https://crazymax.dev/diun/ to send notifications of new images. I also hook it into webbooks with CI for mirroring images, but you should be able to use something like portainer webhooks to auto pull images.