I'm not a good example since I was already using the compose plugin for a long time.
But the update was just that, an update. No issues:
My situation is the same, all my containers were already in openmediavault-compose. In fact Portainer no longer existed on my system.
If people had done this long ago the commotion would have been insignificant, but normally we are all animals of habit, for better or for worse.
Display MoreWhat can I say, JUST LOVE IT!!!!!!!!!!
ryecoaaronThank you for taking this move.
Me and chente had spoke with you that this was the way to go and people will have to accept it and evolve with it.
I'm not a good example since I was already using the compose plugin for a long time.
But the update was just that, an update. No issues:
And this is what people will have in the end:
I do love simplicity,
I was pretty heavily in stacks.. but they were super easy to move to the new plugin. I like it.
I was pretty heavily in stacks.. but they were super easy to move to the new plugin
My only multi service stack is nextcloud.
FYI, On the openmediavault-compose thread, there's a lot of info/talk about how the plugin changed to cover all angles, especially on ditching portainer.
My only multi service stack is nextcloud.
FYI, On the openmediavault-compose thread, there's a lot of info/talk about how the plugin changed to cover all angles, especially on ditching portainer.
Yeah. People still seemed massively confused. Aaron asked someone to write a guide so I fired one off.
please can you create a little link button like KVM or something so you can click it like in Portainer and it'll open up your containers web UI?
In Portainer, you could click the port link, and it would take you to the container.
I guess I could make the ports in the Containers tab hyperlinks to click on. I will look at that.
I'll also try to move my lscr.io/linuxserver/plex in a while. Thank you.
Finally I moved all the containers, even though I didn't have the yaml files. Now everything is simpler and more effective. Thank you all for your support and for evolving and improving OMV with this update. 
Finally I moved all the containers, even though I didn't have the yaml files. Now everything is simpler and more effective. Thank you all for your support and for evolving and improving OMV with this update.
So how did you do it without the yaml files to get all your configs back for each of your Docker applications? Or did you start from scratch?
So how did you do it without the yaml files to get all your configs back for each of your Docker applications? Or did you start from scratch?
You can do that with autocompose. It's not the best but it can be done. Autocompose generates a yaml file from a working container, but will sometimes include unnecessary information. It is always better to have the original yaml.
If I had to do it I'd rather start from scratch or try to create the yaml myself.
Gents,
the compose plugin is really, really great. I love it´s simplicy. Struggled a little bit with the empty containers list but with the how-to of KM0201 it was easy to fix, coming from an "older" Installation.
ryecoaaron Thank you again for your hard work 
I was pretty heavily in stacks.. but they were super easy to move to the new plugin. I like it.
I am kind of the same especially it is easier to map the ports when adding services that depend on a different service.
So far everything is running, just one thing: If I want to stop a container I have to go to files and press the down arrow. As I have made various containers with one single stack I can only stop all containers. It would be handy indeed to be able to stop only a desired container instead of stopping all of them. Is there a way? If not, I would most probably split the compose files in order to be able to start and stop specific containers...
Otherwise: Great job ryecoaaron. Works flawless.
I am kind of the same especially it is easier to map the ports when adding services that depend on a different service.
So far everything is running, just one thing: If I want to stop a container I have to go to files and press the down arrow. As I have made various containers with one single stack I can only stop all containers. It would be handy indeed to be able to stop only a desired container instead of stopping all of them. Is there a way? If not, I would most probably split the compose files in order to be able to start and stop specific containers...
Otherwise: Great job ryecoaaron. Works flawless.
Well, the way to resolve that is use a single stack for each container. I broke away from using 1 stack for multiple containers years ago for this reason. Now, I only have 1 stack/compose file for each service (nextcloud has 2 containers, piwigo has 2 containers... but all my other ones only have 1)
Is there a reason you need them all in one stack/compose file? Having them separate, also makes them easier to update, as you don't have to redeploy the entire compose file, just to update one container.
Of course the other simple way....
docker stop container_name
It would be handy indeed to be able to stop only a desired container instead of stopping all of them
There is no such possibility, and I agree, it would be useful. ryecoaaron , maybe you could add a button on the Containers tab to stop a container.
It is often useful to have multiple containers in a single composition file to facilitate communication between them without the need to create a specific network to add to each container. In this case, only one of the containers cannot be stopped.
I just released a new version of openmediavault-omvextrasorg 6.3 and openmediavault-compose 6.7.
IF YOU DON'T UNDERSTAND DOCKER WELL, WAIT to FOLLOW THESE DIRECTIONS UNTIL THEY ARE IMPROVED!!!
- The docker, portainer, and yacht installs have been removed from omvextras. You will only enable the docker repo in omv-extras now.
- The docker install has been added to the openmediavault-compose plugin.
- If you were using portainer created by omv-extras, you should be able to use the "add example" option the Files tab of the compose plugin to add a portainer compose file using the portainer-omvextras example. This will reuse the existing portainer_data volume. You will need to do a docker container stop portainer and docker container rm portainer first.
- The "Reinstall Docker button on the Settings tab of the compose plugin will install docker and docker-compose (This is only needed if docker is not installed).
All of this was done since the docker stuff did not belong in omv-extras in my opinion. And while I think the compose plugin replaces portainer nicely, I think moving people to using portainer with a docker-compose file is better than me maintaining a config that was not very flexible (lots of people asking for customizations).
Hey!
Might this be the issue why PhotoPrism and Filebrowser don’t work anymore on my new install?
They install, and run just fine, but apparently, nmap tells me that the ports are filtered, even though I added a rule to the firewall that allow the ports from both plugins.
Please correct me if i'm wrong :
1- I updated this morning, all my container still run smoothly
2- I installed docker compose plugin
3- In there, i see the docker path is the same as i had before (that's why it still runs)
4- All the containers are well seen in the stats tab
5- if i want to remove portainer, i have to redeploy all the stacks and containers using the plugin
6- if i don't do that, i still need to use portainer to manage everything, or the usual CLI commands.
Thx in advance.
Might this be the issue why PhotoPrism and Filebrowser don’t work anymore on my new install?
They install, and run just fine, but apparently, nmap tells me that the ports are filtered, even though I added a rule to the firewall that allow the ports from both plugins.
The update has nothing to do with this conflict between docker and podman. Look for information on the forum, there are many threads about this.
Display MorePlease correct me if i'm wrong :
1- I updated this morning, all my container still run smoothly
2- I installed docker compose plugin
3- In there, i see the docker path is the same as i had before (that's why it still runs)
4- All the containers are well seen in the stats tab
5- if i want to remove portainer, i have to redeploy all the stacks and containers using the plugin
6- if i don't do that, i still need to use portainer to manage everything, or the usual CLI commands.
you have a procedure here https://wiki.omv-extras.org/do…openmediavault-compose_67
and a guide here Guide: Using the new docker plugin
that explain what you need. Have you read them?
The update has nothing to do with this conflict between docker and podman. Look for information on the forum, there are many threads about this.
Alright, I'll try to look around, and eventually create a thread, if I don't find anything. 
Docker has changed just yesterday.... Look in the Guides section on "How to use the new docker plugin".
I found your newly written guide and reviewed it. Thank you and everyone for the efforts! As I was following the previous guide in order to have omv6 on a flash drive, docker on an SSD, and my data on a 6TB HDD. You introduced the name containers. You seem to say that should go on the HDD. Is that the same as the DATA in the previous guide? It would be helpful to have some consistency for those of us with only a limited knowledge and trying to follow something. Could someone possibly look at the previous guide and get us to the endpoint of loading a container with jellyfin, using the naming convention used in the previous guide. Thank you 🙏!
Don’t have an account yet? Register yourself now and be a part of our community!
