podman auto-update
doesn't work with containers that managed by the pod's systemd unit file
#6770
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
I have a pod, and there are several containes in this pod. I use
podman generate systemd --new --name pod_name
to creates systems unit files.But I can't use
podman auto-update
to update the containers in this pod.Steps to reproduce the issue:
Some container's images release new versions.
Use the
podman auto-update
.Describe the results you received:
Podman shows the errors below:
It seems the podman tries to restart these container services here. It doesn't work because these containers' systems unit files are created by
podman generate systemd --new --files --name pod_a
. These systems unit files containRefuseManualStart=yes
andRefuseManualStop=yes
. So the podman failed to restart them here.Describe the results you expected:
The podman should stop the pod (it would also stop its containers), update the images, then start the pod service.
Or some other ways that can update the containers without any problem.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Additional information:
I tried to add
io.containers.autoupdate=image
label in this pod instead of this pod's containers.Then use
podman auto-update
to update the containers. But it doesn't work, too.edited:
After some thought, this issue might be a feature instead of a bug. So feel free to change the label of the issue to the feature.
Also, it might be a good idea/feature to add the
io.containers.autoupdate
label for pod instead of the containers here. Then podman check this pod's containers version and update them.The text was updated successfully, but these errors were encountered: