-
Notifications
You must be signed in to change notification settings - Fork 22
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
Podman support? #15
Comments
Additionally, Podman is used in SUSE distros (openSUSE Tumbleweed and Leap, and also SUSE Linux Enterprise). It's also made its way into Debian recently and should be in Ubuntu soon as well. |
Supporting podman would be a very nice feature, but k3x does not interact with docker directly: all the heavy work is done by k3d. k3d is currently using the Docker API so, until k3d supports podman is some other way, this will not be possible. There is an open issue in the k3d repo about this though. |
Cool, thanks! |
I see that k3d 3.4.0 and Podman 2.2.1 are now sufficiently compatible with each other to start the k3s container. The k3x flatpak still bundles k3d 1.7.0, however. |
https://k3d.io/v5.4.0/usage/advanced/podman/ suggests that this should be fairly easy to configure, but I cannot get it working as described with symlinks :( Any chance this issue can get a bump up in priority? 🙏 ❤️ Especially considering that k3d-io/k3d#84 seems to be resolved. |
Fedora, CentOS, and Red Hat Enterprise Linux have dropped Docker (Moby) and switched to Podman, which doesn't require a daemon. It does have API support (which is what we're using in cockpit-podman) We're specifically the new Podman 2.0 API, not the deprecated varlink API.
The new API has a podman-specific API and a Docker-compatible version.
Podman's API is documented at https://docs.podman.io/en/latest/_static/api.html and there's a simple overview @ https://www.redhat.com/sysadmin/podmans-new-rest-api
The text was updated successfully, but these errors were encountered: