Valentin Rothberg 75578aad61 add container-init support ... Add support for executing an init binary as PID 1 in a container to forward signals and reap processes. When the `--init` flag is set for podman-create or podman-run, the init binary is bind-mounted to `/dev/init` in the container and "/dev/init --" is prepended to the container's command. The default base path of the container-init binary is `/usr/libexec/podman` while the default binary is catatonit [1]. This default can be changed permanently via the `init_path` field in the `libpod.conf` configuration file (which is recommended for packaging) or temporarily via the `--init-path` flag of podman-create and podman-run. [1] https://github.com/openSUSE/catatonit Fixes: #1670 Signed-off-by: Valentin Rothberg <rothberg@redhat.com>		2019-01-04 11:42:03 +01:00
..
config_linux.go	Fix handling of symbolic links	2018-12-28 13:10:15 -05:00
config_unsupported.go	spec: Make addPrivilegedDevices and createBlockIO per-platform	2018-07-06 00:48:40 +00:00
createconfig.go	add container-init support	2019-01-04 11:42:03 +01:00
parse.go	Invalid index for array	2018-12-21 09:25:25 -05:00
ports.go	Spell check strings and comments	2018-05-25 08:45:15 +00:00
spec.go	Fixes to handle /dev/shm correctly.	2018-12-24 09:03:53 -05:00
spec_test.go	Swap default mount propagation from private to rprivate	2018-09-13 21:35:44 +00:00