Suggestion: make the compose plugin accept podman-docker as an alternative to docker-ce

[fghaas]

Is your feature request related to a problem? Please describe.

Using the compose plugin requires native Docker, as Salt checks for the presence of the docker-ce package:

https://github.com/OpenMediaVault-Plugin-Developers/openmediavault-compose/blob/main/srv/salt/omv/deploy/compose/30docker.sls#L45

This requires enabling a separate package repository.

For those who already use the podman plugin (openmediavault/openmediavault#1616) (or install Podman as a dependency of the photoprism plugin, openmediavault/openmediavault#1250), this shouldn't be necessary, considering the podman-docker package exists in Debian to provide a drop-in replacement for native Docker, using Podman, which works just fine even with docker-compose.

Describe the solution you'd like
It would be great openmediavault-compose would include the option of either using docker-ce, or podman-docker.

Describe alternatives you've considered
Users could always just go ahead and install the docker-ce package, of course. :) Or use just the podman plugin, forgoing the use of docker-compose.

Additional context
None

[ryecoaaron]

I have looked into this. Unfortunately, podman-docker is not a 100% drop-in and quite a few things are broken in the plugin using podman. It has been a year or so. So, I can possible check it out again.

Just a warning, the podman plugin will not continue to be maintained. The k8s plugin is what Volker was recommending going forward. And I did look at adding Kompose support to the plugin but Kompose is not even close to being ready as a drop-in for the plugin.

[fghaas]

Whoa, that was quick — thanks!

I have looked into this. Unfortunately, podman-docker is not a 100% drop-in and quite a few things are broken in the plugin using podman. It has been a year or so. So, I can possible check it out again.

Right, I did do the same about a year ago and things have much improved since. One thing I do know to not work is docker buildx, but that doesn't strike me as something that would break the typical use case of the compose plugin.

Just a warning, the podman plugin will not continue to be maintained.

This I actually don't mind too much, personally. I don't use that plugin to actually launch things; I use it primarily to check on Photoprism and on the containers I currently launch semi-manually from docker-compose files.

The k8s plugin is what Volker was recommending going forward.

I use Kubernetes so much at work that I prefer to do without it on my home network. :)

[ryecoaaron]

Breaking docker build doesn't both me much either. I will look at the podman stuff and see what it is like. Might be a few days.

[fghaas]

Sure, no rush at all, and also feel free to dismiss this altogether if it's a bad idea. Thanks for looking into this!