podman update
resets the configuration of other container resources
#24610
Labels
jira
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.
Issue Description
If a container has a resource configuration set and is updated with the
podman update
command, the current resource configuration is replaced with a new resource configuration that does not reflect the previous configuration. Thus, if you change a single resource configuration field withpodman update
, the other fieald of resource configuration is set to its default values. See the reproducer example.Steps to reproduce the issue
Steps to reproduce the issue
podman run -dt --pids-limit 1024 --name hc1 quay.io/libpod/alpine:latest top
podman inspect hc1 --format {{.HostConfig.PidsLimit}}
podman update hc1 --memory 100Mb
(You can change any other resource of your choice)podman inspect hc1 --format {{.HostConfig.Memory}}
podman inspect hc1 --format {{.HostConfig.PidsLimit}}
For this reproduction, you can choose any of the
podman update
resource flags.Describe the results you received
After the last
podman update
the memory is set to 104857600 and PidsLimit is 0.Describe the results you expected
After the last
podman update
the memory is set to 104857600 and the PidsLimit is 1024.podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
It was found here.
The text was updated successfully, but these errors were encountered: