- Podman - Podman List Archives

logging stopping container
by Hendrik Haddorp 08 Jun '21

08 Jun '21

Hi, I have a test service that does a slow graceful shutdown and logs a few things while doing so. If I run "podman logs -f <name>" for the container the logs stop as soon as the container receives the SIGTERM signal, so once it enters the "stopping" state. Consequently the terminal containing the "podman run ..." command shows more logs then the "podman logs -f" command. Shouldn't "podman logs -f" follow the logs until the container reached the stopped state and the streams got closed and not only until it starts its shutdown? regards, Hendrik

2 2

Re: kill container when parent dies
by Hendrik Haddorp 07 Jun '21

07 Jun '21

Thanks, I didn't really want to disable the cgroups but I checked the options again an option is actually `--cgroupns=host`. This way systemd is able to kill the podman process when the main process of the unit is being killed. Given that podman had no chance to react the state of the container is wrong after that and `podman ps` shows the container as running and an error is logged when stopping the container. So it's an option but I think it's cleaner to let my unit be restarted on-failure and then cleanup the state. On 6/7/21 8:24 PM, Matt Heon wrote: > You could use `--cgroups=disabled` when starting Podman, which will > keep it in the same cgroup as the systemd unit and allow systemd to > kill the container process as well. This does require the use of the > `crun` OCI runtime (the default everywhere what's not RHEL and CentOS) > and disable some Podman features, though (most notably resource > limits, but a few more as well). > > Thanks, > Matt Heon > > On Mon, Jun 7, 2021 at 11:57 AM Hendrik Haddorp > <hendrik.haddorp(a)gmx.net <mailto:hendrik.haddorp@gmx.net>> wrote: > > I actually tested about the same. My outer process is running as a > systemd service and then starts a podman container as part of its > work.//This also does not make sure that the container gets killed > when the service gets kill. Systemd kills all process that are > part of the service (using KillMode=mixed) but it is not able to > kill all podman processes. I assume it is due to them not being in > the same cgroup. I can only somewhat resolve it by systemd > restarting my service on failure and then I can cleanup any still > running container >

1 0

kill container when parent dies
by Hendrik Haddorp 07 Jun '21

07 Jun '21

Hi, I have a process (A) that starts a podman container as a child process (B). When A dies due to a crash or gets killed I want the container to be killed as well. I tried to start B with all kinds of process attributes, like Setsid = true, Setpgid = true, Pdeathsig = SIGKILL, but B does not get killed and the container runs on. In fact I see that the podman process B has another child process and B seems to get reparented to a "systemd --user" process when A dies. How can I make sure the podman container dies when the parent process dies? This is on Linux and rootless. thanks, Hendrik

4 5

User mapping in rootless containers
by Michael Ivanov 07 Jun '21

07 Jun '21

Hallo, Is it possible to map host user id to some predefined user in rootless container instead of root:root? Best regards, -- \ / | | (OvO) | Михаил Иванов | (^^^) | | \^/ | E-mail: ivans(a)isle.spb.ru | ^ ^ | |

1 0

June 2021 Podman Community Meeting Recording
by Tom Sweeney 02 Jun '21

02 Jun '21

Hi All, In case you missed the meeting today, the video recording of the June 2021 Podman Community Meeting is now up at: https://bluejeans.com/s/3fO@uV5g9KF/ This meeting featured talks about Podman and TYE, Podman v3.2.0, Podman in Kubernetes, Podman Machine updates, and more! Also, I've been fighting with the calendar invites in BlueJeans, and I've been told some people have been getting two calendar invites with one of them being erroneous. I canceled the scheduled meetings in BlueJeans and will be creating a new video conference room for our August 3rd meeting. Watch for a new link to that in future emails and in the Google calendar invites. Note, we've decided to *not* hold the meeting in July due to it being the first day after the July 4th holiday and a number of people will be on vacation, myself included. Meeting notes will be up later in the week. Best Wishes, t

1 0

docker registry terminates when run under podman
by Michael Ivanov 01 Jun '21

01 Jun '21

Hallo, Not sure whether it is a right place o ask, but still. I am trying to run docker registry in rootless podman. I have created a 'register' user and started the registry with the following command: podman run --privileged -d --name registry -p 5000:5000 -v /srv/registry:/var/lib/registry --restart=always registry:latest (/srv/registry belongs to 'registry' user, so should be visible in rootless container as belonging to root). So far so good, I test the register with podman search and it returns expected results. But as soon as I exit the ssh session in which I started the container, container terminates, not immediately but in half minute or so. There;s no diagnostic about the reason in podman logs, nor in /var/syslog, nor in dmesg output. Just in case I tried to start it with nohup - same result. I also tried to start it as a service using the following file: [Unit] Description=Containers registry After=syslog.target network.target RequiresMountsFor=/srv/registry [Service] User=registry Group=registry LimitMEMLOCK=infinity LimitNOFILE=65535 Type=simple RemainAfterExit=yes ExecStart=/usr/bin/podman start registry ExecStop=/usr/bin/podman stop -t 60 registry [Install] WantedBy=multi-user.target And it still terminates in about half a minute after service startup. How can I find at least some indication about why this happens? Best regards, -- \ / | | (OvO) | Михаил Иванов | (^^^) | | \^/ | E-mail: ivans(a)isle.spb.ru | ^ ^ | |

4 6

systemd rootless service unit (not user users' system) - ?
by lejeczek 31 May '21

31 May '21

Hi guys. Trying "regular" podman generated systemd service unit with systemd fails with also what I could have fiddled into it so I wonder - if a rootless container, created and managed by a non-root user can be given to systemd(system's, not user's) for complete management? many thanks, L.

2 3

Re: podman and kubernetes
by Valentin Rothberg 28 May '21

28 May '21

Hi Thierry, Putting the list back in the loop. I think you accidentally replied to me only. On Wed, May 26, 2021 at 5:17 PM Thierry Parmentelat < thierry.parmentelat(a)inria.fr> wrote: > Hi Valentin > > thanks for your feedback, I’m answering inline > > > Podman is not meant to run K8s. Podman targets single-node machines and > focuses on servers and developer machines. It does not implement Container > Runtime Interface (CRI) that K8s uses to communicate with the container > runtime. CRI-O is dedicated to exactly that use-case. > > yeah, I got that > > so let me rephrase; the fact that I mentioned minikube - that is just a > first step for me a beginner here - seems to have been misleading > > my ultimate goal is to deploy a k8s cluster on a handful of bare-metal > fedora boxes, running podman instead of docker > but I was surprised to see **almost no mention** of podman in the k8s > documentation, where docker appears a zillion of times along with, in > shorter supply, rkt > As mentioned before, Podman is not meant to be running underneath Kubernetes. That is CRI-O's job. Docker and rkt are mentioned for historical reasons. Both have been used underneath Kubernetes for a longer period of time. rkt has been discontinued a long time ago and also Docker is not supported underneath Kubernetes anymore. > I understand that the podman team is not in charge of that documentation, > I’m just saying this suggests podman cannot be used in this way, which I’m > pretty certain it is, right ? > Podman cannot be used underneath Kubernetes. > > If you see specific bugs, opening an issue upstream would be great. For > questions, the mailing list works well, GitHub issues or the #podman > channel on Freenode IRC (and Libera Chat). > > thanks for pointing out irc, I’ll try to join you guys there > Great, see you over there :) Kind regards, Valentin

2 1

Podman v3.2.0-RC3 is available for testing
by Matt Heon 27 May '21

27 May '21

Hi All, We recently released what we hope will be the final release candidate for Podman v3.2.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 a number of other distros packages are 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, please file a Github issue with details. I am anticipating the v3.2.0 final release will come early next week, likely Tuesday. Thanks, Matt Heon [1] https://github.com/containers/podman/releases/tag/v3.2.0-rc3 [2] https://koji.fedoraproject.org/koji/buildinfo?buildID=1755692 [3] https://build.opensuse.org/package/show/devel:kubic:libcontainers:testing/p… [4] https://podman.io/getting-started/installation#building-from-scratch

1 0

Upcoming Podman Community Meeting - Tues June 1, 2021 11:00 a.m. EDT (UTC-4)
by Tom Sweeney 27 May '21

27 May '21

Hi All, I thought I'd send out an early reminder for the upcoming Podman Community Meeting next Tuesday as I and several other maintainers based in the US have Monday off. So we'll be meeting next Tuesday June 1, 2021 at 11:00 a.m. EDT (UTC-4) in this BlueJeans room: https://bluejeans.com/796412039. We'll be talking about Podman and TYE, Podman v3.2.0 update, Podman in Kubernetes, Podman machine update, and an open forum for questions/answers. As always, free to attend! The agenda is here for more details: https://podman.io/community/meeting/agenda/ and we hope to see many of you there! t

1 0