b24b4f
% containers.conf 5 Container engine configuration file
b24b4f
b24b4f
# NAME
b24b4f
containers.conf - The container engine configuration file specifies default
b24b4f
configuration options and command-line flags for container engines.
b24b4f
b24b4f
# DESCRIPTION
b24b4f
Container engines like Podman & Buildah read containers.conf file, if it exists
b24b4f
and modify the defaults for running containers on the host. containers.conf uses
b24b4f
a TOML format that can be easily modified and versioned.
b24b4f
b24b4f
Container engines read the /usr/share/containers/containers.conf and
b24b4f
/etc/containers/containers.conf, and /etc/containers/containers.conf.d/*.conf files
b24b4f
if they exist. When running in rootless mode, they also read
b24b4f
$HOME/.config/containers/containers.conf and
b24b4f
$HOME/.config/containers/containers.conf.d/*.conf files.
b24b4f
b24b4f
Fields specified in containers conf override the default options, as well as
b24b4f
options in previously read containers.conf files.
b24b4f
b24b4f
Config files in the `.d` directories, are added in alpha numeric sorted order and must end in `.conf`.
b24b4f
b24b4f
Not all options are supported in all container engines.
b24b4f
b24b4f
Note container engines also use other configuration files for configuring the environment.
b24b4f
b24b4f
* `storage.conf` for configuration of container and images storage.
b24b4f
* `registries.conf` for definition of container registires to search while pulling.
b24b4f
container images.
b24b4f
* `policy.conf` for controlling which images can be pulled to the system.
b24b4f
b24b4f
# FORMAT
b24b4f
The [TOML format][toml] is used as the encoding of the configuration file.
b24b4f
Every option is nested under its table. No bare options are used. The format of
b24b4f
TOML can be simplified to:
b24b4f
b24b4f
    [table1]
b24b4f
    option = value
b24b4f
b24b4f
    [table2]
b24b4f
    option = value
b24b4f
b24b4f
    [table3]
b24b4f
    option = value
b24b4f
b24b4f
    [table3.subtable1]
b24b4f
    option = value
b24b4f
b24b4f
## CONTAINERS TABLE
b24b4f
The containers table contains settings to configure and manage the OCI runtime.
b24b4f
b24b4f
**annotations** = []
b24b4f
List of annotations. Specified as "key=value" pairs to be added to all containers.
b24b4f
b24b4f
Example: "run.oci.keep_original_groups=1"
b24b4f
b24b4f
**apparmor_profile**="container-default"
b24b4f
b24b4f
Used to change the name of the default AppArmor profile of container engines.
b24b4f
The default profile name is "container-default".
b24b4f
b24b4f
**cgroups**="enabled"
b24b4f
b24b4f
Determines  whether  the  container will create CGroups.
b24b4f
Options are:
b24b4f
  `enabled`   Enable cgroup support within container
b24b4f
  `disabled`  Disable cgroup support, will inherit cgroups from parent
b24b4f
  `no-conmon` Do not create a cgroup dedicated to conmon.
b24b4f
b24b4f
**cgroupns**="private"
b24b4f
b24b4f
Default way to to create a cgroup namespace for the container.
b24b4f
Options are:
b24b4f
`private` Create private Cgroup Namespace for the container.
b24b4f
`host`    Share host Cgroup Namespace with the container.
b24b4f
b24b4f
**default_capabilities**=[]
b24b4f
b24b4f
List of default capabilities for containers.
b24b4f
b24b4f
The default list is:
b24b4f
```
b24b4f
default_capabilities = [
b24b4f
"AUDIT_WRITE",
b24b4f
      "CHOWN",
b24b4f
      "DAC_OVERRIDE",
b24b4f
      "FOWNER",
b24b4f
      "FSETID",
b24b4f
      "KILL",
b24b4f
      "MKNOD",
b24b4f
      "NET_BIND_SERVICE",
b24b4f
      "NET_RAW",
b24b4f
      "SETGID",
b24b4f
      "SETPCAP",
b24b4f
      "SETUID",
b24b4f
      "SYS_CHROOT",
b24b4f
]
b24b4f
```
b24b4f
b24b4f
**default_sysctls**=[]
b24b4f
b24b4f
A list of sysctls to be set in containers by default,
b24b4f
specified as "name=value".
b24b4f
b24b4f
Example:"net.ipv4.ping_group_range=0 1000".
b24b4f
b24b4f
**default_ulimits**=[]
b24b4f
b24b4f
A list of ulimits to be set in containers by default,
b24b4f
specified as "name=soft-limit:hard-limit".
b24b4f
b24b4f
Example: "nofile=1024:2048".
b24b4f
b24b4f
**devices**=[]
b24b4f
b24b4f
List of devices.
b24b4f
Specified as 'device-on-host:device-on-container:permissions'.
b24b4f
b24b4f
Example: "/dev/sdc:/dev/xvdc:rwm".
b24b4f
b24b4f
**dns_options**=[]
b24b4f
b24b4f
List of default DNS options to be added to /etc/resolv.conf inside of the
b24b4f
container.
b24b4f
b24b4f
**dns_searches**=[]
b24b4f
b24b4f
List of default DNS search domains to be added to /etc/resolv.conf inside of
b24b4f
the container.
b24b4f
b24b4f
**dns_servers**=[]
b24b4f
b24b4f
A list of dns servers to override the DNS configuration passed to the
b24b4f
container. The special value “none” can be specified to disable creation of
b24b4f
/etc/resolv.conf in the container.
b24b4f
b24b4f
**env**=["PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", "TERM=xterm"]
b24b4f
b24b4f
Environment variable list for the container process, used for passing
b24b4f
environment variables to the container.
b24b4f
b24b4f
**env_host**=false
b24b4f
b24b4f
Pass all host environment variables into the container.
b24b4f
b24b4f
**http_proxy**=true
b24b4f
b24b4f
Default proxy environment variables will be passed into the container.
b24b4f
The environment variables passed in include:
b24b4f
`http_proxy`, `https_proxy`, `ftp_proxy`, `no_proxy`, and the upper case
b24b4f
versions of these. The `no_proxy` option is needed when host system uses a proxy
b24b4f
but container should not use proxy. Proxy environment variables specified for
b24b4f
the container in any other way will override the values passed from the host.
b24b4f
b24b4f
**init**=false
b24b4f
b24b4f
Run an init inside the container that forwards signals and reaps processes.
b24b4f
b24b4f
**init_path**="/usr/libexec/podman/catatonit"
b24b4f
b24b4f
Path to the container-init binary, which forwards signals and reaps processes
b24b4f
within containers. Note that the container-init binary will only be used when
b24b4f
the `--init` for podman-create and podman-run is set.
b24b4f
b24b4f
**ipcns**="private"
b24b4f
b24b4f
Default way to to create a IPC namespace for the container.
b24b4f
Options are:
b24b4f
  `private` Create private IPC Namespace for the container.
b24b4f
  `host`    Share host IPC Namespace with the container.
b24b4f
b24b4f
**keyring**=true
b24b4f
b24b4f
Indicates whether the container engines create a kernel keyring for use within
b24b4f
the container.
b24b4f
b24b4f
**label**=true
b24b4f
b24b4f
Indicates whether the container engine uses MAC(SELinux) container separation via labeling. This option is ignored on disabled systems.
b24b4f
b24b4f
**log_driver**="k8s-file"
b24b4f
b24b4f
Logging driver for the container. Available options: `k8s-file` and `journald`.
b24b4f
b24b4f
**log_size_max**=-1
b24b4f
b24b4f
Maximum size allowed for the container's log file. Negative numbers indicate
b24b4f
that no size limit is imposed. If it is positive, it must be >= 8192 to
b24b4f
match/exceed conmon's read buffer. The file is truncated and re-opened so the
b24b4f
limit is never exceeded.
b24b4f
b24b4f
**log_tag**=""
b24b4f
b24b4f
Default format tag for container log messages. This is useful for creating a specific tag for container log messages. Container log messages default to using the truncated container ID as a tag.
b24b4f
b24b4f
**netns**="private"
b24b4f
b24b4f
Default way to to create a NET namespace for the container.
b24b4f
Options are:
b24b4f
  `private` Create private NET Namespace for the container.
b24b4f
  `host`    Share host NET Namespace with the container.
b24b4f
  `none`    Containers do not use the network.
b24b4f
b24b4f
**no_hosts**=false
b24b4f
b24b4f
Create /etc/hosts for the container. By default, container engines manage
b24b4f
/etc/hosts, automatically adding  the container's  own  IP  address.
b24b4f
b24b4f
**pidns**="private"
b24b4f
b24b4f
Default way to to create a PID namespace for the container.
b24b4f
Options are:
b24b4f
  `private` Create private PID Namespace for the container.
b24b4f
  `host`    Share host PID Namespace with the container.
b24b4f
b24b4f
**pids_limit**=1024
b24b4f
b24b4f
Maximum number of processes allowed in a container. 0 indicates that no limit
b24b4f
is imposed.
b24b4f
b24b4f
**prepare_volume_on_create**=false
b24b4f
b24b4f
Copy the content from the underlying image into the newly created volume when the container is created instead of when it is started. If `false`, the container engine will not copy the content until the container is started. Setting it to `true` may have negative performance implications.
b24b4f
b24b4f
**seccomp_profile**="/usr/share/containers/seccomp.json"
b24b4f
b24b4f
Path to the seccomp.json profile which is used as the default seccomp profile
b24b4f
for the runtime.
b24b4f
b24b4f
**shm_size**="65536k"
b24b4f
b24b4f
Size of `/dev/shm`. The format is `<number><unit>`. `number` must be greater
b24b4f
than `0`.
b24b4f
Unit is optional and can be:
b24b4f
`b` (bytes), `k` (kilobytes), `m`(megabytes), or `g` (gigabytes).
b24b4f
If you omit the unit, the system uses bytes. If you omit the size entirely,
b24b4f
the system uses `65536k`.
b24b4f
b24b4f
**tz=**""
b24b4f
b24b4f
Set timezone in container. Takes IANA timezones as well as `local`, which sets the timezone in the container to match the host machine.
b24b4f
If not set, then containers will run with the time zone specified in the image.
b24b4f
b24b4f
Examples:
b24b4f
  `tz="local"`
b24b4f
  `tz="America/New_York"`
b24b4f
b24b4f
**umask**="0022"
b24b4f
b24b4f
Sets umask inside the container.
b24b4f
b24b4f
**userns**="host"
b24b4f
b24b4f
Default way to to create a USER namespace for the container.
b24b4f
Options are:
b24b4f
  `private` Create private USER Namespace for the container.
b24b4f
  `host`    Share host USER Namespace with the container.
b24b4f
b24b4f
**userns_size**=65536
b24b4f
b24b4f
Number of UIDs to allocate for the automatic container creation. UIDs are
b24b4f
allocated from the “container” UIDs listed in /etc/subuid & /etc/subgid.
b24b4f
b24b4f
**utsns**="private"
b24b4f
b24b4f
Default way to to create a UTS namespace for the container.
b24b4f
Options are:
b24b4f
  `private` Create private UTS Namespace for the container.
b24b4f
  `host`    Share host UTS Namespace with the container.
b24b4f
b24b4f
b24b4f
## NETWORK TABLE
b24b4f
The `network` table contains settings pertaining to the management of CNI
b24b4f
plugins.
b24b4f
b24b4f
**network_backend**=""
b24b4f
b24b4f
Network backend determines what network driver will be used to set up and tear down container networks.
b24b4f
Valid values are "cni" and "netavark".
b24b4f
The default value is empty which means that it will automatically choose CNI or netavark. If there are
b24b4f
already containers/images or CNI networks preset it will choose CNI.
b24b4f
b24b4f
Before changing this value all containers must be stopped otherwise it is likely that
b24b4f
iptables rules and network interfaces might leak on the host. A reboot will fix this.
b24b4f
b24b4f
**cni_plugin_dirs**=[]
b24b4f
b24b4f
List of paths to directories where CNI plugin binaries are located.
b24b4f
b24b4f
The default list is:
b24b4f
```
b24b4f
cni_plugin_dirs = [
b24b4f
  "/usr/local/libexec/cni",
b24b4f
  "/usr/libexec/cni",
b24b4f
  "/usr/local/lib/cni",
b24b4f
  "/usr/lib/cni",
b24b4f
  "/opt/cni/bin",
b24b4f
]
b24b4f
```
b24b4f
b24b4f
**default_network**="podman"
b24b4f
b24b4f
The network name of the default network to attach pods to.
b24b4f
b24b4f
**default_subnet**="10.88.0.0/16"
b24b4f
b24b4f
The subnet to use for the default network (named above in **default_network**).
b24b4f
If the default network does not exist, it will be automatically created the first time a tool is run using this subnet.
b24b4f
b24b4f
**network_config_dir**="/etc/cni/net.d/"
b24b4f
b24b4f
Path to the directory where network configuration files are located.
b24b4f
For the CNI backend the default is "/etc/cni/net.d" as root
b24b4f
and "$HOME/.config/cni/net.d" as rootless.
b24b4f
For the netavark backend "/etc/containers/networks" is used as root
b24b4f
and "$graphroot/networks" as rootless.
b24b4f
b24b4f
**volumes**=[]
b24b4f
b24b4f
List of volumes.
b24b4f
Specified as "directory-on-host:directory-in-container:options".
b24b4f
b24b4f
Example:  "/db:/var/lib/db:ro".
b24b4f
b24b4f
## ENGINE TABLE
b24b4f
The `engine` table contains configuration options used to set up container engines such as Podman and Buildah.
b24b4f
b24b4f
**active_service**=""
b24b4f
b24b4f
Name of destination for accessing the Podman service. See SERVICE DESTINATION TABLE below.
b24b4f
b24b4f
**cgroup_manager**="systemd"
b24b4f
b24b4f
The cgroup management implementation used for the runtime. Supports `cgroupfs`
b24b4f
and `systemd`.
b24b4f
b24b4f
**conmon_env_vars**=[]
b24b4f
b24b4f
Environment variables to pass into Conmon.
b24b4f
b24b4f
**conmon_path**=[]
b24b4f
b24b4f
Paths to search for the conmon container manager binary. If the paths are
b24b4f
empty or no valid path was found, then the `$PATH` environment variable will be
b24b4f
used as the fallback.
b24b4f
b24b4f
The default list is:
b24b4f
```
b24b4f
conmon_path=[
b24b4f
    "/usr/libexec/podman/conmon",
b24b4f
    "/usr/local/libexec/podman/conmon",
b24b4f
    "/usr/local/lib/podman/conmon",
b24b4f
    "/usr/bin/conmon",
b24b4f
    "/usr/sbin/conmon",
b24b4f
    "/usr/local/bin/conmon",
b24b4f
    "/usr/local/sbin/conmon",
b24b4f
    "/run/current-system/sw/bin/conmon",
b24b4f
]
b24b4f
```
b24b4f
b24b4f
**detach_keys**="ctrl-p,ctrl-q"
b24b4f
b24b4f
Keys sequence used for detaching a container.
b24b4f
Specify the keys sequence used to detach a container.
b24b4f
Format is a single character `[a-Z]` or a comma separated sequence of
b24b4f
`ctrl-<value>`, where `<value>` is one of:
b24b4f
`a-z`, `@`, `^`, `[`, `\`, `]`, `^` or `_`
b24b4f
b24b4f
**enable_port_reservation**=true
b24b4f
b24b4f
Determines whether the engine will reserve ports on the host when they are
b24b4f
forwarded to containers. When enabled, when ports are forwarded to containers,
b24b4f
they are held open by conmon as long as the container is running, ensuring that
b24b4f
they cannot be reused by other programs on the host. However, this can cause
b24b4f
significant memory usage if a container has many ports forwarded to it.
b24b4f
Disabling this can save memory.
b24b4f
b24b4f
**env**=[]
b24b4f
b24b4f
Environment variables to be used when running the container engine (e.g., Podman, Buildah). For example "http_proxy=internal.proxy.company.com".
b24b4f
Note these environment variables will not be used within the container. Set the env section under [containers] table,
b24b4f
if you want to set environment variables for the container.
b24b4f
b24b4f
**events_logfile_path**=""
b24b4f
b24b4f
Define where event logs will be stored, when events_logger is "file".
b24b4f
b24b4f
**events_logger**="journald"
b24b4f
b24b4f
Default method to use when logging events.
b24b4f
Valid values: `file`, `journald`, and `none`.
b24b4f
b24b4f
**helper_binaries_dir**=["/usr/libexec/podman", ...]
b24b4f
b24b4f
A is a list of directories which are used to search for helper binaries.
b24b4f
b24b4f
The default paths on Linux are:
b24b4f
- `/usr/local/libexec/podman`
b24b4f
- `/usr/local/lib/podman`
b24b4f
- `/usr/libexec/podman`
b24b4f
- `/usr/lib/podman`
b24b4f
b24b4f
The default paths on macOS are:
b24b4f
- `/usr/local/opt/podman/libexec`
b24b4f
-	`/opt/homebrew/bin`
b24b4f
-	`/opt/homebrew/opt/podman/libexec`
b24b4f
- `/usr/local/bin`
b24b4f
-	`/usr/local/libexec/podman`
b24b4f
-	`/usr/local/lib/podman`
b24b4f
-	`/usr/libexec/podman`
b24b4f
-	`/usr/lib/podman`
b24b4f
b24b4f
The default path on Windows is:
b24b4f
- `C:\Program Files\RedHat\Podman`
b24b4f
b24b4f
**hooks_dir**=["/etc/containers/oci/hooks.d", ...]
b24b4f
b24b4f
Path to the OCI hooks directories for automatically executed hooks.
b24b4f
b24b4f
**image_default_format**="oci"|"v2s2"|"v2s1"
b24b4f
b24b4f
Manifest Type (oci, v2s2, or v2s1) to use when pulling, pushing, building
b24b4f
container images. By default images pulled and pushed match the format of the
b24b4f
source image. Building/committing defaults to OCI.
b24b4f
Note: **image_build_format** is deprecated.
b24b4f
b24b4f
**image_default_transport**="docker://"
b24b4f
b24b4f
Default transport method for pulling and pushing images.
b24b4f
b24b4f
**image_parallel_copies**=0
b24b4f
b24b4f
Maximum number of image layers to be copied (pulled/pushed) simultaneously.
b24b4f
Not setting this field will fall back to containers/image defaults. (6)
b24b4f
b24b4f
**infra_command**="/pause"
b24b4f
b24b4f
Infra (pause) container image command for pod infra containers. When running a
b24b4f
pod, we start a `/pause` process in a container to hold open the namespaces
b24b4f
associated with the pod. This container does nothing other then sleep,
b24b4f
reserving the pods resources for the lifetime of the pod.
b24b4f
b24b4f
**infra_image**=""
b24b4f
b24b4f
Infra (pause) container image for pod infra containers. When running a
b24b4f
pod, we start a `pause` process in a container to hold open the namespaces
b24b4f
associated with the pod. This container does nothing other then sleep,
b24b4f
reserving the pods resources for the lifetime of the pod. By default container
b24b4f
engines run a builtin container using the pause executable. If you want override
b24b4f
specify an image to pull.
b24b4f
b24b4f
**lock_type**="shm"
b24b4f
b24b4f
Specify the locking mechanism to use; valid values are "shm" and "file".
b24b4f
Change the default only if you are sure of what you are doing, in general
b24b4f
"file" is useful only on platforms where cgo is not available for using the
b24b4f
faster "shm" lock type. You may need to run "podman system renumber" after you
b24b4f
change the lock type.
b24b4f
b24b4f
**machine_enabled**=false
b24b4f
b24b4f
Indicates if Podman is running inside a VM via Podman Machine.
b24b4f
Podman uses this value to do extra setup around networking from the
b24b4f
container inside the VM to to host.
b24b4f
b24b4f
**multi_image_archive**=false
b24b4f
b24b4f
Allows for creating archives (e.g., tarballs) with more than one image. Some container engines, such as Podman, interpret additional arguments as tags for one image and hence do not store more than one image. The default behavior can be altered with this option.
b24b4f
b24b4f
**namespace**=""
b24b4f
b24b4f
Default engine namespace. If the engine is joined to a namespace, it will see
b24b4f
only containers and pods that were created in the same namespace, and will
b24b4f
create new containers and pods in that namespace. The default namespace is "",
b24b4f
which corresponds to no namespace. When no namespace is set, all containers
b24b4f
and pods are visible.
b24b4f
b24b4f
**network_cmd_path**=""
b24b4f
b24b4f
Path to the slirp4netns binary.
b24b4f
b24b4f
**network_cmd_options**=["enable_ipv6=true",]
b24b4f
b24b4f
Default options to pass to the slirp4netns binary.
b24b4f
b24b4f
Valid options values are:
b24b4f
b24b4f
  - **allow_host_loopback=true|false**: Allow the slirp4netns to reach the host loopback IP (`10.0.2.2`, which is added to `/etc/hosts` as `host.containers.internal` for your convenience). Default is false.
b24b4f
  - **mtu=MTU**: Specify the MTU to use for this network. (Default is `65520`).
b24b4f
  - **cidr=CIDR**: Specify ip range to use for this network. (Default is `10.0.2.0/24`).
b24b4f
  - **enable_ipv6=true|false**: Enable IPv6. Default is false. (Required for `outbound_addr6`).
b24b4f
  - **outbound_addr=INTERFACE**: Specify the outbound interface slirp should bind to (ipv4 traffic only).
b24b4f
  - **outbound_addr=IPv4**: Specify the outbound ipv4 address slirp should bind to.
b24b4f
  - **outbound_addr6=INTERFACE**: Specify the outbound interface slirp should bind to (ipv6 traffic only).
b24b4f
  - **outbound_addr6=IPv6**: Specify the outbound ipv6 address slirp should bind to.
b24b4f
  - **port_handler=rootlesskit**: Use rootlesskit for port forwarding. Default.
b24b4f
  Note: Rootlesskit changes the source IP address of incoming packets to a IP address in the container network namespace, usually `10.0.2.100`. If your application requires the real source IP address, e.g. web server logs, use the slirp4netns port handler. The rootlesskit port handler is also used for rootless containers when connected to user-defined networks.
b24b4f
  - **port_handler=slirp4netns**: Use the slirp4netns port forwarding, it is slower than rootlesskit but preserves the correct source IP address. This port handler cannot be used for user-defined networks.
b24b4f
b24b4f
**no_pivot_root**=false
b24b4f
b24b4f
Whether to use chroot instead of pivot_root in the runtime.
b24b4f
b24b4f
**num_locks**=2048
b24b4f
b24b4f
Number of locks available for containers and pods. Each created container or
b24b4f
pod consumes one lock. The default number available is 2048. If this is
b24b4f
changed, a lock renumbering must be performed, using the
b24b4f
`podman system renumber` command.
b24b4f
b24b4f
**pull_policy**="always"|"missing"|"never"
b24b4f
b24b4f
Pull image before running or creating a container. The default is **missing**.
b24b4f
b24b4f
- **missing**: attempt to pull the latest image from the registries listed in registries.conf if a local image does not exist. Raise an error if the image is not in any listed registry and is not present locally.
b24b4f
- **always**: pull the image from the first registry it is found in as listed in registries.conf. Raise an error if not found in the registries, even if the image is present locally.
b24b4f
- **never**: do not pull the image from the registry, use only the local version. Raise an error if the image is not present locally.
b24b4f
b24b4f
**remote** = false
b24b4f
Indicates whether the application should be running in remote mode. This flag modifies the
b24b4f
--remote option on container engines. Setting the flag to true will default `podman --remote=true` for access to the remote Podman service.
b24b4f
b24b4f
**runtime**=""
b24b4f
b24b4f
Default OCI specific runtime in runtimes that will be used by default. Must
b24b4f
refer to a member of the runtimes table. Default runtime will be searched for
b24b4f
on the system using the priority: "crun", "runc", "kata".
b24b4f
b24b4f
**runtime_supports_json**=["crun", "runc", "kata", "runsc", "krun"]
b24b4f
b24b4f
The list of the OCI runtimes that support `--format=json`.
b24b4f
b24b4f
**runtime_supports_kvm**=["kata", "krun"]
b24b4f
b24b4f
The list of OCI runtimes that support running containers with KVM separation.
b24b4f
b24b4f
**runtime_supports_nocgroups**=["crun", "krun"]
b24b4f
b24b4f
The list of OCI runtimes that support running containers without CGroups.
b24b4f
b24b4f
**image_copy_tmp_dir**="/var/tmp"
b24b4f
b24b4f
Default location for storing temporary container image content. Can be
b24b4f
overridden with the TMPDIR environment variable. If you specify "storage", then
b24b4f
the location of the container/storage tmp directory will be used. If set then it
b24b4f
is the users responsibility to cleanup storage. Configure tmpfiles.d(5) to
b24b4f
cleanup storage.
b24b4f
b24b4f
**service_timeout**=**5**
b24b4f
b24b4f
Number of seconds to wait without a connection  before the
b24b4f
`podman system service` times out and exits
b24b4f
b24b4f
**static_dir**="/var/lib/containers/storage/libpod"
b24b4f
b24b4f
Directory for persistent libpod files (database, etc).
b24b4f
By default this will be configured relative to where containers/storage
b24b4f
stores containers.
b24b4f
b24b4f
**stop_timeout**=10
b24b4f
b24b4f
Number of seconds to wait for container to exit before sending kill signal.
b24b4f
b24b4f
**tmp_dir**="/run/libpod"
b24b4f
b24b4f
The path to a temporary directory to store per-boot container.
b24b4f
Must be a tmpfs (wiped after reboot).
b24b4f
b24b4f
**volume_path**="/var/lib/containers/storage/volumes"
b24b4f
b24b4f
Directory where named volumes will be created in using the default volume
b24b4f
driver.
b24b4f
By default this will be configured relative to where containers/storage store
b24b4f
containers. This convention is followed by the default volume driver, but may
b24b4f
not be by other drivers.
b24b4f
b24b4f
**chown_copied_files**=true
b24b4f
b24b4f
Determines whether file copied into a container will have changed ownership to
b24b4f
the primary uid/gid of the container.
b24b4f
b24b4f
**compression_format**=""
b24b4f
b24b4f
Specifies the compression format to use when pushing an image. Supported values are: `gzip`, `zstd` and `zstd:chunked`.
b24b4f
b24b4f
## SERVICE DESTINATION TABLE
b24b4f
The `service_destinations` table contains configuration options used to set up remote connections to the podman service for the podman API.
b24b4f
b24b4f
**[service_destinations.{name}]**
b24b4f
URI to access the Podman service
b24b4f
**uri="ssh://user@production.example.com/run/user/1001/podman/podman.sock"**
b24b4f
b24b4f
  Example URIs:
b24b4f
b24b4f
- **rootless local**  - unix://run/user/1000/podman/podman.sock
b24b4f
- **rootless remote** - ssh://user@engineering.lab.company.com/run/user/1000/podman/podman.sock
b24b4f
- **rootfull local**  - unix://run/podman/podman.sock
b24b4f
- **rootfull remote** - ssh://root@10.10.1.136:22/run/podman/podman.sock
b24b4f
b24b4f
**identity="~/.ssh/id_rsa**
b24b4f
b24b4f
Path to file containing ssh identity key
b24b4f
b24b4f
**[engine.volume_plugins]**
b24b4f
b24b4f
A table of all the enabled volume plugins on the system. Volume plugins can be
b24b4f
used as the backend for Podman named volumes. Individual plugins are specified
b24b4f
below, as a map of the plugin name (what the plugin will be called) to its path
b24b4f
(filepath of the plugin's unix socket).
b24b4f
b24b4f
b24b4f
## SECRET TABLE
b24b4f
The `secret` table contains settings for the configuration of the secret subsystem.
b24b4f
b24b4f
**driver**=file
b24b4f
b24b4f
Name of the secret driver to be used.
b24b4f
Currently valid values are:
b24b4f
  * file
b24b4f
  * pass
b24b4f
b24b4f
**[secrets.opts]**
b24b4f
b24b4f
The driver specific options object.
b24b4f
b24b4f
## MACHINE TABLE
b24b4f
The `machine` table contains configurations for podman machine VMs
b24b4f
b24b4f
**cpus**=1
b24b4f
Number of CPU's a machine is created with.
b24b4f
b24b4f
**disk_size**=10
b24b4f
b24b4f
The size of the disk in GB created when init-ing a podman-machine VM
b24b4f
b24b4f
**image**=""
b24b4f
b24b4f
Default image used when creating a new VM using `podman machine init`.
b24b4f
Options: On Linux/Mac, `testing`, `stable`, `next`. On Windows, the major
b24b4f
version of the OS (e.g `35`). For all platforms you can alternatively specify
b24b4f
a custom path or download URL to an image. The default is `testing` on
b24b4f
Linux/Mac, and `35` on Windows.
b24b4f
b24b4f
**memory**=2048
b24b4f
b24b4f
Memory in MB a machine is created with.
b24b4f
b24b4f
**user**=""
b24b4f
b24b4f
Username to use and create on the podman machine OS for rootless container
b24b4f
access. The default value is `user`. On Linux/Mac the default is`core`.
b24b4f
b24b4f
# FILES
b24b4f
b24b4f
**containers.conf**
b24b4f
b24b4f
Distributions often provide a `/usr/share/containers/containers.conf` file to
b24b4f
define default container configuration. Administrators can override fields in
b24b4f
this file by creating `/etc/containers/containers.conf` to specify their own
b24b4f
configuration. Rootless users can further override fields in the config by
b24b4f
creating a config file stored in the `$HOME/.config/containers/containers.conf` file.
b24b4f
b24b4f
If the `CONTAINERS_CONF` path environment variable is set, just
b24b4f
this path will be used. This is primarily used for testing.
b24b4f
b24b4f
Fields specified in the containers.conf file override the default options, as
b24b4f
well as options in previously read containers.conf files.
b24b4f
b24b4f
**storage.conf**
b24b4f
b24b4f
The `/etc/containers/storage.conf` file is the default storage configuration file.
b24b4f
Rootless users can override fields in the storage config by creating
b24b4f
`$HOME/.config/containers/storage.conf`.
b24b4f
b24b4f
If the `CONTAINERS_STORAGE_CONF` path environment variable is set, this path
b24b4f
is used for the storage.conf file rather than the default.
b24b4f
This is primarily used for testing.
b24b4f
b24b4f
# SEE ALSO
b24b4f
containers-storage.conf(5), containers-policy.json(5), containers-registries.conf(5), tmpfiles.d(5)
b24b4f
b24b4f
[toml]: https://github.com/toml-lang/toml