992253f871
Podman does not require skopeo to run. They are both independent tools. In distros like Debian, Fedora and Arch they don't depend on it either. Skopeo also seems to be used in some of podman's tests, so it makes sense to keep it around for the ptest. We do require skopeo's libdevmapper dependency, so include that directly. And inherit container-host to make sure the container configs are present on the device. Signed-off-by: Patrick Wicki <patrick.wicki@siemens.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> |
||
|---|---|---|
| .. | ||
| podman | ||
| podman_git.bb | ||
| README | ||
rootless podman
Basic configuration:
https://developers.redhat.com/blog/2020/09/25/rootless-containers-with-podman-the-basics#
% echo "user.max_user_namespaces=28633" > /etc/sysctl.d/userns.conf % sysctl -p /etc/sysctl.d/userns.conf
% useradd -c "yocto" yocto % passwd yocto
% su - yocto
% podman pull alpine % podman run alpine cat /etc/os-release % podman images % podman unshare cat /proc/self/uid_map
podman system service
The podman system service command creates a listening service that answers API calls for Podman, it supports systemd socket activation.
Test with docker-compose (v2):
To be noticed, docker could NOT be installed together with podman, so docker-compose should be built as a standalone tool, remove 'docker-plugin' from its PACKAGECONFIG at build time:
PACKAGECONFIG:remove:pn-docker-compose = "docker-plugin"
% sudo systemctl start podman.socket % git clone https://github.com/docker/awesome-compose.git % cd awesome-compose/postgresql-pgadmin; source .env % sudo docker-compose up -d