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
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