please do not add more complexity to pluging wait some weeks to user understood well how it works.
omv-extras 6.3 / openmediavault-compose 6.7
-
- OMV 6.x
- ryecoaaron
- Closed
-
-
please do not add more complexity to pluging wait some weeks to user understood well how it works.
People literally only need to use the Settings and Files tabs - maybe the Services tab for the links - and can ignore all of the other tabs. Portainer still has much more complexity and people don't seem to be bothered by that.
And I work on things when I have time. I might not have any time in a couple of weeks. That said, we were just kicking around ideas.
-
Sorry for my newbieness, but which is the way to update (pull latest) portainer image now? I see the option is gone in omv-extras tab.
Thanks in advance.
-
-
Sorry for my newbieness, but which is the way to update (pull latest) portainer image now? I see the option is gone in omv-extras tab.
Thanks in advance.
only need to select portainer in files, use button pull ( to pull latest image), and once done, use button UP ( to restart container with recent downloaded image)
-
which is the way to update (pull latest) portainer image now? I see the option is gone in omv-extras tab.
Portainer is just another container, nothing differentiates it from the others. So the procedure is the same as for any other container.
-
only need to select portainer in files, use button pull ( to pull latest image), and once done, use button UP ( to restart container with recent downloaded image)
Thank you.
But it seems I have to set a "shared folder" first, I got an error in webui once I access the folder section. I will look for some tutorial.
Portainer is just another container, nothing differentiates it from the others. So the procedure is the same as for any other container.
Thank you.
But I cannot stop and recreate it by pulling latest image from portainer menu itself (the options are greyed out), which is the way I update all the other containers. I guess it it because if I stop it, the webui will be lost and I could not recreate it from the webui, so it makes sense. Before the change to omv-extras it was pretty straightforward to update it by clicking on install portainer from OMV menu.
Maybe I could do via cli, and the previous image and options are maintained?:
Code$ docker stop portainer $ docker rm portainer $ docker pull portainer/portainer-ce -
-
I will look for some tutorial.
There is a 2.5 min video on the first post of this thread that shows you what you need.
-
So I only just noticed this happened xD
It wasn't too bad, I was using stacks in Portainer so I simply recreated them in the Compose / Files tab, then I removed and redeployed the containers using the same volumes so zero dataloss.
ryecoaaron thank you for the video, it showed me all I need to know to figure out the rest by myself.
What is the quickest way to update my container each time there is a new Plex update for example?
-
What is the quickest way to update my container each time there is a new Plex update for example?
Select the File and click Pull then Up.
-
-
Ah I think I understand better now
Pull = Downloads latest image
Up = Stop, then Delete container and recreate from downloaded image
Stop = Just stop container
Down = Stop and Delete Container
-
Ah I think I understand better now
I will add the info from this post to the first post but pretty sure that stuff is in the wiki.
-
Please excuse the stupid question, but is it mandatory to have to do this? Will future updates to OVM prevent the way I currently have Docker and Portainer setup? I understand it is to have everything in one place, but I am just curious before I attempt to do any changes as everything is working as is. No disrespect is intended ryecoaaron, just trying to understand it all.
-
-
is it mandatory to have to do this?
Nope.
Will future updates to OVM prevent the way I currently have Docker and Portainer setup?
OMV didn't do anything. All I did is move the docker install from omv-extras to the compose plugin. I posted a 2.5 min video on the first post of this thread of how to move from the omv-extras install of portainer to the compose plugin install of portainer.
I understand it is to have everything in one place, but I am just curious before I attempt to do any changes as everything is working as is.
I think if you watched the video and do what I did in the video, you wouldn't be so dead set on staying with the old setup. If you don't delete your volumes, you can't lose any data. Portainer runs things with docker-compose just like the plugin. Portainer just calls it a stack. You are just changing the place you initiate it. Once you initiate a docker-compose in the plugin or portainer, neither one does anything with it again.
No disrespect is intended ryecoaaron, just trying to understand it all.
I don't take it that way. I just don't understand the reluctance to change. For most people, they are just moving to a different up/start and pull button since they are using stacks in portainer which is the same the plugin.
-
I managed to do the "migration" of Portainer to the compose plugin without any major issues, thanks for the instructions.
I don't take it that way. I just don't understand the reluctance to change. For most people, they are just moving to a different up/start and pull button since they are using stacks in portainer which is the same the plugin.
I'm wondering if these kinds of changes would be better received by the users if they were communicated a little better.
Yesterday I let my OMV machine update everything and I just happened to feel like also updating Portainer in the meantime, so I immediately found out the feature I always used to do that with is gone. And because OMV is... well, OMV, my first thought wasn't that an update changed something - my first thought was that an update broke something. It is only after checking these forums when I noticed there was an intended change done in omv-extras.
If I were not to update Portainer now, and in the future I were forced to update Portainer for one reason or another, I could see myself get a little annoyed that there's no trace left from the "Install Portainer" button I've been used to seeing/using for a while. You know the feeling when you're trying to fix one sudden problem but suddenly you have to also try to figure out another one on the way?
I think if there was some sort of notification inside the omv-extras settings page about the features being (re)moved along with a link to this thread, less people would be complaining about it. Even better if the plugin could perform the migration for you, maybe only asking you where to create that shared folder for compose, but I understand time put into developing a free plugin is very precious, so I'm keeping my expectations in check
-
If I were not to update Portainer now, and in the future I were forced to update Portainer for one reason or another, I could see myself get a little annoyed that there's no trace left from the "Install Portainer" button I've been used to seeing/using for a while. You know the feeling when you're trying to fix one sudden problem but suddenly you have to also try to figure out another one on the way?
Don't forget that Portainer is just another container, just like the rest. In the wiki you have information on how to update any container, it is very simple.
if there was some sort of notification inside the omv-extras settings page about the features being (re)moved along with a link to this thread
That seems like a good suggestion.
-
-
Just to make the post number 1000
-
Don't forget that Portainer is just another container, just like the rest. In the wiki you have information on how to update any container, it is very simple.
Yeah, but I'm someone who still struggles with dealing with Docker and its concepts, so 99% of my Docker work relies directly on Portainer, I'm not comfortable with Docker CLI at all. And it just so happens the Portainer container cannot be updated from within Portainer
Even if there's a wiki page saying how to do it command by command, there was still a much simpler and safer way to do it, and it being suddenly gone can totally cause bad reactions from people IMO.My bad, I thought you were referring to some way of doing it before this omv-extras update. Yeah, I'm aware of that method now, the helpful tips in the first post guided me towards it. And I don't mind that method at all.
-
Yeah, but I'm someone who still struggles with dealing with Docker and its concepts, so 99% of my Docker work relies directly on Portainer, I'm not comfortable with Docker CLI at all. And it just so happens the Portainer container cannot be updated from within Portainer
You don't need to use CLI at all. Just plugin GUI and push two buttons. Before you only pressed a button, the difference is that nothing more.
Have you read the procedure? https://wiki.omv-extras.org/do…_docker-compose_yaml_file
-
-
Yeah, but I'm someone who still struggles with dealing with Docker and its concepts, so 99% of my Docker work relies directly on Portainer, I'm not comfortable with Docker CLI at all. And it just so happens the Portainer container cannot be updated from within Portainer
My recommendation is that when you have 20 minutes of time, follow these steps and get rid of Portainer. https://wiki.omv-extras.org/do…openmediavault-compose_67
-
Even if there's a wiki page saying how to do it command by command, there was still a much simpler and safer way to do it
Sorry, but I disagree. The way to do it is just as simple and just as safe.
The first time you upgraded Portainer from the previous version you had to search or ask how to upgrade Portainer, until you learned that the procedure was to push a button.
Now the procedure is to press two buttons that are elsewhere, you just have to find them.
I understand the annoyance that you are forced to take new procedures. But you must also understand that software evolves. This step is simply one more evolution.
When OMV7 arrives you will also be forced to learn new procedures. Can we expect the same reaction from you? I suppose you have assumed that this will come and you will have no choice but to do it if you want to have your server updated.
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!