diff options
| author | Matthew Heon <mheon@redhat.com> | 2020-06-16 10:50:33 -0400 |
|---|---|---|
| committer | Matthew Heon <mheon@redhat.com> | 2020-06-16 11:09:48 -0400 |
| commit | 20345b1ec0dc4fb64ce77400cad822f1fadb86f0 (patch) | |
| tree | ea97d4e1ddc8dd999c1fdd1fc6103c056bd52f0b /libpod/container_log_unsupported.go | |
| parent | 0968f25988624699f2db559f0a984cf84c8a284f (diff) | |
| download | podman-20345b1ec0dc4fb64ce77400cad822f1fadb86f0.tar.gz podman-20345b1ec0dc4fb64ce77400cad822f1fadb86f0.tar.bz2 podman-20345b1ec0dc4fb64ce77400cad822f1fadb86f0.zip | |
Revert "Change Varlink systemd unit to use `system service`"
This reverts commit 1bc992bfc3a983b4d9ab53f778a545d83bcde94d.
We originally thought `podman varlink` was entirely removed, but
that was not true. We originally thought that
`podman system service --varlink` worked the same as
`podman varlink` but that was also not true. `system service` is
broken when used under systemd units, and `podman varlink` still
exists and works. Revert the change to `podman system service` to
fix socket-activated Varlink under systemd.
Signed-off-by: Matthew Heon <mheon@redhat.com>
Diffstat (limited to 'libpod/container_log_unsupported.go')
0 files changed, 0 insertions, 0 deletions