omv-extras 6.3.1 is in the repo now. It adds a link to the wiki and adds a hint to the docker checkbox that you need the openmediavault-compose plugin for docker functionality.
The wiki also links to this thread.
omv-extras 6.3.1 is in the repo now. It adds a link to the wiki and adds a hint to the docker checkbox that you need the openmediavault-compose plugin for docker functionality.
The wiki also links to this thread.
I'm trying to follow the guide in the wiki to install docker correctly with the new system but this step does not seem to work as described:
omv extra does not have a drop down menu
I'm getting the connection lost issue when i try to install the compose plugin. I think it may have also said this when I installed extras update that just came out too. I was too quick to close the window. Anyhow when I tried to install the compose plugin I get this:
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 58650 files and directories currently installed.)
Preparing to unpack .../openmediavault-compose_6.7.4_all.deb ...
Unpacking openmediavault-compose (6.7.4) over (6.7.4) ...
Setting up openmediavault-compose (6.7.4) ...
Updating configuration database ...
Processing triggers for openmediavault (6.4.0-3) ...
Updating workbench configuration files ...
** CONNECTION LOST **
█
My journal has a bunch of messages about omv-engined process not stopping during restart.
I got omv-engined restarted and then the install worked. Was the portainer installer removed?
I got omv-engined restarted and then the install worked. Was the portainer installer removed?
yes portainer installer was removed
I'm trying to follow the guide in the wiki to install docker correctly with the new system but this step does not seem to work as described:
4. Install Docker and openmediavault-compose plugin
- In the OMV GUI, go to the System > omv-extras > Docker
- In the Docker storage field replace the value with the path of the docker folder created earlier, and press the Save button.
omv extra does not have a drop down menu
Docker has changed just yesterday.... Look in the Guides section on "How to use the new docker plugin".
Yes, it's better. Read publication 1 of this thread, ask your questions.
Ok, thank you, I'm trying with a container, but it doesn't seem so easy, I followed these steps:
1- got a docker-compose yaml file by running:
docker run --rm -v /var/run/docker.sock:/var/run/docker.sock red5d/docker-autocompose transmission-openvpn
2- I stopped and deleted docker with:
docker container stop transmission-openvpn
docker container rm transmission-openvpn
3- I pasted the yaml file content into Compose/Files/Create/File but got the error:
500 - Internal ServerError
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker-compose --file '/srv/dev-disk-by-label-REDRAID4X12/compose//transmission-openvpn/transmission-openvpn.yml' --env-file '/srv/dev-disk-by-label- REDRAID4X12/compose//transmission-openvpn/transmission-openvpn.env' up -d 2>&1': failed to read /srv/dev-disk-by-label-REDRAID4X12/compose/transmission-openvpn/transmission-openvpn.env : line 8: key cannot contain a space
4- I then tried to create the stack from Portainer with the same yaml file, but I got this error:
Deployment error
failed to deploy a stack: Container transmission-openvpn Creating Error response from daemon: network-scoped alias is supported only for containers in user defined networks
Where am I wrong? My goal is, if possible, to transfer my two created Containers directly into Portainer under OMV Compose.
Thank you.
I'm trying to follow the guide in the wiki to install docker correctly with the new system but this step does not seem to work as described:
4. Install Docker and openmediavault-compose plugin
In the OMV GUI, go to the System > omv-extras > Docker
In the Docker storage field replace the value with the path of the docker folder created earlier, and press the Save button.omv extra does not have a drop down menu
The docker docs on the wiki are up to date.
omv6:omv6_plugins:docker_compose [omv-extras.org]
omv6:docker_in_omv [omv-extras.org]
I believe I have included all of the performance changes, though I may have unintentionally omitted some.
I know that there are currently many people consulting these documents. I would appreciate any suggestions to improve the comprehension or the writing of the documents, English is not my native language.
ryecoaaron please can you create a little link button like KVM or something so you can click it like in Portainer and it'll open up your containers web UI?
Like SABnzbd or whatever, log into OMV, click the button and it opens in a new page, in case we forget the port or what not?
ryecoaaron please can you create a little link button like KVM or something so you can click it like in Portainer and it'll open up your containers web UI?
Like SABnzbd or whatever, log into OMV, click the button and it opens in a new page, in case we forget the port or what not?
I was wondering that yesterday. In Portainer, you could click the port link, and it would take you to the container.
Alles anzeigenOk, thank you, I'm trying with a container, but it doesn't seem so easy, I followed these steps:
1- got a docker-compose yaml file by running:
docker run --rm -v /var/run/docker.sock:/var/run/docker.sock red5d/docker-autocompose transmission-openvpn
2- I stopped and deleted docker with:
docker container stop transmission-openvpn
docker container rm transmission-openvpn
3- I pasted the yaml file content into Compose/Files/Create/File but got the error:
Code500 - Internal ServerError Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker-compose --file '/srv/dev-disk-by-label-REDRAID4X12/compose//transmission-openvpn/transmission-openvpn.yml' --env-file '/srv/dev-disk-by-label- REDRAID4X12/compose//transmission-openvpn/transmission-openvpn.env' up -d 2>&1': failed to read /srv/dev-disk-by-label-REDRAID4X12/compose/transmission-openvpn/transmission-openvpn.env : line 8: key cannot contain a space
4- I then tried to create the stack from Portainer with the same yaml file, but I got this error:
CodeDeployment error failed to deploy a stack: Container transmission-openvpn Creating Error response from daemon: network-scoped alias is supported only for containers in user defined networks
Where am I wrong? My goal is, if possible, to transfer my two created Containers directly into Portainer under OMV Compose.
Thank you.
It's complaining about a spaces in the -env file... Are you pasting a docker-compose?
When you paste it in the file.. There's two boxes, 1 on top, 1 on bottom. The top one is for a stack/docker-compose. The bottom one is for an environment file. If you're just using a compose... Delete the file, create a new one and make sure you paste it at the top.
Save/Apply, then Deploy
I moved haugene/transmission no problem yesterday.
Added in the docker-compose wiki document the procedure:
How to recover Portainer and other containers from versions prior to omv-extras 6.3 / openmediavault-compose 6.7
Added in the docker-compose wiki document the procedure:
How to recover Portainer and other containers from versions prior to omv-extras 6.3 / openmediavault-compose 6.7
I think I have not made any mistakes, but this has been done with little time. I would appreciate if those of you who know the procedure review it just in case, please.
1- got a docker-compose yaml file by running:
How did you create that container? Don't have a yaml file? Autocompose is not ideal for this process.
Added in the docker-compose wiki document the procedure:
How to recover Portainer and other containers from versions prior to omv-extras 6.3 / openmediavault-compose 6.7
Thank you very much for this addition. This is very helpful and will hopefully mitigate the stress for OMV hobby admins (regarding as it was noted in this post (average users, majority of user etc.: RE: omv-extras 6.3 / openmediavault-compose 6.7) with this upgrade or improvement.
Thank you very much for this addition. This is very helpful and will hopefully mitigate the stress for OMV hobby admins with this upgrade or improvement.
You're welcome, I hope so too.
How did you create that container? Don't have a yaml file? Autocompose is not ideal for this process.
I created it directly inside Portainer, so I don't have a yaml file.
Alles anzeigenIt's complaining about a spaces in the -env file... Are you pasting a docker-compose?
When you paste it in the file.. There's two boxes, 1 on top, 1 on bottom. The top one is for a stack/docker-compose. The bottom one is for an environment file. If you're just using a compose... Delete the file, create a new one and make sure you paste it at the top.
Save/Apply, then Deploy
I moved haugene/transmission no problem yesterday.
Ok, thanks, I succeeded. but I had to delete the following lines, otherwise I was getting an error:
I'll also try to move my lscr.io/linuxserver/plex in a while. Thank you.
What can I say, JUST LOVE IT!!!!!!!!!!
ryecoaaron
Thank you for taking this move.
Me and chente had spoke with you that this was the way to go and people will have to accept it and evolve with it.
I'm not a good example since I was already using the compose plugin for a long time.
But the update was just that, an update. No issues:
And this is what people will have in the end:
I do love simplicity,
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!