omv-extras 6.3 / openmediavault-compose 6.7

Quote from ryecoaaron

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

Display More

Oh no!

Eventually, I finished my services configuration via docker and Portainer last week. So proud of me!

Yesterday I updated without thinking twice

Happy to know that I have to study something new, but would it be possible to add few lines, just the more important changes, in the interface, near each update element?

I would just say: appreciate the changes on the plugin.

forced me to clean up my docker-installation. And after some fiddling with config-files and installation-paths (deleting portainer, as well) everything works with the compose-plugin. great thing!

makes backup so easy, now...

So, if someone still struggles with hidden containers, maybe worth reading:

Post

Somewhere I did screw up the new update, need some assist, please...

Hello guys and girls,

So I did the last update and find out, that there were some changes with the Extras, Docker, Portainer and such.

I have done some of the described steps, but as I see now, maybe not in the right order or so, and now I'm stuck.
No hurry, everything still works, but the move from Portainer to Compose plugin is not finished and I don't know, how to.

So, I have this:

Running OMV last version.
Running Docker and Compose plugin:

forum.openmediavault.org/wsc/index.php?attachment/30209/

…

BebeMischa

Jun 1st 2023

I just got it sorted...

Quote from ryecoaaron

Do you see any containers in the Stats tab? What is the full path of the shared folder you set on the Settings tab? You can find in the Storage -> Shared Folders tab in the Absolute Path column (may need to make it visible). Also, what is the output of:

dpkg -l | grep -E "openme|docker"

Yes, I see the running containers listed in the stats tab and can view the logs and inspect without issue.

root@storage:~# dpkg -l | grep -E "openme|docker"

ii docker-ce 5:24.0.2-1~debian.11~bullseye amd64 Docker: the open-source application container engine

ii docker-ce-cli 5:24.0.2-1~debian.11~bullseye amd64 Docker CLI: the open-source application container engine

ii docker-compose 1.25.0-1 all Punctual, lightweight development environments using Docker

ii docker-compose-plugin 2.18.1-1~debian.11~bullseye amd64 Docker Compose (V2) plugin for the Docker CLI.

rc omvextras-unionbackend 5.0.2 all union filesystems backend plugin for openmediavault

ii openmediavault 6.4.0-3 all openmediavault - The open network attached storage solution

ii openmediavault-compose 6.7.6 all OpenMediaVault compose plugin

ii openmediavault-kernel 6.4.8 all kernel package

ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive

ii openmediavault-mergerfs 6.3.7 all mergerfs plugin for openmediavault.

ii openmediavault-omvextrasorg 6.3.1 all OMV-Extras.org Package Repositories for OpenMediaVault

ii openmediavault-sharerootfs 6.0.2-1 all openmediavault share root filesystem plugin

ii openmediavault-snapraid 6.1 all snapraid plugin for OpenMediaVault.

ii python3-docker 4.1.0-1.2 all Python 3 wrapper to access docker.io's control socket

ii python3-dockerpty 0.4.1-2 all Pseudo-tty handler for docker Python client (Python 3.x)

Thanks.

Quote from ryecoaaron

I would uninstall the docker-compose package (not the docker-compose-plugin package)

sudo apt-get purge docker-compose

Thank you. It's now working since removing the docker-compose package.

Hi, I'm experiencing an issue with keeping nvidia runtime properly set in `/etc/docker/daemon.json`. Everytime I apply any change in the Compose gui in OMV, the daemon.json file gets reset and removes nvidia runtime section.

Here is how I set it up

{
  "data-root": "/DOCKER/system/",
  "runtimes": {
        "nvidia": {
            "path": "nvidia-container-runtime",
            "runtimeArgs": []
        }
    }
}

But it gets reset whenever I apply changes.

First I would like to thank you for your efforts in developing omv-extras plugins.

I have a question about new version of the compose plugin, if I understand correctly, i can use compose plugin to install docker and use portainer to manager docker just like older omv-extras version

Quote from chente

You have a document here that explains all the buttons and how to use the plugin.

https://wiki.omv-extras.org/do…v6_plugins:docker_compose

Actually this plugin and this document are not recent. The plugin is already a year old and everything is updated regularly.

Yeah, I know that if I open google and search for "openmediavault changelog" or "openmediavault-omvextrasorg changelog" I can find everything and get prepared to major changes, but I don't thing that few notes inside the interface, or at least a link to the changelog file, would require such a great effort. It would help reduce critical situations. Here is a stupid case: all containers are running and working, nothing happened basically. But again, few lines would help out lazy people

here is what I mean:

Quote from chente

You have a button to show the changes of each update before applying it.

Thanks! I just discovered a new function!

anyway, having that inside the box of the single update would improve the UX, giving the possibility to scroll all the updates with the changes in sights. In this way the user has to click for every item in the list

One feature I really like in portainer is the update the stack feature to repull all containers and restart. Is there an easy way to achieve this in the new interface? I'm wary of using something like watchtower which might do it unattended.

steve

Quote from ryecoaaron

Select the compose file

Click Pull

Click Up

Nice, I haven't switched yet, but this is one of the few things i really use in portainer so I'll start the switchover. Thanks!

Quote from ryecoaaron

You leave the path blank in the settings tab if you need to customize daemon.json.

Alright, I will test that.

Quote from midisama

Alright, I will test that.

After reading this I noticed that installing the compose plugin picked up my path and overwrote my daemon.json. Was the old one stashed somewhere? I'm not sure I backed it up. I had ipv6 setup which I can redo, but I'm not sure what else was in there. thanks