omv-extras 6.3 / openmediavault-compose 6.7

Zitat von KM0201

The idea of course, is to eventually get away from Portainer and keep things within the webUI and make support easier. I know this may seem painful, but I think in the end, this is going to be an excellent change. Transitioning is really not that hard.

Take a look in the guide section. I just put a simple guide to setting up the new plugin for both new and current installs. Once that's done and seems to sink in for everyone, I'll go over stacks to the new plugin.

I understand the concept and agree with it. It just came as unannounced surprise and confusion, at least in my case.

Zitat von geaves

Have a look at this it should be of help

I followed the various steps but I'm exactly in the same situation as before, nothing new.

Thanks for your help.

thanks!

Zitat von ryecoaaron

Assuming you used a stack in portainer for mariadb, you just stop the stack, copy the stack (really a compose file), and paste into a new File in the compose plugin. Save and apply. Then press Up for that file. It will use the same image and volumes. Nothing will really be new.

One more question: in Portainer we had Env. settings (see bellow)

Do I need to and/or how do I transfer them to "Services | Compose | Files Environment section?

use advanced mode to copy & Paste:

Zitat von geaves

That guide could not be any simpler, your #174 point 2 makes no sense, there is no portainer gui so I fail to see how it can be a black page

I thought it would be possible to use the Portainer interface again, or any other GUI to easily manage my two containers (both created with Portainer). At the moment I am left with the CLI. How can I at least transfer the containers previously created with Portainer into Compose and thus see them listed among Compose/Containers?

Zitat von KM0201

No data is shown in Containers, because it only shows data that has been with containers configured in the new plugin.

How did you install Portainer before? Have you tried reloading your browser cache on Portainer? (Control + Shift + R)

I performed these steps:

1- docker container stop portainer

2- docker container rm portainer

3- Compose/Files/Add from Example/portainer-omvextras

Zitat von ryecoaaron

Now, you need to start the containers with the Up button on the Files tab.

Great, it works! Thank you. Now I have Portainer again.

It's not clear to me at this point if it's better to "migrate" the management of Cointainers to Compose and how to do it exactly.

Zitat von ryecoaaron

How was I supposed to announce it? I can't wait weeks waiting for people to not read a post on the forum. And this really isn't as big of a change as some are making it out to be. The compose plugin has been out a year. Literally the only things that have to change are where you install docker and how you start portainer.

Sticky note on this forum could have been a help. In the background how the thinks operate you are correct, but way of how it needs to be done now is different. People, like me for example, got used to do things certain way and are creatures of habit. Now this change comes and we are baffled as to what happened, check the postings on this forum. All of the help, explanations that we see here, and they are great, should have been, IMHO, posted here first and ahead of transition. I read someplace here that this change was slated to be implemented in OMV7, but was decided to do it now. So there was no rush, as far as I can tell. I like to stress that after working with this new approach/method for couple of hours, I think that this is much better approach to containers vs Portainer. Those are just my comments and NOT criticism of developers nor anyone else. I started with OMV4 and I see great progress and growing maturity of OMV. Keep up the great work.

Zitat von ryecoaaron

How was I supposed to announce it? I can't wait weeks waiting for people to not read a post on the forum. And this really isn't as big of a change as some are making it out to be. The compose plugin has been out a year. Literally the only things that have to change are where you install docker and how you start portainer.

80% of users don't browse these forums. I like many others was blindsided by this. Unlike most people, I am a full-time dev and am fully aware of how containers portainer and yacht work.

I totally support the compose plugin making things more simple and using docker files and compose files frequently with portainer. There are some major things you failed to think about as a developer before committing to this idea.

1. A MAJORITY of the people using OMV are following youtube tutorials and barely even know how to move a file on Linux. So years of this functioning the same and now most OMV users using this plugin just changed overnight. The few videos that exist supporting all the awesome features your plugin offers are now outdated. (And yes ik its simple to learn the commands but we are talking about the average user who now has to fill this thread with things being broken and having barely any actual Linux experience lol)

2. The average user is primarily interested in running applications like PiHoles and enjoying the straightforward integration that allows Portainer to easily create and manage networks. With the removal of the user-friendly features we previously had automatically in portainer, are you expecting these users to suddenly become comfortable with command lines?

3. While intended to improve efficiency and simplify processes, it appears to have the opposite effect. Deployment time on fresh installs has increased significantly. What used to be a simple 'get' command and click to install Docker has now become a process that freezes systems, necessitates a restart, and often results in hanging. The update process, as it stands, lacks smoothness and user-friendliness.


I recommend you revert this and add a tab to OMV extras with a warning sign letting users know the functionality is due to change with a wiki link and a warning ICON. If reverting is not an option please at a bare minimum add a wiki link or thread link with a warning sign under the omv-extras in the system so people aren't so confused.

I don't intend to ridicule you for this change but from any perspective, some steps were missing from this deployment to ensure a smooth transition. Nonetheless, you are owed a huge THANK YOU for all the work you've done on omv-extras. Thanks to you I have had my home systems running smoothly for years. I hope you value this criticism as more appreciation for what you've already accomplished more than random hate.

Zitat von ryecoaaron

Where are you getting this? I know people did not like the omv-extras 6.2.1 plugin that was in the testing repo but this is not that. Enabling the docker repo is significantly faster on all systems. I realize the update is not perfect but of the bad stuff was caused by users not following the instructions properly. I actually just went through the upgrade on my brothers system and cannot figure out why it was so bad for some users.

I encountered this strange issue doing a fresh OMV install three times after I didn't notice the change (lol 🤣). I also saw someone mention the same exact issue in another thread/post, I'm not sure what would cause it but I'll do my best to break it down.

Fresh Omv install > install updates > reload > install omv extras > some new updates appear attempting to apply then from OMV's update manager (4 including salt and an update for OMV itself)

One of these steps caused omv to hang after applying changes requiring a full reboot to regain access

THEN when you attempt to update you get this:

Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ** CONNECTION LOST ** █ OPEN MEDIA VAULT

Running omv-upgrade manually fixed this and any omv-extras didn't work prior to doing so (KVM plugin etc). Something small but from the post I saw this didn't only happen to me.