summaryrefslogtreecommitdiff
path: root/nix/nixpkgs.nix
diff options
context:
space:
mode:
authorTycho Andersen <tycho@tycho.pizza>2021-05-20 13:01:21 -0600
committerTycho Andersen <tycho@tycho.pizza>2021-06-24 09:01:39 -0600
commit364e8a26da2d49c3ea06cc9c0470e47925dcd192 (patch)
tree59224623eef2451b217356fdb5b05968ede3b299 /nix/nixpkgs.nix
parent21d80faa0b30a042b62566a2ffdff5510a92b9e6 (diff)
downloadpodman-364e8a26da2d49c3ea06cc9c0470e47925dcd192.tar.gz
podman-364e8a26da2d49c3ea06cc9c0470e47925dcd192.tar.bz2
podman-364e8a26da2d49c3ea06cc9c0470e47925dcd192.zip
pkg/systemd: don't require LISTEN_FDNAMES for socket activation
LISTEN_FDNAMES is optional, the docs for sd_listen_fds() says: This information is read from the $LISTEN_FDNAMES variable, which **may** contain a colon-separated list of names. emphasis mine (indeed, the cited coreos code also suggests it is optional). This actually results in bug, since the default /contrib/systemd/system/podman.socket file doesn't set a FileDescriptorName=. podman when run with this systemd configuration *always* starts in unix socket mode since SocketActivated() will return false because the name is missing. The bug is a race with a very small window: between when podman does the unlink() and when it re-binds the socket later in the code, requests made during this time will fail since nothing is listening. There's another small race when the service stops and systemd realizes it and starts listening again. However, small this window we managed to hit it :). Let's fix this by ignoring LISTEN_FDNAMES. Since the code in cmd/podman/system/service_abi.go:restService() ignores this value anyway when setting up the socket activated stuff, there's no real loss here. Signed-off-by: Tycho Andersen <tycho@tycho.pizza>
Diffstat (limited to 'nix/nixpkgs.nix')
0 files changed, 0 insertions, 0 deletions