Provides podman and its dependencies statically linked - https://github.com/mgoltzsche/podman-static
500K+
Provides alpine-based podman image variants for nested and rootless containerization scenarios.
The project is maintained at https://github.com/mgoltzsche/podman-static.
| Tag | Description |
|---|---|
latest, <VERSION> | podman with all dependencies: runc, crun, conmon, fuse-overlayfs, netavark, pasta, aardvark-dns, catatonit. |
minimal, <VERSION>-minimal | podman, crun, conmon, fuse-overlayfs and netavark binaries, configured to use the host's existing namespaces (low isolation level; ideal to run nested containers, e.g. within CI pipelines). |
remote, <VERSION>-remote | the podman remote binary. |
The image provides the following statically linked binaries (without systemd support):
Run podman in docker (or podman):
docker run --device=/dev/fuse -u podman:podman mgoltzsche/podman:minimal docker run alpine:latest echo hello from nested container
Within the container docker is linked to podman to support applications that use the docker command.
To allow the container to write to a shared volume using your host UID, add the --userns=keep-id option.
To be able to build images within a nested container, mount a volume at the storage directory, e.g. --tmpfs /podman/.local/share/containers/storage:mode=1777.
(This is because fuse-overlayfs file systems cannot be nested.)
If you want the nested containers to run with stronger isolation, you must use the regular (non-minimal) podman image and sacrifice the outer container's isolation by running it in --privileged mode:
docker run --privileged -u podman:podman mgoltzsche/podman:latest docker run alpine:latest echo hello from nested container
By default containers are run as user root.
However the podman (uid/gid 1000) user can be used instead for which also a subuid/gid mapping is configured with the image (/etc/subuid, /etc/subgid).
Content type
Image
Digest
sha256:928da877b…
Size
30.7 MB
Last updated
4 days ago
docker pull mgoltzsche/podman:6.2.0-minimal