- Podman - Podman List Archives

Podman 3.0 on WSL distro like Fedora33 with systemd, i.e. started using Aekane-system genie - 1st impression.
by Pavel Sosin 31 Jan '21

31 Jan '21

1. cgroup manager can be set to systems 2. Podman requires systemd session created for the rootless user. To achieve it distro must be started as wsl -d Fedora33 -u root genie -s. Then user session must be created using wsl -d Fedora33 genie -l

1 0

Podman 3.0 for Fedora 33 WSL
by Pavel Sosin 25 Jan '21

25 Jan '21

I just finished the assembly and smoke test of my underground Fedora 33 WSL distro weaponized with Arkane genie, i.e. systemd. Installed early Podman 2.2.1 is working OK. From which repository I can install Podman 3.0?

2 1

can not run ubi7-init systemd container, fedora systemd container works fine
by Jan Hutař 22 Jan '21

22 Jan '21

Hello! I have issue with running "ubi7-init" based container. When I base mine container on "fedora", it works fine: $ cat Containerfile FROM fedora RUN dnf -y install httpd; dnf clean all; systemctl enable httpd EXPOSE 80 CMD [ "/sbin/init" ] and then: $ sudo podman build -f Containerfile $ sudo podman run -ti -p 80:80 20185593d0f96c4dee56e351eae4754cdd429679c1b645dae1b6f24880ce33fc systemd v246.6-3.fc33 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified) [...] [ OK ] Started The Apache HTTP Server. [...] But when I try the same with ubi7-init based container (or rhel7-init): $ cat Containerfile FROM registry.access.redhat.com/ubi7/ubi-init RUN echo -e "[repo1]\nname=repo1\nbaseurl=http://repos.example.com/RHEL-7/7.9/Server/x86_…" >/etc/yum.repos.d/repo1.repo; yum -y install httpd; yum clean all; systemctl enable httpd EXPOSE 80 CMD [ "/sbin/init" ] it fails: $ sudo podman run -ti -p 80:80 d872b16b8d0f9718c60420e3569cb4d5ddd16053fb72903e70d7b62ba3f34964 Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!!!!!] Failed to mount API filesystems, freezing. And same with privileged: $ sudo podman run -ti -p 80:80 --privileged=true d872b16b8d0f9718c60420e3569cb4d5ddd16053fb72903e70d7b62ba3f34964 Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!!!!!] Failed to mount API filesystems, freezing. I have these versions: $ rpm -q fedora-release-common podman fedora-release-common-33-3.noarch podman-2.2.1-1.fc33.x86_64 $ sudo podman version Version: 2.2.1 API Version: 2.1.0 Go Version: go1.15.5 Built: Tue Dec 8 15:37:50 2020 OS/Arch: linux/amd64 Please, any idea on what I'm doing wrong? Thank you in advance and happy new year! Regards, Jan -- Jan Hutar Performance Engineering jhutar(a)redhat.com Red Hat, Inc.

4 4

Podman Community Meeting Agenda - Tues February 2, 2021 - 11:00 a.m. Eastern (UTC-5)
by Tom Sweeney 21 Jan '21

21 Jan '21

Hi All, The next Podman Community Meeting is coming up in just under two weeks. We'll be meeting on Tuesday February 2, 2021 at 11:00 a.m. Eastern (UTC-5). The agenda for the meeting has just been posted on the podman.io site (https://podman.io/community/meeting/agenda/) and you'll find links on the agenda to the BlueJeans Video Conference Room that we'll be using. No cost to attend, hope to see a number of you there! t

1 0

Github.com has added a new feature Discussions
by Daniel Walsh 21 Jan '21

21 Jan '21

We have turned it on for the Podman github. Yet another way to communicate. We are all new to it, and are welcome to ideas on how to use it. https://github.com/containers/podman/discussions

1 0

Reminder Feb 2nd we will have a Podman community meeting.
by Daniel Walsh 21 Jan '21

21 Jan '21

Tom Sweeney will be sending out an agenda. We would love people to play with the podman 3.0 rc1 and rc2 when it ships to help us improve its stability. Available on Fedora 33/34 now, and hopefully other distros.

3 2

Podman v3.0.0-rc1 is now available for testing
by Matt Heon 19 Jan '21

19 Jan '21

Hi All, We recently released the first release candidate for Podman v3.0.0, with a long list of new features and fixes [1]. We'd really appreciate any and all testing you'd be willing to do on this new RC. Builds are available for Fedora in Koji [2], and for most other distros they will soon be available in the Testing repos for OBS [3]. You can also build from source using the instructions at [4]. If you encounter any bugs with the new release candidate, please file a Github issue with details at [5]. We are anticipating a final release in several weeks. We will publish a second release candidate next Monday, and if no major bugs are identified, the 3.0.0 final release will be the subsequent Monday, February 1. Thanks, Matt Heon [1] https://github.com/containers/podman/releases/tag/v3.0.0-rc1 [2] https://koji.fedoraproject.org/koji/buildinfo?buildID=1670934 [3] https://build.opensuse.org/package/show/devel:kubic:libcontainers:testing/p… [4] https://podman.io/getting-started/installation#building-from-scratch [5] https://github.com/containers/podman/issues

1 0

podman run -It -v /tst:/tst --net=host Xxxx /sbin/Init
by Philip Rhoades 19 Jan '21

19 Jan '21

People, If I build a F33 podman container in a virt-manager built F33 VM, I get a working podman container but if I try: ls -al /tst from there I get: ls: cannot open directory '/tst/': Permission denied It appears it is because of selinux in the host VM - if I disable that and build a new container, I can list /tst as expected . . Is there a fix or workaround for this situation? Am I finally going to have to learn about selinux? Thanks, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil(a)pricom.com.au

2 2

How to run a user systemd service in a GitHub Actions workflow
by Erik Sjölund 14 Jan '21

14 Jan '21

Here is a mini demo of how to run a web server (nginx) with podman in a user systemd service with Github Actions: https://github.com/eriksjolund/user-systemd-service-actions-workflow I noticed two non obvious things: 1. A short sleep was needed after loginctl enable-linger runner 2. systemctl needs to be run with the environment variable XDG_RUNTIME_DIR=/run/user/$UID

2 2

Would a new option --disable-subuid make sense?
by Erik Sjölund 11 Jan '21

11 Jan '21

The upcoming Podman 3.0 looks exciting, especially in regards to "rootless single mapping". Regarding the question: > If you know of "features", that you want to get in, then make them known > in github. Would it make sense to add these two new command-line options to "podman run" --disable-subuid --disable-subgid so that it would easy to disable the use of /usr/bin/newuidmap /usr/bin/newgidmap That would be handy when a user wants to run podman and be sure that no subuids and subgids are used. If you wonder about the terminology: "rootless single mapping", I found it here: [erik@laptop podman]$ grep "using rootless " ./pkg/rootless/rootless_linux.go logrus.Warnf("using rootless single mapping into the namespace. This might break some images. Check /etc/subuid and /etc/subgid for adding sub*ids") [erik@laptop podman]$ I could add a feature request to Github, if you think these options make sense.

2 2