1toolbox-init-container(1)()                        toolbox-init-container(1)()
2
3
4

NAME

6       toolbox-init-container - Initialize a running container
7
8

SYNOPSIS

10       toolbox init-container --home HOME
11                              --home-link
12                              --media-link
13                              --mnt-link
14                              --monitor-host
15                              --shell SHELL
16                              --uid UID
17                              --user USER
18
19

DESCRIPTION

21       Initializes  a  newly created container that's running. It is primarily
22       meant to be used as the entry point for  all  toolbox  containers,  and
23       must  be  run  inside the container that's to be initialized. It is not
24       expected to be directly invoked by humans, and cannot be  used  on  the
25       host.
26
27
28       A  key  feature of toolbox containers is their entry point, the toolbox
29       init-container command.
30
31
32       OCI containers are inherently immutable. Configuration  options  passed
33       through  podman  create  are  baked into the definition of the OCI con‐
34       tainer, and can't  be  changed  later.  This  means  that  changes  and
35       improvements  made  in  newer  versions  of Toolbox can't be applied to
36       pre-existing toolbox containers created by older versions  of  Toolbox.
37       This  is avoided by using the entry point to configure the container at
38       runtime.
39
40
41       The entry point of a toolbox container customizes the container to  fit
42       the current user by ensuring that it has a user that matches the one on
43       the host.  It ensures that configuration files, such as /etc/host.conf,
44       /etc/hosts,  /etc/localtime, /etc/resolv.conf and /etc/timezone, inside
45       the container are kept synchronized with the host. The entry point also
46       bind mounts various subsets of the host's filesystem hierarchy to their
47       corresponding locations inside the container to provide seamless  inte‐
48       gration  with  the host. This includes /run/libvirt, /run/systemd/jour‐
49       nal,   /run/udev/data,   /var/lib/libvirt,   /var/lib/systemd/coredump,
50       /var/log/journal and others.
51
52
53       On  some  host operating systems, important paths like /home, /media or
54       /mnt are symbolic links to other locations.  The  entry  point  ensures
55       that paths inside the container match those on the host, to avoid need‐
56       less confusion.
57
58

OPTIONS

60       The following options are understood:
61
62
63       --home HOME
64
65
66       Create a user inside the toolbox container  whose  login  directory  is
67       HOME.
68
69
70       --home-link
71
72
73       Make /home a symbolic link to /var/home.
74
75
76       --media-link
77
78
79       Make /media a symbolic link to /run/media.
80
81
82       --mnt-link
83
84
85       Make /mnt a symbolic link to /var/mnt.
86
87
88       --monitor-host
89
90
91       Ensure  that  certain  configuration files inside the toolbox container
92       are kept synchronized with their counterparts on the  host.  Currently,
93       these files are /etc/hosts and /etc/resolv.conf.
94
95
96       --shell SHELL
97
98
99       Create a user inside the toolbox container whose login shell is SHELL.
100
101
102       --uid UID
103
104
105       Create  a  user inside the toolbox container whose numerical user ID is
106       UID.
107
108
109       --user USER
110
111
112       Create a user inside the toolbox container whose login name is LOGIN.
113
114

SEE ALSO

116       podman(1), podman-create(1), podman-start(1)
117
118
119
120                                                   toolbox-init-container(1)()
Impressum