omv-extras 6.3 / openmediavault-compose 6.7

trythat · May 31st 2023

Quote from ryecoaaron

All of the columns are sortable but I would have to change the plugin for the Name column to be the sorted field always. The containers are grouped by project but not sorted currently. And this is what I would prefer. Between having the filter field and being able to sort the container names with one click, I don't see a reason to change how it is now.

Sorry my question wasn't as straight forward as I thought when I reread it. I was asking that the Containers page would remember what the sort order was from the last time it was displayed. I do realize a lot of my suggestions are because I'm lazy

ryecoaaron · May 31st 2023

Quote from trythat

I was asking that the Containers page would remember what the sort order was from the last time it was displayed.

OMV remembers the columns you have displayed but not sorting. That would have to be a core OMV request.

jorensanbar · May 31st 2023

Quote from ryecoaaron

Seems to work better than portainer that on my system is just doing something like this - 0.0.0.0:28080 (which doesn't work).

That's because you never configured the environment. Although with this plugin possibly many people will leave Portainer aside.

Portainer > Environment > "YourEnvirnment" > IP o Domain > Save.

ryecoaaron · May 31st 2023

Quote from jorensanbar

That's because you never configured the environment

You are correct. I have never really used portainer and have no plans to. I prefer command line myself. I might change my primary server over to the compose plugin since I am using the kvm plugin so much now.

noiro · May 31st 2023

Quote from chente

Yes, it's better. Read publication 1 of this thread, ask your questions.

That is debatable They serve different purpose.

If one wants a pure OMV installation, then yes. The "new" way of manage docker containers is a huge improvement.

If one wants to go one step further from just "managing" docker containers (i.e. play with kubernetes, play with kubernetes on cloud, manage more than one server) then portainer is a very good solution. Both the Community Edition and the Business Edition (free for up to 5 nodes).

I fully support the decision to split portainer/yacht from omv-extras and have a more "native" solution even thoough I will still use portainer.

It is also debatable if the timing of the introduction of that "split" was right or no. There is no perfect time IMHO. Did it cause problems? Not really. The forum is here and if someone can read it will sort any issue in no time. ryecoaaron is very helpful and petient, sometimes too petient

I do believe the timing was good. If it was introduced with version 7 it will cause bigger impact, less time to assist etc.

Anyhow, it is an open and free software. I am grateful for what I get and if it broke my system(s) once or twice is fine, I learned couple of new things along the way

ryecoaaron · May 31st 2023

Quote from noiro

If one wants to go one step further from just "managing" docker containers (i.e. play with kubernetes, play with kubernetes on cloud, manage more than one server) then portainer is a very good solution. Both the Community Edition and the Business Edition (free for up to 5 nodes).

This is way beyond what 99.9% of OMV users need and not the intended reason I added it to omv-extras in the first place. People cutting & pasting compose files to spin up docker containers don't need portainer. None of the changes I made prevent someone from using portainer. In fact, it allows it to be more flexible. But I am going to try very hard to push people toward using the compose plugin because there are way too many portainer support requests on this forum.

chente · May 31st 2023

Quote from noiro

That is debatable They serve different purpose.

There is not much to discuss. It is better for the vast majority of users

If you are not among them, install Portainer in the plugin.

chente · May 31st 2023

Quote from ryecoaaron

there are way too many portainer support requests on this forum.

Completely agree. It's been a while since I wrote this. https://wiki.omv-extras.org/do…se_openmediavault-compose

noiro · May 31st 2023

Quote from ryecoaaron

But I am going to try very hard to push people toward using the compose plugin because there are way too many portainer support requests on this forum.

Truth be told portainer is not doing good job of keeping appdata, yamls etc tidy and in easy to find place. The compose plugin simplifies that I think.

I do not think you need to push. It is a good evolution so people will follow. Well at least the 99.9% of them

Maybe a way to assist is a clear path/guide to "migrate" from portainer way to compose plugin.

Portainer saves the stacks in /var/lib/docker/volumes/portainer_data/_data/compose/ but in folders with a number and not with the stack name. But they are there. Copy past to the plugin and you are up and running.

ryecoaaron · May 31st 2023

Quote from noiro

Maybe a way to assist is a clear path/guide to "migrate" from portainer way to compose plugin.

Thread

Guide: Using the new docker plugin

This is for those of you struggling with the new docker plugin. It should hopefully help you transition to the new plugin, with the eventual goal of transitioning away from Portainer (the idea of the new plugin is to keep everything contained in the OMV webUI, and make support more consistent).

If you are transitioning from an install with the old plugin, verify where your containers are stored on your system. As root or sudo, execute the following command

(Code, 1 line)

and record the path in…

KM0201

May 30th 2023

noiro · May 31st 2023

Quote from trythat

I use prune via a cron job once a week and using watchtower means there are nearly always unused images about

watchtower can delete images after it updates them.

set up the environment parameter

Code

WATCHTOWER_CLEANUP = true

BiNh0X · Jun 1st 2023

I understand that the OMV team is always looking for improvements and I am very grateful for that, after all we have a great and free NAS system (again, thanks for that), but this mandatory migration to composer was terrible for me, who likes to manage containers (install, update and remove) directly through the Portainer interface. Before, I just clicked a button in omv-extras, installed Portainer and everything was fine and simple. I rarely touch the terminal to do anything Docker related and everything works perfectly fine for me. Or it worked. Everything seemed so much simpler before and the only thing I did was check the status of containers in the OMV WebGUI. Now, not even that. And all this change seems to be still poorly documented and from what I've read so far in this topic, I'm going to have a lot of work to migrate everything... Terrible.

Soma · Jun 1st 2023

Quote from BiNh0X

Or it worked. Everything seemed so much simpler

And it still is.

Nothing is stoping you to continue to use portainer.

chente · Jun 1st 2023

Quote from BiNh0X

I understand that the OMV team is always looking for improvements and I am very grateful for that, after all we have a great and free NAS system (again, thanks for that), but this mandatory migration to composer was terrible for me, who likes to manage containers (install, update and remove) directly through the Portainer interface. Before, I just clicked a button in omv-extras, installed Portainer and everything was fine and simple. I rarely touch the terminal to do anything Docker related and everything works perfectly fine for me. Or it worked. Everything seemed so much simpler before and the only thing I did was check the status of containers in the OMV WebGUI. Now, not even that. And all this change seems to be still poorly documented and from what I've read so far in this topic, I'm going to have a lot of work to migrate everything... Terrible.

Over time you will appreciate it, as soon as you start the transition and realize how simple it is and when you see the simplicity of use and functionality of the plugin. I guarantee you won't want anything to do with Portainer anymore.

Personally, it has taken me by surprise and the first two days I could hardly attend to this matter due to work issues, but the wiki documents are already updated since this morning, and with an added procedure to recover portainers and containers. And you have a specific guide for this update in the guides section of the forum. And you have this thread with 313 posts to ask questions. I think you are well taken care of.

Actually, in the time that I have been here, I have rarely seen the display that has been dedicated to this topic.

chente · Jun 1st 2023

Quote from Soma

Nothing is stoping you to continue to use portainer.

As soon as he cats the plugin he won't want to use Portainer anymore.

chente · Jun 1st 2023

BiNh0X Ask whatever you want, I am here to solve all your doubts

Soma · Jun 1st 2023

Quote from chente

As soon as he cats the plugin he won't want to use Portainer anymore.

That's the point:

Portainer will always be available even if you don't use or need it anymore.

But some people only see what's in front of the eyes.

And just because there's no "open portainer page" button, already assume that it's gone FUBAR.

"Friends are like stars

Even if you don't see them

Doesn't mean they're not there"

ryecoaaron · Jun 1st 2023

Quote from BiNh0X

this mandatory migration to composer was terrible for me,

It isn't mandatory.

Quote from BiNh0X

who likes to manage containers (install, update and remove) directly through the Portainer interface

Shockingly, you can do that in the compose plugin and it is simpler in my opinion.

Quote from BiNh0X

Before, I just clicked a button in omv-extras, installed Portainer and everything was fine and simple.

All you have to do is install the compose plugin from the Plugins tab. Future updates will be installed from the Updates tab which you are doing anyway to update OMV and the OS. The setup of the containers will need to be done again but you had to setup your containers in portainer when you started too. You will have a better backup and easier recovery as well. I get it that change is hard for some but look at it instead of just assuming the change is bad.

Quote from BiNh0X

I rarely touch the terminal to do anything Docker related

You still won't have to.

Quote from BiNh0X

Everything seemed so much simpler before and the only thing I did was check the status of containers in the OMV WebGUI.

That also still works.

Quote from BiNh0X

And all this change seems to be still poorly documented and from what I've read so far in this topic,

There are multiple guides and this thread has just about everything you need. I guess you need to read more.

Quote from BiNh0X

I'm going to have a lot of work to migrate everything... Terrible.

Or just install portainer in the compose plugin and stay with your old system. Even that migration is covered extensively.

KM0201 · Jun 1st 2023

Quote from BiNh0X

I understand that the OMV team is always looking for improvements and I am very grateful for that, after all we have a great and free NAS system (again, thanks for that), but this mandatory migration to composer was terrible for me, who likes to manage containers (install, update and remove) directly through the Portainer interface. Before, I just clicked a button in omv-extras, installed Portainer and everything was fine and simple. I rarely touch the terminal to do anything Docker related and everything works perfectly fine for me. Or it worked. Everything seemed so much simpler before and the only thing I did was check the status of containers in the OMV WebGUI. Now, not even that. And all this change seems to be still poorly documented and from what I've read so far in this topic, I'm going to have a lot of work to migrate everything... Terrible.

I'm not sure where you got mandatory.

Recommended, yes. Mandatory? No.

BiNh0X · Jun 1st 2023

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.

Participate now!