I need help on how to update portainer.
It was installed under openmediavault-compose 6.9 and now the new portainer version is 2.18.4.
Thanks
omv-extras 6.3 / openmediavault-compose 6.7
-
- OMV 6.x
- ryecoaaron
- Closed
-
-
Display More
I need help on how to update portainer.
It was installed under openmediavault-compose 6.9 and now the new portainer version is 2.18.4.
Thanks
explained on guide.
basically 2 buttons:
1 - select portainer
2 - use pull buton ( this download new & recent image)
3 - use up button, ( this deploy portainer with latest downloaded image ).
-
Simple and perfect, but only for those who know
Thank you very much.
-
-
Simple and perfect, but only for those who know
You can consult the documentation. https://wiki.omv-extras.org/do…v6_plugins:docker_compose
-
Like many more before me in this thread, I ignored the plugin development (as I just want to have my containerized services running and not be involved in how this is achieved).
First there was the "Install Portainer" button in the OMV GUI to easily update Portainer whenever there was a new version available.
Then, the "Install Portainer" button was gone, but one could still ssh into OMV and use some "omv-salt deploy run omvextras" command to update the Portainer container.
Today I saw the update for Portainer 2.18.4 and realized that this command didn't work either. So, I went to this forum (which I don't frequently visit, only if there are update issues). I was shocked to see 59 pages full of complaints about this change and was frightened beyond belief.
Then I decided to watch the 2.5 minutes video in post #1 and the migration of the old OMV Portainer worked straight away.
BUT: What I don't understand (and I do not want to troll or start some religious wars, I'm just genuinely interested): why the hate for Portainer? I found it to be a quite adequate tool for the task and am wondering why there's so much hate for it.
-
why the hate for Portainer?
There is no hate for Portainer. You just don't need to use it anymore and the plugin has a few extra benefits like backups etc.
Portainer also generates many threads requesting support on its operation that should no longer be needed on this forum. I suppose there will be other more appropriate places to ask these questions, this is an OMV forum. It also doesn't mean that they won't help you if you use Portainer, but it's not our specialty.
But if for any reason you need to continue using Portainer, then go ahead. No one is going to shoot anyone for using Portainer and the plugin doesn't prevent it as you just saw in the video
-
-
Yes, all that is understood, but reading through those 59 pages it sounded like "remove Portainer!" is the mission.
I would have thought that answering questions in the forum with "your issue is a Portainer issue and not an OMV or OMV-extras issue, so please ask that question in the Portainer forums" would have been easier than having to answer the questions "OMV-compose does not work like I expect it ... this is your plugin, please help me" that will come up in the future.
But all good then. Each to their own. OMV-extras developer are happy, I am happy, everyone is happy.
-
First there was the "Install Portainer" button in the OMV GUI to easily update Portainer whenever there was a new version available.
Then, the "Install Portainer" button was gone, but one could still ssh into OMV and use some "omv-salt deploy run omvextras" command to update the Portainer container.This really wasn't the case. There was a testing release that people didn't really like. It would require disabling portainer and then enabling it to get an update. But for a bit more history, there was a docker plugin in OMV 4.x that people really liked but it was a nightmare to maintain and would have been almost impossible to port to OMV 6.x. People were really pissed when I added a portainer button instead of porting the docker plugin.
I was shocked to see 59 pages full of complaints about this change and was frightened beyond belief.
All 59 pages are not complaints. There is a lot of discussion on features to add/fix/change or helping people with the migration.
why the hate for Portainer?
I definitely don't hate portainer. I don't use it (i use command line but am moving to compose plugin) making it harder to maintain it working with OMV. I wouldn't have created a video on how to keep it working and created a couple of portainer example compose files if I hated it. I just wanted to make something OMV native that was simpler. I also wanted something to manage docker that didn't need docker working.
It doesn't work.
would have been easier than having to answer the questions "OMV-compose does not work like I expect it ... this is your plugin, please help me" that will come up in the future.
Since I wrote the compose plugin, I am able to help much easier and change things to avoid questions like that. We also control the documentation to make it very OMV focused. Telling them to go to another forum causes more problems than helping them with a plugin.
-
Yes, all that is understood, but reading through those 59 pages it sounded like "remove Portainer!" is the mission.
Absolutely. Those 59 pages are primarily answers to questions like yours. Users surprised with the change and giving their opinion about it. If you read them you will be able to verify it, but it will be a long and boring read, I guarantee it.
I would have thought that answering questions in the forum with "your issue is a Portainer issue and not an OMV or OMV-extras issue, so please ask that question in the Portainer forums" would have been easier than having to answer the questions "OMV-compose does not work like I expect it ... this is your plugin, please help me" that will come up in the future.
I don't think anyone ever answers that. Support is given here on many topics that are not related to OMV. Before we simply had an "obligation" to solve Portainer problems and now we will only do it because we want to. It is a substancial difference in my opinion.
But all good then. Each to their own. OMV-extras developer are happy, I am happy, everyone is happy.
So what is the problem? You see it? Your two questions in this thread have only been one more opinion. That's why it's so long.
Can you imagine how many OMV users use docker? -
-
Absolutely. Those 59 pages are primarily answers to questions like yours. Users surprised with the change and giving their opinion about it. If you read them you will be able to verify it, but it will be a long and boring read, I guarantee it.
I read all 59 of them prior to posting.
So what is the problem?
As long as I can still use Portainer (because the new plugin does not offer the options I need), I do not have any problem.
-
I read all 59 of them prior to posting.
haha
As long as I can still use Portainer (because the new plugin does not offer the options I need), I do not have any problem.
I could never stop you from using portainer. You can install docker and portainer from the command without any omv-extras at all.
Out of curiosity, what options do you need?
-
I read all 59 of them prior to posting.
Oh really?! You must be a person with inexhaustible patience.
-
-
haha
That was no joke.
Out of curiosity, what options do you need?
Deploy stack from Github repository.
-
Deploy stack from Github repository.
You could easily cut & paste the compose file from the github repo into a new file. I release this is a few extra steps but not a reason to force you to keep using portainer. I could see adding to the plugin the ability to create a new compose file given the url. The plugin is basically doing that now for the Add Example.
-
You could easily cut & paste the compose file from the github repo into a new file.
But I would have to do that (copying&pasting) over and over again for the same stack whenever it is updated on Github. Portainer just pulls the latest version from Github, updates and deploys accordingly.
-
-
Portainer just pulls the latest version from Github, updates and deploys accordingly.
Am I thick or that's exactly what "pull" command does?
-
Am I thick or that's exactly what "pull" command does?
You are talking about "pull latest image". I'm talking about "pull latest stack yml from github and pull whole stack".
-
You are talking about "pull latest image". I'm talking about "pull latest stack yml from github and pull whole stack".
OMV GUI-> Services-> Compose-> Files-> Create
Make a Portainer Container
Log in via http://LAN_IP:9000
Do what you need on portainer as you did before.
No, you won't have a button as before on the omv-extras.
So?!?
-
-
But I would have to do that (copying&pasting) over and over again for the same stack whenever it is updated on Github. Portainer just pulls the latest version from Github, updates and deploys accordingly.
If you are using a compose file that changes that often, it is not a good image maintainer. The image might change often but the compose file shouldn’t.
-
Display More
OMV GUI-> Services-> Compose-> Files-> Create
Make a Portainer Container
Log in via http://LAN_IP:9000
Do what you need on portainer as you did before.
No, you won't have a button as before on the omv-extras.
So?!?
That’s what he did? Why so aggro?
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!