omv-extras 6.3 / openmediavault-compose 6.7
-
- OMV 6.x
- ryecoaaron
- Geschlossen
-
-
How wud I add Containers to this?
Create a compose file for them.
-
Since it is implemented in YACHT. You can update containers from the program interface.
If you select a compose file in Files and click Pull, it will download new images if available for every image in the compose. Then you click Up and it will recreate any container that has a new image. This is all functionality built-in to docker-compose.
-
-
Create a compose file for them.
Will do and can I just create one big Stack for the whole lot?
-
If you select a compose file in Files and click Pull, it will download new images if available for every image in the compose. Then you click Up and it will recreate any container that has a new image. This is all functionality built-in to docker-compose.
It's clear. But it is convenient to have a common button for all containers and an icon that would indicate that the container has updates. Inconvenient to go into each container and check for updates
-
Will do and can I just create one big Stack for the whole lot?
I wouldn't. If the containers aren't related, I would create a compose for each.
-
-
I wouldn't. If the containers aren't related, I would create a compose for each.
Ok cool will read up on how to make a compose file for them. So wud u suggest creating a Stack for every Container I have? But I sud use the Stacks to do this and deploy so that I can add to OMV right?
-
-
So wud u suggest creating a Stack for every Container I have?
Yes. stack is the portainer name for compose file.
But I sud use the Stacks to do this and deploy so that I can add to OMV right?
Up to you. The idea of the compose plugin is not need portainer though.
-
-
Yes. stack is the portainer name for compose file.
Up to you. The idea of the compose plugin is not need portainer though.
Im trying to find the easiest way to make Compose files from my single Containers that are running but cant work this out - A little advanced for me and dont want to muck up what I have running. Is there a simple program or way to take the information in the Container and put it into a Stack/Editor Compose file
-
Hi,
I just moved all my containers from portainer to the new compose-plugin.How can I move the portainer itself with ports, mapped direcotry etc.?
-
Im trying to find the easiest way to make Compose files from my single Containers that are running but cant work this out - A little advanced for me and dont want to muck up what I have running. Is there a simple program or way to take the information in the Container and put it into a Stack/Editor Compose file
You can try it with Autocompose.
-
-
Is there a simple program or way to take the information in the Container and put it into a Stack/Editor Compose file
Not that I know of. Did you look to see if there is already an Example in the Files tab that is for the image you want to convert? If not, you could start with one of the examples and modify it for the image you want to convert.
-
How can I move the portainer itself with ports, mapped direcotry etc.?
If all of your stacks/containers are in the plugin, you shouldn't need or really even use portainer.
-
Not that I know of. Did you look to see if there is already an Example in the Files tab that is for the image you want to convert? If not, you could start with one of the examples and modify it for the image you want to convert.
In my Files tab there is nothing. Im first trying to move across jc21/nginx-proxy-manager:latest version. As that runs my reverse proxy stuff
-
-
In my Files tab there is nothing. Im first trying to move across jc21/nginx-proxy-manager:latest version. As that runs my reverse proxy stuff
Crate new:
Code
Alles anzeigenversion: '3.8' services: nginx-proxy-manager: image: jc21/nginx-proxy-manager:latest container_name: nginx-pm volumes: - /docker/nginx-proxy-manager/data:/data - /docker/nginx-proxy-manager/letsencrypt:/etc/letsencrypt ports: - 80:80 - 81:81 #WebUI Тут если чё можно зайти и порулить - 443:443 #- 21:21 # FTP restart: unless-stopped
-
Crate new:
Code
Alles anzeigenversion: '3.8' services: nginx-proxy-manager: image: jc21/nginx-proxy-manager:latest container_name: nginx-pm volumes: - /docker/nginx-proxy-manager/data:/data - /docker/nginx-proxy-manager/letsencrypt:/etc/letsencrypt ports: - 80:80 - 81:81 #WebUI Тут если чё можно зайти и порулить - 443:443 #- 21:21 # FTP restart: unless-stopped
Thank you for that - Does the Container name need to be the same as I have it in Portainer for it to work on OMV? Also what is the additional ports:21:21 FTP - I dont have this so can I remove?
-
If all of your stacks/containers are in the plugin, you shouldn't need or really even use portainer.
I know but some debugging things seem to be easier in portainer, like jumping into the console for a container or viewing logs with live updates.
Anyway I followed the instructions in the Docu, and seems like everything works. Just had to adjust the port, I think that was the only thing that could have been adjusted in the old OMV GUI.
Not sure why the post with the link to the Docu dissapeared
-
-
Thank you for that - Does the Container name need to be the same as I have it in Portainer for it to work on OMV? Also what is the additional ports:21:21 FTP - I dont have this so can I remove?
The name may be the same. You need to stop the container at Portainer
ports:21:21 FTP - I dont have this so can I remove? Commented out. Can be deleted -
The name may be the same. You need to stop the container at Portainer
ports:21:21 FTP - I dont have this so can I remove? Commented out. Can be deletedCool - so stop the container/stack in Portainer - then create in OMV.
Names have to be the same
Then do Portainer last
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!