omv-extras 6.3 / openmediavault-compose 6.7

Procedure if you want to get rid of Portainer.

You must first redeploy containers one by one in openmediavault-compose. To do that, for example with Jellyfin:

1. Make sure you have the jellyfin configuration yaml file to deploy from openmediavault-compose. If you don't have a copy first retrieve Portainer as per post 18 and copy the jellyfin yaml file to a text file.

2. Stop and remove the jellyfin container docker stop jellyfin and docker rm jellyfin Or from the Portainer GUI, the result will be the same.

3. Deploy the container in openmediavault-compose to Services>Compose>Files with the jellyfin yaml file and initialize it.

When you have done that with all your containers you can delete Portainer, you no longer need it.

Quote from fbeye

So is all this essentially paving the way to rid of Portainer as a middle-man?

Yes, that is ryecoaaron 's reasoning. openmediavault-compose allows you to do what most people need to deploy a container, so you avoid having Portainer installed.

You always have the possibility to install Portainer as another container if you need it for any reason. In the examples there is a yaml ready to launch Portainer if anyone wants it, it's always been there.

If I'm seeing your direction correctly, I really like where you're going with this. It would appear you're trying to integrate docker back into the webUI (the way it was many moons ago) without requiring so much work on your part as it basically just uses docker-compose..... I ran into one minor "issue". Clean install of debian, installed OMV w/ the omv-extras script.

I set my containers folder and compose folders, installed docker no problem. Put a compose file in and when I went to run it, docker-compose was not installed. Once I installed it docker-compose with apt, it went w/o a hitch.

I suspect there will be some growing paints for people moving to this from the old system... but again if I'm seeing your direction correctly... I like this change a lot.

Quote from fbeye

So is all this essentially paving the way to rid of Portainer as a middle-man?

It would appear so. Way way long ago.. docker was heavily integrated into the webUI.. unfortunately the way it was done, required a massive amount of work for aaron to maintain.. thus why he basically put the portainer plugin and recommended everyone use portainer (if you look at some old technodad videos of omv 4, you'll see what I'm talking about)

With the way he's integrating it now.. it's really just docker-compose... I'm guessing that will be far easier for him to maintain.

Quote from ryecoaaron

wtf. I just posted this as an announcement. I didn't realize it would turn into a shit show. Uninstalling omv-extras or upgrading it won't change docker or portainer.

Since the compose plugin depends on the newest version of omv-extras that doesn't have the docker components, this is unavoidable.

I know. I forgot to change it.

No.

It only shows containers that are created by the plugin compose files.

Thanks. Just remember it isn't OMV. it is omv-extras. I know people hate change but your "constructive" criticism doesn't help much. Leaving things the same wasn't an option. Peoples reliance on portainer without having a backup or really understanding what it was doing is why I needed to do this.

Don't use the compose plugin then. Why is having the sharerootfs plugin "active" a problem? Quite a few omv-extras plugins depend on it. And being used for docker-compose files is a VERY good reason to have it always active. I would love to hear how to not have it active...

Yep. portainer is overkill for 99% of omv users and not really needed. Most people are just cutting and pasting compose files in portainer anyway but with no backup as I mentioned above.

Display More

For what it's worth.. I deployed portainer with the compose plugin (just as a test), and it's not showing in the container list either, but it's running just fine. I was just about to point that out.

Quote from ryecoaaron

Easier and more flexible for users. But evidently, I'm not allowed to change anything ever...

Me and you have had this discussion. As you are aware, my response invovles foul language and insults..lol.

As I said above, I really like where you're going with this. There likely to be a few hiccups and a slight learning curve for people going from "the old way" to this way.. but I remember when you dropped the docker plugin altogether, and all the chicken little's thought the sky was falling...

Quote from ryecoaaron

I'm not having that problem. I would ask for more details but the response to these changes makes me not want to work on anything.

Don't let the jackasses get you down.

root@omv6-test:~# docker ps
CONTAINER ID   IMAGE                           COMMAND        CREATED          STATUS          PORTS                                                                                            NAMES
93fcfa36ccd8   portainer/portainer-ce:latest   "/portainer"   30 minutes ago   Up 16 minutes   0.0.0.0:8000->8000/tcp, :::8000->8000/tcp, 0.0.0.0:9000->9000/tcp, :::9000->9000/tcp, 9443/tcp   portainer
root@omv6-test:~# 

Quote from ryecoaaron

I would ask for more details but the response to these changes makes me not want to work on anything.

From my point of view you are absolutely right to make this change. I already told you a long time ago.

You are also right to be upset by the reaction of... two ... users. But don't lose sight of the fact that there have been 2. It's not worth it. In time those two users will also appreciate it in their hearts, but they will never say it here, of course.

They never like changes because they force people to reconfigure something that was already working, but in this case, as you say, it was a necessary change.

When you have calmed down I think it would be a good idea to add docker stop portainer and docker rm portainer in the initial post.

ryecoaaron

Not sure if this helps, but the Stats page is working correctly... Not sure why it isn't showing in Containers..

Quote from chente

From my point of view you are absolutely right to make this change. I already told you a long time ago.

You are also right to be upset by the reaction of... two ... users. But don't lose sight of the fact that there have been 2. It's not worth it. In time those two users will also appreciate it in their hearts, but they will never say it here, of course.

They never like changes because they force people to reconfigure something that was already working, but in this case, as you say, it was a necessary change.

When you have calmed down I think it would be a good idea to add docker stop portainer and docker rm portainer in the initial post.

Agree. I've always said I'm a big "creature of habit" and don't like change much, but this one I can get behind because of the flexibility it has. I just think there might be some growing paints for people moving to it.

For those who don't remember when the sky was falling last time, here's a thread where it was discussed while OMV 5 was in beta.

We all survived, docker ran just fine in OMV 5, etc. once everyone gets this figured out, we'll all be OK again.

Thread

Portainer: Much Ado About Nothing

If there is a move to drop the Docker plugin for Portainer, why not use Cockpit, it's easier to use and understand and not as daunting as Portainer. I've tagged the OMV version as 5 purely for this thread.

geaves

Aug 24th 2019

Quote from ryecoaaron

Was the container started by the compose plugin?

I am calm. People just kill motivation and enthusiasm.

Added

yes. It was a clean install