omv-extras 6.3 / openmediavault-compose 6.7

ryecoaaron · May 29th 2023

I just released a new version of openmediavault-omvextrasorg 6.3 and openmediavault-compose 6.7.

IF YOU DON'T UNDERSTAND DOCKER WELL, WAIT to FOLLOW THESE DIRECTIONS UNTIL THEY ARE IMPROVED!!!

The docker, portainer, and yacht installs have been removed from omvextras. You will only enable the docker repo in omv-extras now.
The docker install has been added to the openmediavault-compose plugin.
If you were using portainer created by omv-extras, you should be able to use the "add example" option the Files tab of the compose plugin to add a portainer compose file using the portainer-omvextras example. This will reuse the existing portainer_data volume. You will need to do a docker container stop portainer and docker container rm portainer first.
The "Reinstall Docker button on the Settings tab of the compose plugin will install docker and docker-compose (This is only needed if docker is not installed).

All of this was done since the docker stuff did not belong in omv-extras in my opinion. And while I think the compose plugin replaces portainer nicely, I think moving people to using portainer with a docker-compose file is better than me maintaining a config that was not very flexible (lots of people asking for customizations).

Guide to help with migration - Guide: Using the new docker plugin

Wiki - How to Recover containers after updating omv-extras - https://wiki.omv-extras.org/do…openmediavault-compose_67

Docker guide - https://wiki.omv-extras.org/doku.php?id=omv6:docker_in_omv

quick video on moving portainer to compose plugin

External Content youtu.be

Content embedded from external sources will not be displayed without your consent.

Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

Helpful tips

On the Files tab:

up is the same as start and will start all containers in the compose file. it will also use new image(s) if new image(s) were pulled.
stop is stop and will stop all containers in the compose file
down will stop and remove all containers in the compose file
pull will try to pull new images for all containers in the compose file

On the Services tab:

pull will try to pull a new image for only the selected container
up will start the selected container and use a new image if a new image was pulled
restart will only restart the selected container

On the Containers tab:

restart will only restart the selected container. This is the same as the Services tab restart but can restart a container that is not maintained by the plugin

fbeye · May 29th 2023

So, unless I mistake your meaning..... As long as directories are accurate, which i can not believe they'd change, by reinstalling the portainer template, everything else under it will re-activate? Or will I need to reinstall every container I had?

Gah!!!!

docker start "Any Container I try"

Error response from daemon: unknown or invalid runtime name: nvidia

Error: failed to start containers: "Any Container I try"

What I did;

Cause I have had great success with updates, I updated this morning then went to work. Got to work everything still worked... I then noticed the thread and my heart sunk. All I did thus far was update the docker directory from var to /src/disk-id/docker and then installed the Portainer Template, no other containers. Rebooted and that is where I am at.

G3n3r0s0 · May 29th 2023

Hi, thanks for providing the plugin, this solution is better indeed!

Just I couple of things I noticed:

1. I use a custom Docker storage folder, I had to enter it again.

2. The "Docs" in Files is landing in "https://wiki.omv-extras.org/doku.php?id=omv6:omv6_plugins:compose", while the URL is "https://wiki.omv-extras.org/doku.php?id=omv6:omv6_plugins:docker_compose"

fbeye · May 29th 2023

Where was Portainer set at before on the drive? Cuase when I import the omv-extras portainer, it reinstalls itself to my NAS drive location, I mean it was not there before! How did it even find that directory?

fbeye · May 29th 2023

Well I done F'd it up.

jorensanbar · May 29th 2023

I have this error always.

Oddies · May 29th 2023

Quote from jorensanbar

I have this error always.

Same!

chente · May 29th 2023

Quote from jorensanbar

I have this error always.

Have you set a shared folder in the plugin configuration to store the container configuration files?

check this https://wiki.omv-extras.org/do…s:docker_compose#settings

kelinjone · May 29th 2023

Quote from jorensanbar

I have this error always.

same error,I will lose my portainer?

olduser · May 29th 2023

Can we still restart individual containers from the GUI?

chente · May 29th 2023

Quote from olduser

Can we still restart individual containers from the GUI?

Yeah. In the containers tab, restart button. https://wiki.omv-extras.org/do…ns:docker_compose#restart

Oddies · May 29th 2023

Quote from kelinjone

same error,I will lose my portainer?

Mine still somehow works. I have Portainer running my Jellyfin server from before the update within OMV6, can't see any info on their status anywhere in the OMV6 GUI but when accessing both through their own web addresses they work fine.

This whole update is a mess, followed the instructions supplied here but I get the "500 - internal server error" every time

Code

(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-uuid-xxxxxxxxxxxx/Config Containers//portainer1/portainer1.yml' --env-file '/srv/dev-disk-by-uuid-xxxxxxxxxxxxxx/Config Containers//portainer1/portainer1.env' pull 2>&1': Couldn't find env file: /srv/dev-disk-by-uuid-xxxxxxxxxxxxxxxxx/Config Containers/portainer1/portainer1.env).

Can't import containers from existing ones and can't create new ones from examples. Does anyone know how to roll back to the perfectly working version that wasn't a complete fail?

chente · May 29th 2023

Quote from Oddies

Mine still somehow works. I have Portainer running my Jellyfin server from before the update within OMV6, can't see any info on their status anywhere in the OMV6 GUI but when accessing both through their own web addresses they work fine.

Portainer doesn't run any container, the container runs itself. Portainer is just a tool to make configurations in the container.

I haven't had time to test this change yet. But following ryecoaaron 's instructions:

Quote from ryecoaaron

If you were using portainer created by omv-extras, you should be able to use the "add example" option the Files tab of the compose plugin to add a portainer compose file using the portainer-omvextras example. This will reuse the existing portainer_data volume.

there should be a sample file called "portainer-omvextras" which I assume ryecoaaron included to get Portainer back to the same state as before.

The access button is this. https://wiki.omv-extras.org/do…_compose#add_from_example

Just select that portainer-omvextras yaml file and deploy the Portainer container.

chente · May 29th 2023

Quote from Oddies

Code

(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-uuid-xxxxxxxxxxxx/Config Containers//portainer1/portainer1.yml' --env-file '/srv/dev-disk-by-uuid-xxxxxxxxxxxxxx/Config Containers//portainer1/portainer1.env' pull 2>&1': Couldn't find env file: /srv/dev-disk-by-uuid-xxxxxxxxxxxxxxxxx/Config Containers/portainer1/portainer1.env).

If I'm not mistaken, this error is because you have not configured a folder as I said in post #8

chente · May 29th 2023

Quote from Oddies

I have Portainer running my Jellyfin server from before the update within OMV6

~~In any case, what I would do is take advantage of all this to stop using Portainer. You only need to have your Jellyfin yaml configuration file.~~

~~1. Stop the Jellyfin container, you should be able to do it from the openmediavault-compose GUI, even though it was created with Portainer.~~

~~2. Purge the container. Persistent data will still be where you had it.~~

~~3. Deploy the container in openmediavault-compose with your yaml file and initialize it.~~

~~The Jellyfin container should be working exactly the same as before and you can now manage it from the plugin, you no longer need Portainer.~~

EDIT: This doesn't work, the containers still don't show up in the GUI, read the following posts later.

jorensanbar · May 29th 2023

Everything in the "manual" has already been done.

- The shared folder was assigned.

- The compose was created with the portainer-ovmextras

- The server has been restarted.

And there is simply no way to recover the original Portainer container (Status).

This has been by far the worst update or "improvement" that OMV has received.

Not to mention that now you have to always have sharerootfs active, and keep a shared folder created that will never be used other than enabling a path to store the docker-compose files.

Quote from chente

Just select that portainer-omvextras yaml file and deploy the Portainer container.

chente · May 29th 2023

Quote from jorensanbar

And there is simply no way to recover the original Portainer container (Status).

It gives you an error because you still have the old container running.

As long as there is a running container named portainer you cannot create another with the same name. To give a solution I would have to try it before, but as I said I haven't had the chance yet. You will have to wait for a better answer than mine.

chente · May 29th 2023

Quote from jorensanbar

And there is simply no way to recover the original Portainer container (Status).

okay. Fortunately I had a vm with the perfect conditions to test this and was able to test it.

The error is what I said before, first you need to kill the running portainer container.

The solution is the next:

Stop the Portainer container

docker stop portainer

Delete the portainer container

docker rm portainer

Follow ryecoaaron 's instructions. Implement the portainer-omvextras sample container. Portainer will now be in its initial state.

I got various errors during the installation process etc. This is normal, just Ctrl+shift+R fixes it.

Quote from jorensanbar

This has been by far the worst update or "improvement" that OMV has received.

As a simple answer to this, I can only say that big changes are generally not welcomed. But in the long run they are always very grateful. We'll see in a while.

Oddies · May 29th 2023

Quote from chente

In any case, what I would do is take advantage of all this to stop using Portainer. You only need to have your Jellyfin yaml configuration file.

1. Stop the Jellyfin container, you should be able to do it from the openmediavault-compose GUI, even though it was created with Portainer.
2. Purge the container. Persistent data will still be where you had it.
3. Deploy the container in openmediavault-compose with your yaml file and initialize it.

The Jellyfin container should be working exactly the same as before and you can now manage it from the plugin, you no longer need Portainer.

Display More

In Services/Compose/Containers I have 0 containers shown even though Portainer and Jellyfin are running and can be accessed via their web UI. The only place where they are shown anywhere in OMV6's GUI is in Services/Compose/Stats.

When I try to create the new Jellyfin instance under Services/Compose/File/Create (+ insert my verbatem Jellyfin config from Portainer) I get the 500 internal server error again. For whatever reason this new setup doesn't want to acknowledge the shared folder I created, referenced and made available as an SMB/CIFS share in the relevant sections of the OMV6 GUI.

Just to be clear, if I go to Services/Compose/Settings/Shared Folder I can see my folder that I created per the initial instructions earlier today. The same folder is also visible in Storage/Shared Folders and in Services/SMB/CIFS/Shares. Funnily enough it hasn't populated yet in my Windows Network share where I can see the rest of the folders OMV has access to.

chente · May 30th 2023

Quote from Oddies

In Services/Compose/Containers I have 0 containers shown even though Portainer and Jellyfin are running and can be accessed via their web UI. The only place where they are shown anywhere in OMV6's GUI is in Services/Compose/Stats.

TRUE. You're right, that post is a bug, I shouldn't have posted anything until I tested it. The containers do not appear in the GUI because they have not been created in the GUI.

Follow the instructions in post 18 to recover portainer.

At that time you will have everything as before. If you want to get rid of portainer now I will post the procedure, give me 10 minutes, I want to test it before posting.

Participate now!