containers-storage.conf

title: containers-storage.conf(5)

text:
# containers-storage.conf(5)

## NAME
storage.conf - Syntax of Container Storage configuration file

## DESCRIPTION
The STORAGE configuration file specifies all of the available container storage options for tools using shared container storage, but in a TOML format that can be more easily modified and versioned.

## FORMAT
The [TOML format][toml] is used as the encoding of the configuration file. Every option and subtable listed here is nested under a global "storage" table. No bare options are used. The format of TOML can be simplified to:

```
[table]
option = value
[table.subtable1]
option = value
[table.subtable2]
option = value
```

## STORAGE TABLE
The storage table supports the following options:

driver=""

Copy On Write (COW) container storage driver. Valid drivers are "overlay", "vfs", "aufs", "btrfs", and "zfs". Some drivers (for example, "zfs", "btrfs", and "aufs") may not work if your kernel lacks support for the filesystem. This field is required to guarantee proper operation. Valid rootless drivers are "btrfs", "overlay", and "vfs". Rootless users default to the driver defined in the system configuration when possible. When the system configuration uses an unsupported rootless driver, rootless users default to "overlay" if available, otherwise "vfs".

graphroot=""

container storage graph dir (default: "/var/lib/containers/storage") Default directory to store all writable content created by container storage programs. The rootless graphroot path supports environment variable substitutions (ie. $HOME/containers/storage). When changing the graphroot location on an SELINUX system, ensure the labeling matches the default locations labels with the following commands:

```
# semanage fcontext -a -e /var/lib/containers/storage /NEWSTORAGEPATH
# restorecon -R -v /NEWSTORAGEPATH
```

In rootless mode you would set

```
# semanage fcontext -a -e $HOME/.local/share/containers NEWSTORAGEPATH
$ restorecon -R -v /NEWSTORAGEPATH
```

rootless_storage_path="$HOME/.local/share/containers/storage"

Storage path for rootless users. By default the graphroot for rootless users is set to $XDG_DATA_HOME/containers/storage, if XDG_DATA_HOME is set. Otherwise $HOME/.local/share/containers/storage is used. This field can be used if administrators need to change the storage location for all users. The rootless storage path supports environment variable substitutions (ie. $HOME/containers/storage)

A common use case for this field is to provide a local storage directory when user home directories are NFS-mounted (podman does not support container storage over NFS).

imagestore=""

The image storage path (the default is assumed to be the same as graphroot). Path of the imagestore, which is different from graphroot. By default, images in the storage library are stored in the graphroot. If imagestore is provided, newly pulled images will be stored in the imagestore location. All other storage continues to be stored in the graphroot. When using the overlay driver, images previously stored in the graphroot remain accessible. Internally, the storage library mounts graphroot as an additionalImageStore to allow this behavior.

A common use case for the imagestore field is users who need to split filesystems in different partitions. The imagestore partition stores images and the graphroot partition stores container content created from the images.

Imagestore, if set, must be different from graphroot.

runroot=""

container storage run dir (default: "/run/containers/storage") Default directory to store all temporary writable content created by container storage programs. The rootless runroot path supports environment variable substitutions (ie. $HOME/containers/storage)

driver_priority=[]

Priority list for the storage drivers that will be tested one after the other to pick the storage driver if it is not defined. The first storage driver in this list that can be used, will be picked as the new one and all subsequent ones will not be tried. If all drivers in this list are not viable, then all known drivers will be tried and the first working one will be picked. By default, the storage driver is set via the driver option. If it is not defined, then the best driver will be picked according to the current platform. This option allows you to override this internal priority list with a custom one to prefer certain drivers. Setting this option only has an effect if the local storage has not been initialized yet and the driver name is not set.

transient_store = "false"|"true"

Transient store mode makes all container metadata be saved in temporary storage (i.e. runroot above). This is faster, but doesn't persist across reboots. Additional garbage collection must also be performed at boot-time, so this option should remain disabled in most configurations. (default: false)

### STORAGE OPTIONS TABLE
The storage.options table supports the following options:

additionalimagestores=[]

Paths to additional container image stores. Usually these are read/only and stored on remote network shares.

root-auto-userns-user=""

Root-auto-userns-user is a user name which can be used to look up one or more UID/GID ranges in the /etc/subuid and /etc/subgid file. These ranges will be partitioned to containers configured to create automatically a user namespace. Containers configured to automatically create a user namespace can still overlap with containers having an explicit mapping set. This setting is ignored when running as rootless.

auto-userns-min-size=1024

Auto-userns-min-size is the minimum size for a user namespace created automatically.

auto-userns-max-size=65536

Auto-userns-max-size is the maximum size for a user namespace created automatically.

disable-volatile=true

If disable-volatile is set, then the "volatile" mount optimization is disabled for all the containers.

### STORAGE PULL OPTIONS TABLE
The storage.options.pull_options table supports the following keys:

enable_partial_images="true"|"false"

Enable the "zstd:chunked" feature, which allows partial pulls, reusing

content that already exists on the system. This is disabled by default,

and must be explicitly enabled to be used. For more on zstd:chunked, see

⟨https://github.com/containers/storage/blob/main/docs/containers-storage-zstd-chunked.md⟩.

This is a "string bool": "false"|"true" (cannot be native TOML boolean)

use_hard_links="false"|"true"

Tells containers/storage to use hard links rather then create new files in

the image, if an identical file already existed in storage.

This is a "string bool": "false"|"true" (cannot be native TOML boolean)

ostree_repos=""

Path to an ostree repository that might have

previously pulled content which can be used when attempting to avoid

pulling content from the container registry.

convert_images="false"|"true"

If set to "true", containers/storage will convert images that are

not already in zstd:chunked format to that format before processing

in order to take advantage of local deduplication and hard linking.

It is an expensive operation so it is not enabled by default.

This is a "string bool": "false"|"true" (cannot be native TOML boolean)

insecure_allow_unpredictable_image_contents="false"|"true"

This should almost never be set.

It allows partial pulls of images without guaranteeing that "partial

pulls" and non-partial pulls both result in consistent image contents.

This allows pulling estargz images and early versions of zstd:chunked images;

otherwise, these layers always use the traditional non-partial pull path.

This option should be enabled extremely rarely, only if all images that could

EVER be conceivably pulled on this system are guaranteed (e.g. using a signature policy)

to come from a build system trusted to never attack image integrity.

If this consistency enforcement were disabled, malicious images could be built

in a way designed to evade other audit mechanisms, so presence of most other audit

mechanisms is not a replacement for the above-mentioned need for all images to come

from a trusted build system.

As a side effect, enabling this option will also make image IDs unpredictable

(usually not equal to the traditional value matching the config digest).

This is a "string bool": "false"|"true" (cannot be native TOML boolean)

### STORAGE OPTIONS FOR AUFS TABLE
The storage.options.aufs table supports the following options:

mountopt=""

Comma separated list of default options to be used to mount container images. Suggested value "nodev". Mount options are documented in the mount(8) man page.

### STORAGE OPTIONS FOR BTRFS TABLE
The storage.options.btrfs table supports the following options:

min_space=""

Specifies the min space in a btrfs volume.

size=""

Maximum size of a container image. This flag can be used to set quota on the size of container images. (format: <number>[<unit>], where unit = b (bytes), k (kilobytes), m (megabytes), or g (gigabytes))

### STORAGE OPTIONS FOR OVERLAY TABLE
The storage.options.overlay table supports the following options:

ignore_chown_errors = "false"

ignore_chown_errors can be set to allow a non privileged user running with a single UID within a user namespace to run containers. The user can pull and use any image even those with multiple uids. Note multiple UIDs will be squashed down to the default uid in the container. These images will have no separation between the users in the container. (default: "false")

This is a "string bool": "false"|"true" (cannot be native TOML boolean)

inodes=""

Maximum inodes in a read/write layer. This flag can be used to set a quota on the inodes allocated for a read/write layer of a container.

force_mask = "0000|shared|private"

ForceMask specifies the permissions mask that is used for new files and directories. The values "shared" and "private" are accepted. (default: ""). Octal permission masks are also accepted.

•

``: Not set All files/directories, get set with the permissions identified within the image.

•

private: it is equivalent to 0700. All files/directories get set with 0700 permissions. The owner has rwx access to the files. No other users on the system can access the files. This setting could be used with networked based home directories.

•

shared: it is equivalent to 0755. The owner has rwx access to the files and everyone else can read, access and execute them. This setting is useful for sharing containers storage with other users. For instance, a storage owned by root could be shared to rootless users as an additional store. NOTE: All files within the image are made readable and executable by any user on the system. Even /etc/shadow within your image is now readable by any user.

OCTAL: Users can experiment with other OCTAL Permissions.

Note: The force_mask Flag is an experimental feature, it could change in the future. When "force_mask" is set the original permission mask is stored in the "user.containers.override_stat" xattr and the "mount_program" option must be specified. Mount programs like "/usr/bin/fuse-overlayfs" present the extended attribute permissions to processes within containers rather than the "force_mask" permissions.

mount_program=""

Specifies the path to a custom program to use instead of using kernel defaults for mounting the file system. In rootless mode, without the CAP_SYS_ADMIN capability, many kernels prevent mounting of overlay file systems, requiring you to specify a mount_program. The mount_program option is also required on systems where the underlying storage is btrfs, aufs, zfs, overlay, or ecryptfs based file systems.

mount_program = "/usr/bin/fuse-overlayfs"

mountopt=""

Comma separated list of default options to be used to mount container images. Suggested value "nodev". Mount options are documented in the mount(8) man page.

skip_mount_home="false"

Tell storage drivers to not create a PRIVATE bind mount on their home directory.

This is a "string bool": "false"|"true" (cannot be native TOML boolean)

size=""

Maximum size of a read/write layer. This flag can be used to set quota on the size of a read/write layer of a container. (format: <number>[<unit>], where unit = b (bytes), k (kilobytes), m (megabytes), or g (gigabytes))

use_composefs = "false"

Use ComposeFS to mount the data layers image. ComposeFS support is experimental and not recommended for production use.

This is a "string bool": "false"|"true" (cannot be native TOML boolean)

### STORAGE OPTIONS FOR VFS TABLE
The storage.options.vfs table supports the following options:

ignore_chown_errors = "false"

ignore_chown_errors can be set to allow a non privileged user running with a single UID within a user namespace to run containers. The user can pull and use any image even those with multiple uids. Note multiple UIDs will be squashed down to the default uid in the container. These images will have no separation between the users in the container.

This is a "string bool": "false"|"true" (cannot be native TOML boolean)

### STORAGE OPTIONS FOR ZFS TABLE
The storage.options.zfs table supports the following options:

fsname=""

File System name for the zfs driver

mountopt=""

Comma separated list of default options to be used to mount container images. Suggested value "nodev". Mount options are documented in the mount(8) man page.

size=""

Maximum size of a container image. This flag can be used to set quota on the size of container images. (format: <number>[<unit>], where unit = b (bytes), k (kilobytes), m (megabytes), or g (gigabytes))

## SELINUX LABELING
When running on an SELinux system, if you move the containers storage graphroot directory, you must make sure the labeling is correct.

Tell SELinux about the new containers storage by setting up an equivalence record. This tells SELinux to label content under the new path, as if it was stored under /var/lib/containers/storage.

```
semanage fcontext -a -e /var/lib/containers NEWSTORAGEPATH
restorecon -R -v NEWSTORAGEPATH
```

In rootless mode, you would set

```
semanage fcontext -a -e $HOME/.local/share/containers NEWSTORAGEPATH
restorecon -R -v NEWSTORAGEPATH
```

The semanage command above tells SELinux to setup the default labeling of NEWSTORAGEPATH to match /var/lib/containers. The restorecon command tells SELinux to apply the labels to the actual content.

Now all new content created in these directories will automatically be created with the correct label.

## QUOTAS
Container storage implements XFS project quota controls for overlay storage containers and volumes. The directory used to store the containers must be an XFS file system and be mounted with the pquota option.

Example /etc/fstab entry:

```
/dev/podman/podman-var /var xfs defaults,x-systemd.device-timeout=0,pquota 1 2
```

Container storage generates project ids for each container and builtin volume, but these project ids need to be unique for the XFS file system.

The xfs_quota tool can be used to assign a project id to the storage driver directory, e.g.:

```
echo 100000:/var/lib/containers/storage/overlay >> /etc/projects
echo 200000:/var/lib/containers/storage/volumes >> /etc/projects
echo storage:100000 >> /etc/projid
echo volumes:200000 >> /etc/projid
xfs_quota -x -c 'project -s storage volumes' /<xfs mount point>
```

In the example above, the storage directory project id will be used as a "start offset" and all containers will be assigned larger project ids (e.g. >= 100000). Then the volumes directory project id will be used as a "start offset" and all volumes will be assigned larger project ids (e.g. >= 200000). This is a way to prevent xfs_quota management from conflicting with containers/storage.

## FILES
Distributions often provide a /usr/share/containers/storage.conf file to define default storage configuration. Administrators can override this file by creating /etc/containers/storage.conf to specify their own configuration. Likewise rootless users can create a storage.conf file to override the system storage.conf files. Files should be stored in the $XDG_CONFIG_HOME/containers/storage.conf file. If $XDG_CONFIG_HOME is not set then the file $HOME/.config/containers/storage.conf is used.

Note: The storage.conf file overrides all other storage.conf files. Container engines run by users with a storage.conf file in their home directory do not use options in the system storage.conf files.

/etc/projects - XFS persistent project root definition /etc/projid - XFS project name mapping file

## SEE ALSO
semanage(8), restorecon(8), mount(8), fuse-overlayfs(1), xfs_quota(8), projects(5), projid(5)

## HISTORY
May 2017, Originally compiled by Dan Walsh ⟨dwalsh@redhat.com⟩ Format copied from crio.conf man page created by Aleksa Sarai ⟨asarai@suse.de⟩


containers-transports

package: containers-common

title: containers-transports(5)

text:
# containers-transports(5)

## NAME
containers-transports - description of supported transports for copying and storing container images

## DESCRIPTION
Tools which use the containers/image library, including skopeo(1), buildah(1), podman(1), all share a common syntax for referring to container images in various locations. The general form of the syntax is transport:details, where details are dependent on the specified transport, which are documented below.

The semantics of the image names ultimately depend on the environment where they are evaluated. For example: if evaluated on a remote server, image names might refer to paths on that server; relative paths are relative to the current directory of the image consumer. <!-- atomic: is deprecated and not documented here. -->

### containers-storage:[[storage-specifier]]{image-id|docker-reference[@image-id]}
An image located in a local containers storage. The format of docker-reference is described in detail in the docker transport.

The storage-specifier allows for referencing storage locations on the file system and has the format [[driver@]root[+run-root][:options]] where the optional driver refers to the storage driver (e.g., overlay or btrfs) and where root is an absolute path to the storage's root directory. The optional run-root can be used to specify the run directory of the storage where all temporary writable content is stored. The optional options are a comma-separated list of driver-specific options. Please refer to containers-storage.conf(5) for further information on the drivers and supported options.

### dir:path
An existing local directory path storing the manifest, layer tarballs and signatures as individual files. This is a non-standardized format, primarily useful for debugging or noninvasive container inspection.

### docker://docker-reference
An image in a registry implementing the "Docker Registry HTTP API V2". By default, uses the authorization state in $XDG_RUNTIME_DIR/containers/auth.json, which is set using podman-login(1). If the authorization state is not found there, $HOME/.docker/config.json is checked, which is set using docker-login(1). The containers-registries.conf(5) further allows for configuring various settings of a registry.

Note that a docker-reference has the following format: name[:tag | @digest]. While the docker transport does not support both a tag and a digest at the same time some formats like containers-storage do. Digests can also be used in an image destination as long as the manifest matches the provided digest.

The docker transport supports pushing images without a tag or digest to a registry when the image name is suffixed with @@unknown-digest@@. The name@@unknown-digest@@ reference format cannot be used with a reference that has a tag or digest. The digest of images can be explored with skopeo-inspect(1).

If name does not contain a slash, it is treated as docker.io/library/name. Otherwise, the component before the first slash is checked if it is recognized as a hostname:port ⟨i.e., it contains either a `.` or a `:`, or the component is exactly `localhost`⟩. If the first component of name is not recognized as a hostname[:port], name is treated as docker.io/name.

### docker-archive:path[:{docker-reference|@source-index}]
An image is stored in the docker-save(1) formatted file.

Unless a tool explicitly documents otherwise, a write to a docker-archive: destination completely overwrites path, replacing it with the single provided image.

The path can refer to a stream, e.g. docker-archive:/dev/stdin.

docker-reference must not contain a digest. Alternatively, for reading archives, @source-index is a zero-based index in archive manifest (to access untagged images). If neither docker-reference nor @_source_index is specified when reading an archive, the archive must contain exactly one image.

### docker-daemon:docker-reference|algo:digest
An image stored in the docker daemon's internal storage. The image must be specified as a docker-reference or in an alternative algo:digest format when being used as an image source. The algo:digest refers to the image ID reported by docker-inspect(1).

### oci:path[:{reference|@source-index}]
An image in a directory structure compliant with the "Open Container Image Layout Specification" at path.

The path value terminates at the first : character; any further : characters are not separators, but a part of reference. The reference is used to set, or match, the org.opencontainers.image.ref.name annotation in the top-level index. For reading images, @source-index is a zero-based index in manifest (to access untagged images). If neither reference nor @_source_index is specified when reading an image, the path must contain exactly one image.

### oci-archive:path[:reference]
An image in a tar(1) archive with contents compliant with the "Open Container Image Layout Specification" at path.

Unless a tool explicitly documents otherwise, a write to an oci-archive: destination completely overwrites path, replacing it with the single provided image.

The path value terminates at the first : character; any further : characters are not separators, but a part of reference. The reference is used to set, or match, the org.opencontainers.image.ref.name annotation in the top-level index. If reference is not specified when reading an archive, the archive must contain exactly one image.

### sif:path
An image using the Singularity image format at path.

Only reading images is supported, and not all scripts can be represented in the OCI format. <!-- tarball: can only usefully be used from Go callers who call tarballReference.ConfigUpdate, and is not documented here. -->

## Examples
The following examples demonstrate how some of the containers transports can be used. The examples use skopeo-copy(1) for copying container images.

Copying an image from one registry to another:

```
$ skopeo copy docker://docker.io/library/alpine:latest docker://localhost:5000/alpine:latest
```

Copying an image from a running Docker daemon to a directory in the OCI layout:

```
$ mkdir alpine-oci
$ skopeo copy docker-daemon:alpine:latest oci:alpine-oci
$ tree alpine-oci
test-oci/
├── blobs
│   └── sha256
│       ├── 83ef92b73cf4595aa7fe214ec6747228283d585f373d8f6bc08d66bebab531b7
│       ├── 9a6259e911dcd0a53535a25a9760ad8f2eded3528e0ad5604c4488624795cecc
│       └── ff8df268d29ccbe81cdf0a173076dcfbbea4bb2b6df1dd26766a73cb7b4ae6f7
├── index.json
└── oci-layout
2 directories, 5 files
```

Copying an image from a registry to the local storage:

```
$ skopeo copy docker://docker.io/library/alpine:latest containers-storage:alpine:latest
```

## SEE ALSO
docker-login(1), docker-save(1), podman-login(1), skopeo-copy(1), skopeo-inspect(1), tar(1), container-registries.conf(5), containers-storage.conf(5)

## AUTHORS
Miloslav Trmač ⟨mitr@redhat.com⟩ Valentin Rothberg ⟨rothberg@redhat.com⟩

branch: sisyphus


containers.conf

title: containers.conf(5)

text:
# containers.conf(5)

## NAME
containers.conf - The container engine configuration file specifies default configuration options and command-line flags for container engines.

## DESCRIPTION
Container engines like Podman Buildah read containers.conf file, if it exists and modify the defaults for running containers on the host. containers.conf uses a TOML format that can be easily modified and versioned.

Container engines read the /usr/share/containers/containers.conf, /etc/containers/containers.conf, and /etc/containers/containers.conf.d/*.conf for global configuration that effects all users. For user specific configuration it reads \$XDG_CONFIG_HOME/containers/containers.conf and \$XDG_CONFIG_HOME/containers/containers.conf.d/*.conf files. When $XDG_CONFIG_HOME is not set it falls back to using $HOME/.config instead.

Fields specified in containers conf override the default options, as well as options in previously read containers.conf files.

Config files in the .d directories, are added in alpha numeric sorted order and must end in .conf.

Not all options are supported in all container engines.

Note, container engines also use other configuration files for configuring the environment.

- storage.conf for configuration of container and images storage.

- registries.conf for definition of container registries to search while pulling. container images.

- policy.conf for controlling which images can be pulled to the system.

Note: If Podman is running in a virtual machine using podman machine (this includes Mac and Windows hosts), ensure that the configuration files are edited in the virtual machine by using podman machine ssh.

## ENVIRONMENT VARIABLES
If the CONTAINERS_CONF environment variable is set, all system and user config files are ignored and only the specified config file will be loaded.

If the CONTAINERS_CONF_OVERRIDE path environment variable is set, the config file will be loaded last even when CONTAINERS_CONF is set.

The values of both environment variables may be absolute or relative paths, for instance, CONTAINERS_CONF=/tmp/my_containers.conf.

## MODULES
A module is a containers.conf file located directly in or a sub-directory of the following three directories:

- \$XDG_CONFIG_HOME/containers/containers.conf.modules or \$HOME/.config/containers/containers.conf.modules if $XDG_CONFIG_HOME is not set.

- /etc/containers/containers.conf.modules

- /usr/share/containers/containers.conf.modules

Files in those locations are not loaded by default but only on-demand. They are loaded after all system and user configuration files but before CONTAINERS_CONF_OVERRIDE hence allowing for overriding system and user configs.

Modules are currently supported by podman(1). The podman --module flag allows for loading a module and can be specified multiple times. If the specified value is an absolute path, the config file will be loaded directly. Relative paths are resolved relative to the three module directories mentioned above and in the specified order such that modules in $XDG_CONFIG_HOME/$HOME allow for overriding those in /etc and /usr/share.

## APPENDING TO STRING ARRAYS
The default behavior during the loading sequence of multiple containers.conf files is to override previous data. To change the behavior from overriding to appending, you can set the append attribute as follows: array=["item-1", "item=2", ..., {append=true}]. Setting the append attribute instructs to append to this specific string array for the current and also subsequent loading steps. To change back to overriding, set {append=false}.

Consider the following example:

```
modules1.conf: env=["1=true"]
modules2.conf: env=["2=true"]
modules3.conf: env=["3=true", {append=true}]
modules4.conf: env=["4=true"]
```

After loading the files in the given order, the final contents are env=["2=true", "3=true", "4=true"]. If modules4.conf would set {append=false}, the final contents would be env=["4=true"].

## FORMAT
The TOML format ⟨https://github.com/toml-lang/toml⟩ is used as the encoding of the configuration file. Every option is nested under its table. No bare options are used. The format of TOML can be simplified to:

```
[table1]
option = value
[table2]
option = value
[table3]
option = value
[table3.subtable1]
option = value
```

## CONTAINERS TABLE
The containers table contains settings to configure and manage the OCI runtime.

annotations = []

List of annotations. Specified as "key=value" pairs to be added to all containers.

Example: "run.oci.keep_original_groups=1"

apparmor_profile="container-default"

Used to change the name of the default AppArmor profile of container engines. The default profile name is "container-default".

base_hosts_file=""

Base file to create the /etc/hosts file inside the container. This must either be an absolute path to a file on the host system, or one of the following special flags:

"" Use the host's /etc/hosts file (the default)

none Do not use a base file (i.e. start with an empty file)

image Use the container image's /etc/hosts file as base file

cgroup_conf=[]

List of cgroup_conf entries specifying a list of cgroup files to write to and their values. For example memory.high=1073741824 sets the memory.high limit to 1GB.

cgroups="enabled"

Determines whether the container will create CGroups. Options are:

enabled Enable cgroup support within container

disabled Disable cgroup support, will inherit cgroups from parent

no-conmon Do not create a cgroup dedicated to conmon.

cgroupns="private"

Default way to create a cgroup namespace for the container. Options are: private Create private Cgroup Namespace for the container. host Share host Cgroup Namespace with the container.

container_name_as_hostname=true|false

When no hostname is set for a container, use the container's name, with characters not valid for a hostname removed, as the hostname instead of the first 12 characters of the container's ID. Containers not running in a private UTS namespace will have their hostname set to the host's hostname regardless of this setting.

Default is false.

default_capabilities=[]

List of default capabilities for containers.

The default list is:

```
default_capabilities = [

      "CHOWN",

      "DAC_OVERRIDE",

      "FOWNER",

      "FSETID",

      "KILL",

      "NET_BIND_SERVICE",

      "SETFCAP",

      "SETGID",

      "SETPCAP",

      "SETUID",

      "SYS_CHROOT",
]
```

Note, by default container engines using containers.conf, run with less capabilities than Docker. Docker runs additionally with "AUDIT_WRITE", "MKNOD" and "NET_RAW". If you need to add one of these capabilities for a particular container, you can use the --cap-add option or edit your system's containers.conf.

default_sysctls=[]

A list of sysctls to be set in containers by default, specified as "name=value".

Example:"net.ipv4.ping_group_range=0 1000".

default_ulimits=[]

A list of ulimits to be set in containers by default, specified as "name=soft-limit:hard-limit".

Example: "nofile=1024:2048".

devices=[]

List of devices. Specified as 'device-on-host:device-on-container:permissions'.

Example: "/dev/sdc:/dev/xvdc:rwm".

dns_options=[]

List of default DNS options to be added to /etc/resolv.conf inside of the container.

dns_searches=[]

List of default DNS search domains to be added to /etc/resolv.conf inside of the container.

dns_servers=[]

A list of dns servers to override the DNS configuration passed to the container. The special value “none” can be specified to disable creation of /etc/resolv.conf in the container.

env=["PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"]

Environment variable list for the container process, used for passing environment variables to the container. If a variable is listed without a value, the value is copied from the host environment.

Note that this is only used when a container is created, not with subsequent commands like podman exec. This prevents variables in the config file from overwriting values specified on the command line when the container was created.

env_host=false

Pass all host environment variables into the container.

host_containers_internal_ip=""

Set the IP address the container should expect to connect to the host. The IP address is used by Podman to automatically add the host.containers.internal and host.docker.internal hostnames to the container's /etc/hosts file. It is also used for the host-gateway flag of Podman's --add-host CLI option. If no IP address is configured (the default), Podman will try to determine it automatically, but might fail to do so depending on the container's network setup. Adding these internal hostnames to /etc/hosts is silently skipped then. Set this config to none to never add the internal hostnames to /etc/hosts.

Note: If Podman is running in a virtual machine using podman machine (this includes Mac and Windows hosts), Podman resolves the host.containers.internal hostname via the podman machine (gvproxy) DNS resolver instead when it is empty. Also because the name will be resolved by the DNS name in gvproxy setting this to none has no effect. This option does not change the gvproxy behavior.

Note: This config doesn't affect the actual network setup, it just tells Podman the IP address it should expect. Configuring an IP address here doesn't ensure that the container can actually reach the host using this IP address.

http_proxy=true

Default proxy environment variables will be passed into the container. The environment variables passed in include: http_proxy, https_proxy, ftp_proxy, no_proxy, and the upper case versions of these. The no_proxy option is needed when host system uses a proxy but container should not use proxy. Proxy environment variables specified for the container in any other way will override the values passed from the host.

init=false

Run an init inside the container that forwards signals and reaps processes.

init_path="/usr/libexec/podman/catatonit"

If this option is not set catatonit is searched in the directories listed under the helper_binaries_dir option. It is recommended to just install catatonit there instead of configuring this option here.

Path to the container-init binary, which forwards signals and reaps processes within containers. Note that the container-init binary will only be used when the --init for podman-create and podman-run is set.

interface_name=""

Default way to set interface names inside containers. Defaults to legacy pattern of ethX, where X is an integer, when left undefined. Options are:

device Uses the network_interface name from the network config as interface name. Falls back to the ethX pattern if the network_interface is not set.

ipcns="shareable"

Default way to create a IPC namespace for the container. Options are:

host Share host IPC Namespace with the container.

none Create shareable IPC Namespace for the container without a private /dev/shm.

private Create private IPC Namespace for the container, other containers are not allowed to share it.

shareable Create shareable IPC Namespace for the container.

keyring=true

Indicates whether the container engines create a kernel keyring for use within the container.

label=true

Indicates whether the container engine uses MAC(SELinux) container separation via labeling. This option is ignored on disabled systems.

label_users=false

label_users indicates whether to enforce confined users in containers on SELinux systems. This option causes containers to maintain the current user and role field of the calling process. By default SELinux containers run with the user system_u, and the role system_r.

log_driver=""

Logging driver for the container. Currently available options are k8s-file, journald, none and passthrough, with json-file aliased to k8s-file for scripting compatibility. The journald driver is used by default if the systemd journal is readable and writable. Otherwise, the k8s-file driver is used.

log_size_max=-1

Maximum size allowed for the container's log file. Negative numbers indicate that no size limit is imposed. If it is positive, it must be >= 8192 to match/exceed conmon's read buffer. The file is truncated and re-opened so the limit is never exceeded.

log_tag=""

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.

mounts=[]

List of mounts. Specified as "type=TYPE,source=<directory-on-host>,destination=<directory-in-container>,<options>"

Example: [ "type=bind,source=/var/lib/foobar,destination=/var/lib/foobar,ro", ]

netns=""

Default way to create a NET namespace for the container. The option is mapped to the --network argument for the podman commands, it accepts the same values as that option. For example it can be set to bridge, host, none, pasta and more, see the podman-create(1) ⟨https://docs.podman.io/en/latest/markdown/podman-create.1.html#network-mode-net⟩ manual for all available options.

no_hosts=false

Do not modify the /etc/hosts file in the container. Podman assumes control over the container's /etc/hosts file by default; refer to the --add-host CLI option for details. To disable this, either set this config to true, or use the functionally identical --no-hosts CLI option.

oom_score_adj=0

Tune the host's OOM preferences for containers (accepts values from -1000 to 1000).

pidns="private"

Default way to create a PID namespace for the container. Options are:

private Create private PID Namespace for the container.

host Share host PID Namespace with the container.

pids_limit=1024

Maximum number of processes allowed in a container. 0 indicates that no limit is imposed.

prepare_volume_on_create=false

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.

privileged=false

Give extended privileges to all containers. A privileged container turns off the security features that isolate the container from the host. Dropped Capabilities, limited devices, read-only mount points, Apparmor/SELinux separation, and Seccomp filters are all disabled. Due to the disabled security features, the privileged field should almost never be set as containers can easily break out of confinment.

Containers running in a user namespace (e.g., rootless containers) cannot have more privileges than the user that launched them.

read_only=true|false

Run all containers with root file system mounted read-only. Set to false by default.

seccomp_profile="/usr/share/containers/seccomp.json"

Path to the seccomp.json profile which is used as the default seccomp profile for the runtime.

shm_size="65536k"

Size of /dev/shm. The format is <number><unit>. number must be greater than 0. Unit is optional and can be: b (bytes), k (kilobytes), m(megabytes), or g (gigabytes). If you omit the unit, the system uses bytes. If you omit the size entirely, the system uses 65536k.

tz=""

Set timezone in container. Takes IANA timezones as well as local, which sets the timezone in the container to match the host machine. If not set, then containers will run with the time zone specified in the image.

Examples:

tz="local"

tz="America/New_York"

umask="0022"

Sets umask inside the container.

userns="host"

Default way to create a USER namespace for the container. Options are:

private Create private USER Namespace for the container.

host Share host USER Namespace with the container.

utsns="private"

Default way to create a UTS namespace for the container. Options are:

private Create private UTS Namespace for the container.

host Share host UTS Namespace with the container.

volumes=[]

List of volumes. Specified as "directory-on-host:directory-in-container:options".

Example: "/db:/var/lib/db:ro".

## NETWORK TABLE
The network table contains settings pertaining to the management of CNI plugins.

network_backend=""

Network backend determines what network driver will be used to set up and tear down container networks. Valid values are "cni" and "netavark". The default value is empty which means that it will automatically choose CNI or netavark. If there are already containers/images or CNI networks preset it will choose CNI.

Before changing this value all containers must be stopped otherwise it is likely that iptables rules and network interfaces might leak on the host. A reboot will fix this.

cni_plugin_dirs=[]

List of paths to directories where CNI plugin binaries are located.

The default list is:

```
cni_plugin_dirs = [

  "/usr/local/libexec/cni",

  "/usr/libexec/cni",

  "/usr/local/lib/cni",

  "/usr/lib/cni",

  "/opt/cni/bin",
]
```

netavark_plugin_dirs=[]

List of directories that will be searched for netavark plugins.

The default list is:

```
netavark_plugin_dirs = [

  "/usr/local/libexec/netavark",

  "/usr/libexec/netavark",

  "/usr/local/lib/netavark",

  "/usr/lib/netavark",
]
```

default_network="podman"

The name of the default network as seen in podman network ls. This option only effects the network assignment when the bridge network mode is selected, i.e. --network bridge. It is the default for rootful containers but not as rootless. To change the default network mode use the netns option under the [containers] table.

Note: This should not be changed while you have any containers using this network.

default_subnet="10.88.0.0/16"

The subnet to use for the default network (named above in default_network).

Note: This should not be changed if any containers are currently running on the default network.

default_subnet_pools=[]

DefaultSubnetPools is a list of subnets and size which are used to allocate subnets automatically for podman network create. It will iterate through the list and will pick the first free subnet with the given size. This is only used for ipv4 subnets, ipv6 subnets are always assigned randomly.

The default list is (10.89.0.0-10.255.255.0/24):

```
default_subnet_pools = [

  {"base" = "10.89.0.0/16", "size" = 24},

  {"base" = "10.90.0.0/15", "size" = 24},

  {"base" = "10.92.0.0/14", "size" = 24},

  {"base" = "10.96.0.0/11", "size" = 24},

  {"base" = "10.128.0.0/9", "size" = 24},
]
```

default_rootless_network_cmd="pasta"

Configure which rootless network program to use by default. Valid options are slirp4netns and pasta (default).

network_config_dir="/etc/cni/net.d/"

Path to the directory where network configuration files are located. For the CNI backend the default is /etc/cni/net.d as root and $HOME/.config/cni/net.d as rootless. For the netavark backend "/etc/containers/networks" is used as root and "$graphroot/networks" as rootless.

firewall_driver=""

The firewall driver to be used by netavark. The default is empty which means netavark will pick one accordingly. Current supported drivers are "iptables", "nftables", "none" (no firewall rules will be created) and "firewalld" (firewalld is experimental at the moment and not recommend outside of testing).

dns_bind_port=53

Port to use for dns forwarding daemon with netavark in rootful bridge mode and dns enabled. Using an alternate port might be useful if other dns services should run on the machine.

pasta_options = []

A list of default pasta options that should be used running pasta. It accepts the pasta cli options, see pasta(1) for the full list of options.

## ENGINE TABLE
The engine table contains configuration options used to set up container engines such as Podman and Buildah.

active_service=""

Name of destination for accessing the Podman service. See SERVICE DESTINATION TABLE below.

add_compression=[]

List of compression algorithms. If set makes sure that requested compression variant for each platform is added to the manifest list keeping original instance intact in the same manifest list on every manifest push. Supported values are (gzip, zstd and zstd:chunked). zstd:chunked is incompatible with encrypting images, and will be treated as zstd with a warning in that case.

Note: This is different from compression_format which allows users to select a default compression format for push and manifest push, while add_compression is limited to manifest push and allows users to append new instances to manifest list with specified compression algorithms in add_compression for each platform.

cgroup_manager="systemd"

The cgroup management implementation used for the runtime. Supports cgroupfs and systemd.

compat_api_enforce_docker_hub=true

Enforce using docker.io for completing short names in Podman's compatibility REST API. Note that this will ignore unqualified-search-registries and short-name aliases defined in containers-registries.conf(5).

compose_providers=[]

Specify one or more external providers for the compose command. The first found provider is used for execution. Can be an absolute and relative path or a (file) name.

compose_warning_logs=true

Emit logs on each invocation of the compose command indicating that an external compose provider is being executed.

conmon_env_vars=[]

Environment variables to pass into Conmon.

conmon_path=[]

Paths to search for the conmon container manager binary. If the paths are empty or no valid path was found, then the $PATH environment variable will be used as the fallback.

The default list is:

```
conmon_path=[

    "/usr/libexec/podman/conmon",

    "/usr/local/libexec/podman/conmon",

    "/usr/local/lib/podman/conmon",

    "/usr/bin/conmon",

    "/usr/sbin/conmon",

    "/usr/local/bin/conmon",

    "/usr/local/sbin/conmon",

    "/run/current-system/sw/bin/conmon",
]
```

database_backend=""

The database backend of Podman. Supported values are "" (default), "boltdb" and "sqlite". An empty value means it will check whenever a boltdb already exists and use it when it does, otherwise it will use sqlite as default (e.g. new installs). This allows for backwards compatibility with older versions. Please run podman-system-reset prior to changing the database backend of an existing deployment, to make sure Podman can operate correctly.

detach_keys="ctrl-p,ctrl-q"

Keys sequence used for detaching a container. Specify the keys sequence used to detach a container. Format is a single character [a-Z] or a comma separated sequence of ctrl-<value>, where <value> is one of: a-z, @, ^, [, \, ], ^ or _ Specifying "" disables this feature.

enable_port_reservation=true

Determines whether the engine will reserve ports on the host when they are forwarded to containers. When enabled, when ports are forwarded to containers, they are held open by conmon as long as the container is running, ensuring that they cannot be reused by other programs on the host. However, this can cause significant memory usage if a container has many ports forwarded to it. Disabling this can save memory.

env=[]

Environment variables to be used when running the container engine (e.g., Podman, Buildah). For example "http_proxy=internal.proxy.company.com". Note these environment variables will not be used within the container. Set the env section under [containers] table, if you want to set environment variables for the container.

events_logfile_path=""

Define where event logs will be stored, when events_logger is "file".

events_logfile_max_size="1m"

Sets the maximum size for events_logfile_path. The unit can be b (bytes), k (kilobytes), m (megabytes) or g (gigabytes). The format for the size is <number><unit>, e.g., 1b or 3g. If no unit is included then the size will be in bytes. When the limit is exceeded, the logfile will be rotated and the old one will be deleted. If the maximum size is set to 0, then no limit will be applied, and the logfile will not be rotated.

events_logger="journald"

The default method to use when logging events.

The default method is different based on the platform that Podman is being run upon. To determine the current value, use this command:

podman info --format {{.Host.EventLogger}}

Valid values are: file, journald, and none.

events_container_create_inspect_data=true|false

Creates a more verbose container-create event which includes a JSON payload with detailed information about the container. Set to false by default.

healthcheck_events=true|false

Whenever Podman should log healthcheck events. With many running healthcheck on short interval Podman will spam the event log a lot as it generates a event for each single healthcheck run. Because this event is optional and only useful to external consumers that may want to know when a healthcheck is run or failed allow users to turn it off by setting it to false.

Default is true.

helper_binaries_dir=["/usr/libexec/podman", ...]

A is a list of directories which are used to search for helper binaries. The following binaries are searched in these directories:

- aardvark-dns

- catatonit

- netavark

- pasta

- slirp4netns

Podman machine uses it for these binaries:

- gvproxy

- qemu

- vfkit

The default paths on Linux are:

- /usr/local/libexec/podman

- /usr/local/lib/podman

- /usr/libexec/podman

- /usr/lib/podman

The default paths on macOS are:

- /usr/local/opt/podman/libexec

- /opt/homebrew/bin

- /opt/homebrew/opt/podman/libexec

- /usr/local/bin

- /usr/local/libexec/podman

- /usr/local/lib/podman

- /usr/libexec/podman

- /usr/lib/podman

The default path on Windows is:

•

C:\Program Files\RedHat\Podman

hooks_dir=["/etc/containers/oci/hooks.d", ...]

Path to the OCI hooks directories for automatically executed hooks.

cdi_spec_dirs=["/etc/cdi", "/var/run/cdi", ...]

Directories to scan for CDI Spec files.

image_default_format="oci"|"v2s2"|"v2s1"

Manifest Type (oci, v2s2, or v2s1) to use when pulling, pushing, building container images. By default images pulled and pushed match the format of the source image. Building/committing defaults to OCI. Note: image_build_format is deprecated.

image_default_transport="docker://"

Default transport method for pulling and pushing images.

image_parallel_copies=0

Maximum number of image layers to be copied (pulled/pushed) simultaneously. Not setting this field will fall back to containers/image defaults. (6)

image_volume_mode="bind"

Tells container engines how to handle the built-in image volumes.

- bind: An anonymous named volume will be created and mounted into the container.

- tmpfs: The volume is mounted onto the container as a tmpfs, which allows the users to create content that disappears when the container is stopped.

- ignore: All volumes are just ignored and no action is taken.

infra_command="/pause"

Infra (pause) container image command for pod infra containers. When running a pod, we start a /pause process in a container to hold open the namespaces associated with the pod. This container does nothing other than sleep, reserving the pod's resources for the lifetime of the pod.

infra_image=""

Infra (pause) container image for pod infra containers. When running a pod, we start a pause process in a container to hold open the namespaces associated with the pod. This container does nothing other than sleep, reserving the pod's resources for the lifetime of the pod. By default container engines run a built-in container using the pause executable. If you want override specify an image to pull.

kube_generate_type="pod"

Default Kubernetes kind/specification of the kubernetes yaml generated with the podman kube generate command. The possible options are pod and deployment.

lock_type="shm"

Specify the locking mechanism to use; valid values are "shm" and "file". Change the default only if you are sure of what you are doing, in general "file" is useful only on platforms where cgo is not available for using the faster "shm" lock type. You may need to run "podman system renumber" after you change the lock type.

multi_image_archive=false

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.

namespace=""

Default engine namespace. If the engine is joined to a namespace, it will see only containers and pods that were created in the same namespace, and will create new containers and pods in that namespace. The default namespace is "", which corresponds to no namespace. When no namespace is set, all containers and pods are visible.

network_cmd_path=""

Path to the slirp4netns binary.

network_cmd_options=[]

Default options to pass to the slirp4netns binary.

Valid options values are:

- allow_host_loopback=true|false: Allow the slirp4netns to reach the host loopback IP (10.0.2.2). Default is false.

- mtu=MTU: Specify the MTU to use for this network. (Default is 65520).

- cidr=CIDR: Specify ip range to use for this network. (Default is 10.0.2.0/24).

- enable_ipv6=true|false: Enable IPv6. Default is true. (Required for outbound_addr6).

- outbound_addr=INTERFACE: Specify the outbound interface slirp should bind to (ipv4 traffic only).

- outbound_addr=IPv4: Specify the outbound ipv4 address slirp should bind to.

- outbound_addr6=INTERFACE: Specify the outbound interface slirp should bind to (ipv6 traffic only).

- outbound_addr6=IPv6: Specify the outbound ipv6 address slirp should bind to.

- port_handler=rootlesskit: Use rootlesskit for port forwarding. Default. 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.

- 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.

no_pivot_root=false

Whether to use chroot instead of pivot_root in the runtime.

num_locks=2048

Number of locks available for containers, pods, and volumes. Each created container, pod, or volume consumes one lock. Locks are recycled and can be reused after the associated container, pod, or volume is removed. The default number available is 2048. If this is changed, a lock renumbering must be performed, using the podman system renumber command.

pod_exit_policy="continue"

Set the exit policy of the pod when the last container exits. Supported policies are:

Exit Policy

Description

continue

The pod continues running when the last container exits. Used by default.

stop

The pod is stopped when the last container exits. Used in play kube.

pull_policy="always"|"missing"|"never"

Pull image before running or creating a container. The default is missing.

- 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.

- 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.

- never: do not pull the image from the registry, use only the local version. Raise an error if the image is not present locally.

remote = false

Indicates whether the application should be running in remote mode. This flag modifies the --remote option on container engines. Setting the flag to true will default podman --remote=true for access to the remote Podman service.

retry = 3

Number of times to retry pulling/pushing images in case of failure.

retry_delay = ""

Delay between retries in case pulling/pushing image fails. If set, container engines will retry at the set interval, otherwise they delay 2 seconds and then exponentially back off.

runtime=""

Default OCI specific runtime in runtimes that will be used by default. Must refer to a member of the runtimes table. Default runtime will be searched for on the system using the priority: "crun", "runc", "runj", "kata", "runsc", "ocijail"

runtime_supports_json=["crun", "crun-vm", "runc", "kata", "runsc", "youki", "krun"]

The list of the OCI runtimes that support --format=json.

runtime_supports_kvm=["kata", "krun"]

The list of OCI runtimes that support running containers with KVM separation.

runtime_supports_nocgroups=["crun", "crun-vm", "krun"]

The list of OCI runtimes that support running containers without CGroups.

image_copy_tmp_dir="/var/tmp"

Default location for storing temporary container image content. Can be overridden with the TMPDIR environment variable. If you specify "storage", then the location of the container/storage tmp directory will be used. If set then it is the users responsibility to cleanup storage. Configure tmpfiles.d(5) to cleanup storage.

service_timeout=5

Number of seconds to wait without a connection before the podman system service times out and exits

static_dir="/var/lib/containers/storage/libpod"

Directory for persistent libpod files (database, etc). By default this will be configured relative to where containers/storage stores containers.

stop_timeout=10

Number of seconds to wait for container to exit before sending kill signal.

exit_command_delay=300

Number of seconds to wait for the API process for the exec call before sending exit command mimicking the Docker behavior of 5 minutes (in seconds).

tmp_dir="/run/libpod"

The path to a temporary directory to store per-boot container. Must be a tmpfs (wiped after reboot).

volume_path="/var/lib/containers/storage/volumes"

Directory where named volumes will be created in using the default volume driver. By default this will be configured relative to where containers/storage store containers. This convention is followed by the default volume driver, but may not be by other drivers.

chown_copied_files=true

Determines whether file copied into a container will have changed ownership to the primary uid/gid of the container.

compression_format="gzip"

Specifies the compression format to use when pushing an image. Supported values are: gzip, zstd and zstd:chunked. This field is ignored when pushing images to the docker-daemon and docker-archive formats. It is also ignored when the manifest format is set to v2s2. zstd:chunked is incompatible with encrypting images, and will be treated as zstd with a warning in that case.

compression_level="5"

The compression level to use when pushing an image. Valid options depend on the compression format used. For gzip, valid options are 1-9, with a default of 5. For zstd, valid options are 1-20, with a default of 3.

## SERVICE DESTINATION TABLE
The engine.service_destinations table contains configuration options used to set up remote connections to the podman service for the podman API.

[engine.service_destinations.{name}] URI to access the Podman service uri="ssh://user@production.example.com/run/user/1001/podman/podman.sock"

Example URIs:

- rootless local - unix:///run/user/1000/podman/podman.sock

- rootless remote - ssh://user@engineering.lab.company.com/run/user/1000/podman/podman.sock

- rootful local - unix:///run/podman/podman.sock

- rootful remote - ssh://root@10.10.1.136:22/run/podman/podman.sock

identity=" /.ssh/id_rsa

Path to file containing ssh identity key

[engine.volume_plugins]

A table of all the enabled volume plugins on the system. Volume plugins can be used as the backend for Podman named volumes. Individual plugins are specified below, as a map of the plugin name (what the plugin will be called) to its path (filepath of the plugin's unix socket).

[engine.platform_to_oci_runtime]

Allows end users to switch the OCI runtime on the bases of container image's platform string. Following config field contains a map of platform/string = oci_runtime.

## SECRET TABLE
The secret table contains settings for the configuration of the secret subsystem.

driver=file

Name of the secret driver to be used. Currently valid values are:

* file

* pass

[secrets.opts]

The driver specific options object.

## MACHINE TABLE
The machine table contains configurations for podman machine VMs

cpus=1 Number of CPU's a machine is created with.

disk_size=10

The size of the disk in GB created when init-ing a podman-machine VM

image=""

Image used when creating a new VM using podman machine init. Can be specified as a registry with a bootable OCI artifact, download URL, or a local path. Registry target must be in the form of docker://registry/repo/image:version. Container engines translate URIs $OS and $ARCH to the native OS and ARCH. URI " ⟨https://example.com/$OS/$ARCH/foobar.ami"⟩ would become " ⟨https://example.com/linux/amd64/foobar.ami"⟩ on a Linux AMD machine. If unspecified, the default Podman machine image will be used.

memory=2048

Memory in MB a machine is created with.

user=""

Username to use and create on the podman machine OS for rootless container access. The default value is user. On Linux/Mac the default iscore.

volumes=["$HOME:$HOME"]

Host directories to be mounted as volumes into the VM by default. Environment variables like $HOME as well as complete paths are supported for the source and destination. An optional third field :ro can be used to tell the container engines to mount the volume readonly.

On Mac, the default volumes are:

[ "/Users:/Users", "/private:/private", "/var/folders:/var/folders" ]

provider=""

Virtualization provider to be used for running a podman-machine VM. Empty value is interpreted as the default provider for the current host OS.

Platform

Default Virtualization provider

Optional

Linux

"" (qemu)

None

Windows

"" ("wsl": Windows Subsystem for Linux)

"hyperv" (Windows Server Virtualization)

Mac

"" ("applehv": Apple Hypervisor)

"libkrun" (Launch machine via libkrun platform, optimized for sharing GPU with the machine)

rosetta="true"

Rosetta supports running x86_64 Linux binaries on a Podman machine on Apple silicon. The default value is true. Supported on AppleHV(arm64) machines only.

## FARMS TABLE
The farms table contains configuration options used to group up remote connections into farms that will be used when sending out builds to different machines in a farm via podman buildfarm.

default=""

The default farm to use when farming out builds.

[farms.list]

Map of farms created where the key is the farm name and the value is the list of system connections.

## PODMANSH TABLE
The podmansh table contains configuration options used by podmansh.

shell="/bin/sh"

The shell to spawn in the container. The default value is /bin/sh.

container="podmansh"

Name of the container that podmansh joins. The default value is podmansh.

timeout=0

Number of seconds to wait for podmansh logins. This value if favoured over the deprecated field engine.podmansh_timeout if set. The default value is 30.

## FILES
containers.conf

Distributions often provide a /usr/share/containers/containers.conf file to provide a default configuration. Administrators can override fields in this file by creating /etc/containers/containers.conf to specify their own configuration. They may also drop .conf files in /etc/containers/containers.conf.d which will be loaded in alphanumeric order. For user specific configuration it reads \$XDG_CONFIG_HOME/containers/containers.conf and \$XDG_CONFIG_HOME/containers/containers.conf.d/*.conf files. When $XDG_CONFIG_HOME is not set it falls back to using $HOME/.config instead.

Fields specified in a containers.conf file override the default options, as well as options in previously loaded containers.conf files.

storage.conf

The /etc/containers/storage.conf file is the default storage configuration file. Rootless users can override fields in the storage config by creating $HOME/.config/containers/storage.conf.

If the CONTAINERS_STORAGE_CONF path environment variable is set, this path is used for the storage.conf file rather than the default. This is primarily used for testing.

## SEE ALSO
containers-storage.conf(5), containers-policy.json(5), containers-registries.conf(5), tmpfiles.d(5)


corefile

title: corefile(5)

text:
# corefile(5)

## NAME
corefile - configuration file for CoreDNS.

## DESCRIPTION
A corefile specifies the internal servers CoreDNS should run and what plugins each of these should chain. The syntax is as follows:

```
[SCHEME://]ZONE [[SCHEME://]ZONE]...[:PORT] {

    [PLUGIN]...
}
```

The ZONE defines for which name this server should be called, multiple zones are allowed and should be white space separated. You can use a "reverse" syntax to specify a reverse zone (i.e. ip6.arpa and in-addr.arpa), by using an IP address in the CIDR notation.

The optional SCHEME defaults to dns://, but can also be tls:// (DNS over TLS), grpc:// (DNS over gRPC) or https:// (DNS over HTTP/2).

The optional PORT controls on which port the server will bind, this default to 53. If you use a port number here, you can't override it with -dns.port (coredns(1)), also see coredns-bind(7).

Specifying a ZONE and PORT combination multiple times for different servers will lead to an error on startup.

When a query comes in, it is matched again all zones for all servers, the server with the longest match on the query name will receive the query.

PLUGIN defines the plugin(s) we want to load into this server. This is optional as well, but as server with no plugins will just return SERVFAIL for all queries. Each plugin can have a number of properties than can have arguments, see the documentation for each plugin.

Comments are allowed and begin with an unquoted hash # and continue to the end of the line. Comments may be started anywhere on a line.

Environment variables are supported and either the Unix or Windows form may be used: {$ENV_VAR_1} or {%ENV_VAR_2%}.

You can use the import "plugin" (See coredns-import(7)) to include parts of other files.

If CoreDNS can’t find a Corefile to load it loads the following builtin one:

```
. {

    whoami

    log
}
```

## IMPORT
You can use the import "plugin" to include parts of other files, see https://coredns.io/plugins/import ⟨https://coredns.io/plugins/import⟩, and coredns-import(7).

## SNIPPETS
If you want to reuse a snippet you can define one with and then use it with import.

```
(mysnippet) {

    log

    whoami
}
. {

    import mysnippet
}
```

## EXAMPLES
The ZONE is root zone ., the PLUGIN is chaos. The chaos plugin takes an (optional) argument: CoreDNS-001. This text is returned on a CH class query: dig CH TXT version.bind @localhost.

```
. {

   chaos CoreDNS-001
}
```

When defining a new zone, you either create a new server, or add it to an existing one. Here we define one server that handles two zones; that potentially chain different plugins:

```
example.org {

    whoami
}
org {

    whoami
}
```

Is identical to:

```
example.org org {

    whoami
}
```

Reverse zones can be specified as domain names:

```
0.0.10.in-addr.arpa {

    whoami
}
```

or by just using the CIDR notation:

```
10.0.0.0/24 {

    whoami
}
```

This also works on a non octet boundary:

```
10.0.0.0/27 {

    whoami
}
```

## AUTHORS
CoreDNS Authors.

## COPYRIGHT
Apache License 2.0

## SEE ALSO
The manual page for CoreDNS: coredns(1) and more documentation on https://coredns.io ⟨https://coredns.io⟩. Also see the import ⟨https://coredns.io/plugins/import⟩'s documentation and all the manual pages for the plugins.