omv-extras 6.3 / openmediavault-compose 6.7

Quote from Soma

But you do know that, even if you kill your portainer container, your mDB container will still be running, correct?

Portainer is a wrapper for the containers, it doesn't own or hold any files from them.

If you nuke the docker installation, then you should be worried.

And that's one of the major concerns (that I've seen) of the devs: when a change is done, never to give a change of damaging the prior installation,

Well, the main issue here is that there are not enough collaborators or devs (and you know that) and no one willing to take that responsibility other than some afficionados on their free time.
And the compose plugin has been around for so long and discussed that this transition was (should be) a breeze.

Display More

You are correct in saying that I should have know better that Portainer is just a "front end" tool, "wrapper" as you say, but without much of an explanation as to "background" of the change I was concern. There is "no harm" done and I think that OMV is progressing in the right direction, so all is good.

On the subject of compose plugin being available for a long time, I use very few plugins in OMV. One of them is MariaDB for Kodi database. My OMV/NAS is just that, NAS as a personal cloud and NAS as a multimedia storage/server. I do not use it as a Firewall, Anti Virus nor Reverse Proxy. I have and use, no offense to anyone, better means, IMHO, of doing all of that. So that is the reason why I do not check/look into available plugins. So, in some respect, it is my own fault of not seeing "compose plugin" and investigating it for what it is. But, as I said, all is good and no harm was done.

Quote from andrzejls

One of them is MariaDB for Kodi database

What I got used to is, for those really important containers, just have a failsafe backup of both the config volumes and the YML.

Solution is to have a rsync clone of the appdata (config) folder on another disk. (config folders won't be that big. Although a Database might be quite some gigas)

Then for test, just kill/nuke the container, edit the YML to point to the new folder (volume/config/appdata, etc) and redeploy the container.

It will be as if nothing happened.

Quote from andrzejls

But, as I said, all is good and no harm was done.

And this was the final goal with the transition,

Quote from Soma

What I got used to is, for those really important containers, just have a failsafe backup of both the config volumes and the YML.

Solution is to have a rsync clone of the appdata (config) folder on another disk. (config folders won't be that big. Although a Database might be quite some gigas)

Then for test, just kill/nuke the container, edit the YML to point to the new folder (volume/config/appdata, etc) and redeploy the container.

It will be as if nothing happened.

And this was the final goal with the transition,

Display More

Yes, I utilize "rsync" extensively for doing 1:1 copy/image of my important data. HD`s are so inexpensive these days, I use 11 (9 internal and 2 USB) of them on my NAS. Chances of 2 (two) HD`s going bad at the same time is slim to none, so I do not even bother with RAID. For home use it just complicate, RAID, things too much.

Quote from noiro

watchtower can delete images after it updates them.

set up the environment parameter

Code

WATCHTOWER_CLEANUP = true

I don't use watchtower to do the updates, just for the email, so for me the new plugin is nice and easy for pruning.

I've also started using Diun for checking of updated images, I don't like the way it does and email for each image though, so I use dozzle to check the logs of Diun and the rest of my containers. As we know there is rarely just one way to do somethings with computers

Quote from BiNh0X

Thank you immensely for being thoughtful in your responses, Soma  chente  ryecoaaron  KM0201

For now, I will not do the migration for fear of breaking something, besides that I do not want to leave the Portainer, because I am already used to using it and I like it. Even in more advanced matters I can solve for him without major difficulties.

The question is, is it possible to re-show the status of containers in WebUI without doing this migration? After the omv-extras update, this option disappeared from the dashbaord.

Thanks.

Display More

TBH you've timed it right to come to this forum, as most of the questions have been answered and a guide has been produced. I humbly suggest you take a little while and read the guide on here and the omv6_plugins:docker_compose doc and the change and setup will be a lot easier than you think.

I really like this plugin, I was a big user of portainer and yacht, but neither of them made it as easy as this plugin does to backup your docker-compose.yml (stacks) files, for me it's worth it just for that feature alone.

But as others have said, you get the best of both worlds though, not often that happens.

I've just been reading https://wiki.omv-extras.org/do…v6_plugins:docker_compose

I was going through 'How to update a single docker-compose container' section and it seems to me that the first line is wrong, can't all this be done from 'Services > Compose > Files' now?

Quote from chente

https://github.com/SelfhostedPro/selfhosted_templates

If I remember correctly doesn't that just setup a container with no editable yml file when in portainer. This is very much like the 'add from example' we have in the plugin, but what nice with the plugin 'add from example' is that it creates a docker-compose file.

So if this was added, which I do think is a nice idea, we would have a truecharts for OMV, but I would really like it if it follows the 'add from example' option and create a docker-compose file.

I just think the docker-compose file is a better way to go rather that the old way OMV used to a docker image, whereby you had to add stuff via a page of options.

Quote from chente

No. If you do it in Services>Compose>Files you will update all the containers defined inside the yaml file.

To update a single container you must do it from the tab Services>Compose>Containers

The only yml file I have more than 1 container is nginx, everything else I run is a single yml file for each container. So for me personally I assume I can do all from Services->Compose->Files? Or I'm I still getting wrong?

Quote from ryecoaaron

Then no, those will not be part of the compose plugin. The first problem is that they require portainer. I see the example compose files available on the files tab as being pretty much an equivalent. We just need more people to contribute to the examples.

What do you require for an example? Just going to linuxserver.io and grabbing the docker-compose file and sending it to you? If so, I don't mind making a start on that. Or you've got a template on what you require please post url so I can look at it.

Quote from trythat

What do you require for an example? Just going to linuxserver.io and grabbing the docker-compose file and sending it to you? If so, I don't mind making a start on that. Or you've got a template on what you require please post url so I can look at it.

Just a thought as a new user, if there is no writing guide, it would be nice to base any examples on the guide in the wiki that uses jellyfin. In other words follow the naming conventions used in the example and locations, etc. It may bring down the learning curve to just get something working correctly the first time. Thanks.

Quote from chente

In that case you would be using the following procedure https://wiki.omv-extras.org/do…_docker-compose_yaml_file

A common example of this is Nextcloud together with nginx and mariadb, which are usually included in the same yaml file. If you want to update only Nextcloud you must do it in the Containers tab.

I get that, but I'll do all mine from the files menu, unless I have some bigass yml file with loads of containers in it. If I can save clicks I'm going for it

This is pointless.

The example is nothing more than the YML already available for the service on docker hub or GitHub.

Then copy/paste to the plugin and edit per use case

Quote from Soma

This is pointless.

The example is nothing more than the YML already available for the service on docker hub or GitHub.

Then copy/paste to the plugin and edit per use case

I understand and thats what I do, but you'd be surprised how often people just won't or can't do that and like the option of just clicking a few buttons and have the yml file there. And looking at a couple of the examples and there are a good number there already, I don't mind spending some time on going to linuxserver.io and grabbing docker-compose files and sending them to ryecoaaron if it makes his and others life easier.