pack8s
is meant to be a podman compatible drop-in replacement for gocli.
We want to add podman support to kubevirtci, but changing
gocli
makes not much sense since the tool is simple and very stable. The quicker and safer way is
to provide a drop-in podman-compatible replacement, hence pack8s
It is pronounced "pak-eight-z", much like "packets".
Apache v2 (same as kubevirtci
)
just run
make
Or fetch one of the releases.
See STATUS.md
- build (see above)
pack8s
and put it anywhere on your PATH. - set up your box as described in this blog post or see
local box setup
below. - tell
kubevirtci
to actually usepack8s
:
export KUBEVIRTCI_RUNTIME=podman
- use kubevirtci as usual (
make cluster-up
,make cluster-down
...).
Excerpt taken from this blog post. See also this other blog post.
$ sudo yum install podman libvarlink-util
$ sudo groupadd podman
Copy /lib/tmpfiles.d/podman.conf to /etc/tmpfiles.d/podman.conf.
$ sudo cp /lib/tmpfiles.d/podman.conf /etc/tmpfiles.d/podman.conf
Edit /etc/tmpfiles.d/podman.conf
to read like:
d /run/podman 0750 root podman
Copy /lib/systemd/system/io.podman.socket to /etc/systemd/system/io.podman.socket.
$ sudo cp /lib/systemd/system/io.podman.socket /etc/systemd/system/io.podman.socket
Edit section [Socket] of /etc/systemd/system/io.podman.socket
to read like:
[Socket]
ListenStream=/run/podman/io.podman
SocketMode=0660
SocketGroup=podman
Then activate the changes:
$ sudo systemctl daemon-reload
$ sudo systemd-tmpfiles --create
$ sudo systemctl enable --now io.podman.socket
The directory and socket now belongs to the podman
group
$ sudo ls -al /run/podman
drwxr-x---. 2 root podman 60 14. Jan 14:50 .
drwxr-xr-x. 51 root root 1420 14. Jan 14:36 ..
srw-rw----. 1 root podman 0 14. Jan 14:50 io.podman
Last step: add your user to the podman
group. Example:
$ sudo usermod -G podman -a $USER
No available. pack8s
is meant to be a single, self contained, statically linked executable, so benefits of a container image are unclear.
Contributions welcome, though.