Open lukas-vlcek opened 1 year ago
What's the issue you're running into using Docker on M1?
1) As far as I understand it is available only as a part of paid subscription (at least that would be my case, see Docker Desktop terms in installation instructions) 2) I would like to use Podman (and I believe there will be more people going forward)
+1 on podman because of licensing
+1 on additional options other than docker for we macOS folks!
@lukas-vlcek looks like we have agreement on podman, would you like to contribute the changes?
Yes, I would like to give it a try. It is on my radar.
Is your feature request related to a problem? Please describe.
Currently, OpenSearch testing has a hard dependency on Docker and Docker-compose. This makes the development on non-Linux platforms more complicated and introduces a barrier for new contributors.
Describe the solution you'd like
A Podman and Podman-compose are open-source alternatives and they had matured a lot. It would be great if developers had the option to choose between docker and podman.
Describe alternatives you've considered
My primary development environment is MacOS (M1) and I am not sure if there are "non-hackich" alternatives (for example Minikube).
Additional context
I was recently experimenting with podman and podman-compose:
And I have to say that I was able to run many example applications from both the https://github.com/docker/awesome-compose and https://github.com/containers/podman-compose/tree/devel/examples.
The experience seem to be really smooth these days. Podman-compose uses Qemu VMs and CLI commands
podman
andpodman-compose
work really effortlessly. You create newpodman machine
instance (which is typically a fresh fedora), do some basic settings (like installingpodman-mac-helper
, exportDOCKER_HOST
). Then you navigate to docker-compose examples folder, firepodman-compose up
and that's it...So far so good. But when I was trying to convince OpenSearch to use podman-compose instead of docker-compose I realized that the main issue is that it rely on gradle-docker-compose-plugin which is not compatible with podman-compose. See https://github.com/avast/gradle-docker-compose-plugin/issues/387
To me it seems that missing gradle plugin for podman is the last bit that is holding us back. Perhaps the most logical way would be to fork the docker plugin and adapt it for podman (but I am not saying this is on my near roadmap, although a prototyping should not be that difficult).
I would like to hear from others, WDYT?