Drop [Install] section from podman.service #7190
Labels
kind/bug
Categorizes issue or PR as related to a bug.
kind/feature
Categorizes issue or PR as related to a new feature.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
openshift-ci-robot
added
kind/bug
martinpitt
added a commit
to martinpitt/cockpit-podman
that referenced
this issue
Aug 3, 2020
2.0.3 breaks API: - https://bugs.debian.org/966501 - containers/podman#7078 The Debian package now ships the REST systemd units, but due to containers/podman#7190 they get "over-enabled". Hack around that.
1 task
martinpitt
added a commit
to martinpitt/cockpit-podman
that referenced
this issue
Aug 3, 2020
2.0.3 breaks API: - https://bugs.debian.org/966501 - containers/podman#7078 The Debian package now ships the REST systemd units, but due to containers/podman#7190 they get "over-enabled". Hack around that.
marusak
pushed a commit
to cockpit-project/cockpit-podman
that referenced
this issue
Aug 3, 2020
2.0.3 breaks API: - https://bugs.debian.org/966501 - containers/podman#7078 The Debian package now ships the REST systemd units, but due to containers/podman#7190 they get "over-enabled". Hack around that.
|
Thanks for the report. I'll open a PR in a minute. |
vrothberg
added a commit
to vrothberg/libpod
that referenced
this issue
Aug 3, 2020
podman.service is socket activated through podman.socket. It should not have its own [Install] section, it does not make sense to systemctl enable podman.service. This leads to podman.service always running on a Debian system, as Debian's policy is to enable/start running services by default. We don't want a daemon :^) Fixes: containers#7190 Reported-by: @martinpitt Signed-off-by: Valentin Rothberg <[email protected]>
vrothberg
added a commit
to vrothberg/libpod
that referenced
this issue
Aug 11, 2020
podman.service is socket activated through podman.socket. It should not have its own [Install] section, it does not make sense to systemctl enable podman.service. This leads to podman.service always running on a Debian system, as Debian's policy is to enable/start running services by default. We don't want a daemon :^) Fixes: containers#7190 Reported-by: @martinpitt Signed-off-by: Valentin Rothberg <[email protected]>
github-actions
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
/kind bug
/kind feature
Description
podman.serviceis socket activated throughpodman.socket. It should not have its own[Install]section, it does not make sense tosystemctl enable podman.service. This is defined here.This leads to podman.service always running on a Debian system, as Debian's policy is to enable/start running services by default.
Can you please drop this?
Output of
podman version:Package info (e.g. output of
rpm -q podmanorapt list podman):The text was updated successfully, but these errors were encountered: