diff options
author | Jonathan Lebon <jonathan@jlebon.com> | 2019-10-08 11:50:32 -0400 |
---|---|---|
committer | Jonathan Lebon <jonathan@jlebon.com> | 2019-10-08 12:12:16 -0400 |
commit | 59353b4dce692df0fb22a15427abbaafad58050e (patch) | |
tree | 116a58a29fc437a498768b3146d72c02aae36c2a /Vagrantfile | |
parent | c817ea1b33966c2f1f089b5c086df8cc45437065 (diff) | |
download | podman-59353b4dce692df0fb22a15427abbaafad58050e.tar.gz podman-59353b4dce692df0fb22a15427abbaafad58050e.tar.bz2 podman-59353b4dce692df0fb22a15427abbaafad58050e.zip |
io.podman.socket: drop Also=multi-user.target
Using `Also=` means that the target unit will also be
installed/uninstalled together with our unit. Doing
`Also=multi-user.target` essentially says: disable `multi-user.target`
if `io.podman.socket` is disabled, which sounds... not at all like
what we want.
In practice, systemd thankfully ignores this (likely because it's the
default target). I think having `Also=io.podman.socket` in the
`io.podman.service` already does what we want here: it gets installed
under `sockets.target` whenever the service is. (And the fact that
systemd ignored this means that it wasn't actually playing a role in
resolving #3998.)
This was causing `systemctl preset-all` to dump core in Fedora CoreOS:
https://github.com/coreos/fedora-coreos-tracker/issues/290
(Likely there's a systemd bug around here too.)
Signed-off-by: Jonathan Lebon <jonathan@jlebon.com>
Diffstat (limited to 'Vagrantfile')
0 files changed, 0 insertions, 0 deletions