Hi,
I've been happily deploying my container services in podman using
podman-generate-systemd
<http://docs.podman.io/en/latest/markdown/podman-generate-systemd.1.html> unit
files. Recently I noticed a scary warning in journald:
XXX systemd[1]: /etc/systemd/system/container-xxx.service:21: Unit
configured to use KillMode=none. This is unsafe, as it disables systemd's
process lifecycle management for the service. Please update your service to
use a safer KillMode=, such as 'mixed' or 'control-group'. Support for
KillMode=none is deprecated and will eventually be removed.
This KillMode line was generated by Podman.
I don't have any reason to believe that KillMode=none isn't as expected.
Podman and systemd are tracking and killing my container processes
correctly as far as I can tell. But the final sentence made me wonder if my
unit files will suddenly stop working after a future version of systemd
removes support for KillMode=none.
A quick Google search and scan of Podman Github issues didn't turn up
anything related so I thought I'd ask this group.
Thanks,
brian
I am trying to replicate the demo given yesterday
https://asciinema.org/a/376554 and not seeing the same results - this is in
new fedora33 server VM, did sudo dnf install podman, enabled the
updates-testing, then followed along... is there anything missing I need to
install to make use of the alias?
[ehaynes@localhost ~]$ sudo dnf --enablerepo=updates-testing update podman
Last metadata expiration check: 0:02:22 ago on Wed 02 Dec 2020 09:25:43 AM
EST.
Dependencies resolved.
=====================================================================================================================================================
Package Architecture Version
Repository Size
=====================================================================================================================================================
Upgrading:
containers-common x86_64
1:1.2.0-10.fc33 updates-testing
79 k
podman x86_64
2:2.2.0-2.fc33 updates-testing
11 M
Transaction Summary
=====================================================================================================================================================
Upgrade 2 Packages
Total download size: 12 M
Is this ok [y/N]: y
Downloading Packages:
(1/2): containers-common-1.2.0-3.fc33_1.2.0-10.fc33.x86_64.drpm
797 kB/s | 57 kB 00:00
(2/2): podman-2.2.0-2.fc33.x86_64.rpm
6.1 MB/s | 11 MB 00:01
[DRPM] containers-common-1.2.0-3.fc33_1.2.0-10.fc33.x86_64.drpm: done
-----------------------------------------------------------------------------------------------------------------------------------------------------
Total
5.9 MB/s | 12 MB 00:01
Delta RPMs reduced 11.5 MB of updates to 11.5 MB (0.1% saved)
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing :
1/1
Running scriptlet: containers-common-1:1.2.0-10.fc33.x86_64
1/1
Upgrading : containers-common-1:1.2.0-10.fc33.x86_64
1/4
Upgrading : podman-2:2.2.0-2.fc33.x86_64
2/4
Cleanup : podman-2:2.1.1-12.fc33.x86_64
3/4
Cleanup : containers-common-1:1.2.0-3.fc33.x86_64
4/4
Running scriptlet: containers-common-1:1.2.0-3.fc33.x86_64
4/4
Verifying : containers-common-1:1.2.0-10.fc33.x86_64
1/4
Verifying : containers-common-1:1.2.0-3.fc33.x86_64
2/4
Verifying : podman-2:2.2.0-2.fc33.x86_64
3/4
Verifying : podman-2:2.1.1-12.fc33.x86_64
4/4
Upgraded:
containers-common-1:1.2.0-10.fc33.x86_64
podman-2:2.2.0-2.fc33.x86_64
Complete!
[ehaynes@localhost ~]$ podman version
Version: 2.2.0
API Version: 2.1.0
Go Version: go1.15.5
Built: Tue Dec 1 12:04:57 2020
OS/Arch: linux/amd64
[ehaynes@localhost ~]$ sudo podman network create test1
/etc/cni/net.d/test1.conflist
[ehaynes@localhost ~]$ sudo podman network create test2
/etc/cni/net.d/test2.conflist
[ehaynes@localhost ~]$ sudo podman run -t -d --rm --net test1 --name
testctr --network-alias httpctr nginx
Completed short name "nginx" with unqualified-search registries (origin:
/etc/containers/registries.conf)
Trying to pull registry.fedoraproject.org/nginx:latest...
manifest unknown: manifest unknown
Trying to pull registry.access.redhat.com/nginx:latest...
unsupported: This repo requires terms acceptance and is only available on
registry.redhat.io
Trying to pull registry.centos.org/nginx:latest...
manifest unknown: manifest unknown
Trying to pull docker.io/library/nginx:latest...
Getting image source signatures
Copying blob 8b03f1e11359 done
Copying blob d20aa7ccdb77 done
Copying blob addb10abd9cb done
Copying blob 852e50cd189d done
Copying blob 571d7e852307 done
Copying config bc9a0695f5 done
Writing manifest to image destination
Storing signatures
29ec6cd7cebdaa2c1e2cdd5b2b4069296050b80f8f3a7a7e504abebc1b92967c
[ehaynes@localhost ~]$ sudo podman run -t -i --rm --net test1 fedora curl
testctr
Resolved short name "fedora" to a recorded short-name alias (origin:
/etc/containers/registries.conf.d/shortnames.conf)
Trying to pull registry.fedoraproject.org/fedora:latest...
Getting image source signatures
Copying blob 8fde7942e775 done
Copying config 79fd58dc76 done
Writing manifest to image destination
Storing signatures
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
body {
width: 35em;
margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif;
}
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>
<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>
<p><em>Thank you for using nginx.</em></p>
</body>
</html>
[ehaynes@localhost ~]$ sudo podman run -t -i --rm --net test1 fedora curl
httpctr
curl: (6) Could not resolve host: httpctr
--
Ed Haynes
SOLUTIONS ARCHITECT
Red Hat <https://www.redhat.com/>
ehaynes(a)redhat.com *M: (978)-551-0057 *
TRIED. TESTED. TRUSTED.
Hi All!
The notes from yesterday's Podman Community Meeting are now up on
podman.io (https://podman.io/community/meeting/notes/2020-12-01/) as is
the video recording
(https://bluejeans.com/playback/s/CaR5m0soJvtz8AOJhkvi74YnRvKbmSDDfhaeQ3f8oy…)
For each topic covered during the meeting, I noted the start time of the
topic in the meeting notes in case you want to skip ahead. Pablo Greco
managed to add a highlight to the recording, but I was unable to post
meeting. Will try to do so for future meetings to make it even easier
to find to the topics there.
It was great seeing and chatting with many of you yesterday. As a
reminder, due to the holidays, we've decided to cancel the January
meeting. So our next meeting will be February 2, 2021 at 11:00 a.m.
Eastern (UTC-5). I'll send out an agenda and reminders as we close in
on that.
For those that celebrate, I hope you have a very happy, healthy and
safe holiday season!
Best Wishes,
t
