-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support podman #9
Comments
Definitely makes sense to add, but I'm not sure podman is daemonised in the same way docker is? I know at the cli api level they're roughly API compatible, but I'm not sure if Bollard is inherently podman compatible I'll definitely look into it once I've got a few more features on the docker side |
podman is indeed a daemonless which makes sense if you think about it, why do you need a daemon to run containers ? |
+1 Usually a podman installation comes with a socket service (either rootless or root) that was designed to replace dockerd socket. For 99% of all containers / docker-compose stuff you don't have any problems with it. I even added a docker context for it (running docker root/docker rootless/podman on my system). Preference goes to Podman but some devs still rely on docker root :( https://docs.podman.io/en/v4.1.1/markdown/podman-system-service.1.html Now you just need to add a pods view. And secrets. |
I will have a re-read of the docs |
+1 |
Would be great to add support for podman as well
The text was updated successfully, but these errors were encountered: