I couldn't find anybody pointing out the missing support for container runtimes other than Docker, so here I go:
As a user of Fedora Silverblue, I don't have out-of-the-box docker builtin with my OS, but instead podman (a daemonless and "rootless" userspace container engine).
For purposes of building images and running containers it's directly compatible with docker, however as it doesn't have a daemon, there's no way to interact with it using go docker bindings (like act does).
From what I understand, act uses docker bindings in order to
- resolve and pull images
- create and execute containers
All of this is possible with podman as well, so a solution could be to replace the direct docker bindings with an abstraction layer that would default to docker, but allows the user to select podman (or another binding) to interact with containers or images.
I would be interested in helping to get this to work, and want to raise this issue to ask for support on this topic.
I couldn't find anybody pointing out the missing support for container runtimes other than Docker, so here I go:
As a user of Fedora Silverblue, I don't have out-of-the-box
dockerbuiltin with my OS, but insteadpodman(a daemonless and "rootless" userspace container engine).For purposes of building images and running containers it's directly compatible with
docker, however as it doesn't have a daemon, there's no way to interact with it using godockerbindings (likeactdoes).From what I understand,
actusesdockerbindings in order toAll of this is possible with
podmanas well, so a solution could be to replace the directdockerbindings with an abstraction layer that would default todocker, but allows the user to selectpodman(or another binding) to interact with containers or images.I would be interested in helping to get this to work, and want to raise this issue to ask for support on this topic.