1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
|
% libpod.conf(5)
## NAME
libpod.conf - libpod configuration file
## DESCRIPTION
The libpod.conf file is the default configuration file for all tools using
libpod to manage containers.
## OPTIONS
**image_default_transport**=""
Default transport method for pulling and pushing images
**runtime_path**=""
Paths to search for a valid OCI runtime binary
**conmon_path**=""
Paths to search for the Conmon container manager binary
**conmon_env_vars**=""
Environment variables to pass into Conmon
**cgroup_manager**=""
Specify the CGroup Manager to use; valid values are "systemd" and "cgroupfs"
**init_path**=""
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.
**hooks_dir**=["*path*", ...]
Each `*.json` file in the path configures a hook for Podman containers. For more details on the syntax of the JSON files and the semantics of hook injection, see `oci-hooks(5)`. Podman and libpod currently support both the 1.0.0 and 0.1.0 hook schemas, although the 0.1.0 schema is deprecated.
Paths listed later in the array higher precedence (`oci-hooks(5)` discusses directory precedence).
For the annotation conditions, libpod uses any annotations set in the generated OCI configuration.
For the bind-mount conditions, only mounts explicitly requested by the caller via `--volume` are considered. Bind mounts that libpod inserts by default (e.g. `/dev/shm`) are not considered.
Podman and libpod currently support an additional `precreate` state which is called before the runtime's `create` operation. Unlike the other stages, which receive the container state on their standard input, `precreate` hooks receive the proposed runtime configuration on their standard input. They may alter that configuration as they see fit, and write the altered form to their standard output.
**WARNING**: the `precreate` hook lets you do powerful things, such as adding additional mounts to the runtime configuration. That power also makes it easy to break things. Before reporting libpod errors, try running your container with `precreate` hooks disabled to see if the problem is due to one of your hooks.
**static_dir**=""
Directory for persistent libpod files (database, etc)
By default this will be configured relative to where containers/storage
stores containers
**tmp_dir**=""
Directory for temporary files
Must be a tmpfs (wiped after reboot)
**max_log_size**=""
Maximum size of log files (in bytes)
**no_pivot_root**=""
Whether to use chroot instead of pivot_root in the runtime
**cni_config_dir**=""
Directory containing CNI plugin configuration files
**cni_plugin_dir**=""
Directories where CNI plugin binaries may be located
**pause_image** = ""
Pause container image name for pod pause containers. When running a pod, we
start a `pause` processes in a container to hold open the namespaces associated with the
pod. This container and process, basically sleep/pause for the lifetime of the pod.
**pause_command**=""
Command to run the pause container
**namespace**=""
Default libpod namespace. If libpod 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.
**label**="true|false"
Indicates whether the containers should use label separation.
## FILES
`/usr/share/containers/libpod.conf`, default libpod configuration path
`/etc/containers/libpod.conf`, override libpod configuration path
## HISTORY
Apr 2018, Originally compiled by Nathan Williams <nath.e.will@gmail.com>
|
