I got omv-engined restarted and then the install worked. Was the portainer installer removed?
yes portainer installer was removed
Posts by destroyed-IT
-
-
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. -
A major function change has taken place and omv-extras has updated the way it works.
please refer to this thread on how to deal with this:
omv-extras 6.3 / openmediavault-compose 6.7
you will need to install the docker-compose plugin after enabling the docker repo / back ports -
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.
