Files
podman/docs/source/markdown/podman-update.1.md.in
Jan Kaluza 701aade262 Add --env and --unsetenv to podman update.
The --env is used to add new environment variable to container or
override the existing one. The --unsetenv is used to remove
the environment variable.

It is done by sharing "env" and "unsetenv" flags between both
"update" and "create" commands and later handling these flags
in the "update" command handler.

The list of environment variables to add/remove is stored
in newly added variables in the ContainerUpdateOptions.

The Container.Update API call is refactored to take
the ContainerUpdateOptions as an input to limit the number of its
arguments.

The Env and UnsetEnv lists are later handled using the envLib
package and the Container is updated.

The remote API is also extended to handle Env and EnvUnset.

Fixes: #24875

Signed-off-by: Jan Kaluza <jkaluza@redhat.com>
2025-03-21 13:15:44 +01:00

120 lines
2.4 KiB
Markdown

% podman-update 1
## NAME
podman\-update - Update the configuration of a given container
## SYNOPSIS
**podman update** [*options*] *container*
**podman container update** [*options*] *container*
## DESCRIPTION
Updates the configuration of an existing container, allowing changes to resource limits and healthchecks.
## OPTIONS
@@option blkio-weight
@@option blkio-weight-device
@@option cpu-period
@@option cpu-quota
@@option cpu-rt-period
@@option cpu-rt-runtime
@@option cpu-shares
@@option cpus.container
@@option cpuset-cpus
@@option cpuset-mems
@@option device-read-bps
@@option device-read-iops
@@option device-write-bps
@@option device-write-iops
@@option env.update
@@option health-cmd
@@option health-interval
Changing this setting resets the timer.
@@option health-log-destination
Warning: Changing this setting may cause the loss of previous logs.
@@option health-max-log-count
@@option health-max-log-size
@@option health-on-failure
@@option health-retries
@@option health-start-period
@@option health-startup-cmd
@@option health-startup-interval
Changing this setting resets the timer, depending on the state of the container.
@@option health-startup-retries
@@option health-startup-success
@@option health-startup-timeout
@@option health-timeout
@@option memory
@@option memory-reservation
@@option memory-swap
@@option memory-swappiness
@@option no-healthcheck
@@option pids-limit
@@option restart
@@option unsetenv.update
## EXAMPLEs
Update a container with a new cpu quota and period.
```
podman update --cpus=5 myCtr
```
Update a container with all available options for cgroups v2.
```
podman update --cpus 5 --cpuset-cpus 0 --cpu-shares 123 --cpuset-mems 0 --memory 1G --memory-swap 2G --memory-reservation 2G --blkio-weight-device /dev/zero:123 --blkio-weight 123 --device-read-bps /dev/zero:10mb --device-write-bps /dev/zero:10mb --device-read-iops /dev/zero:1000 --device-write-iops /dev/zero:1000 --pids-limit 123 ctrID
```
Update a container with all available options for cgroups v1.
```
podman update --cpus 5 --cpuset-cpus 0 --cpu-shares 123 --cpuset-mems 0 --memory 1G --memory-swap 2G --memory-reservation 2G --memory-swappiness 50 --pids-limit 123 ctrID
```
## SEE ALSO
**[podman(1)](podman.1.md)**, **[podman-create(1)](podman-create.1.md)**, **[podman-run(1)](podman-run.1.md)**
## HISTORY
August 2022, Originally written by Charlie Doern <cdoern@redhat.com>