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 --gid GID
11                              --home HOME
12                              --home-link
13                              --media-link
14                              --mnt-link
15                              --monitor-host
16                              --shell SHELL
17                              --uid UID
18                              --user USER
19
20

DESCRIPTION

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

OPTIONS

64       The following options are understood:
65
66
67       --gid GID
68
69
70       Pass GID as the user's numerical group ID from the host to the  toolbox
71       container.
72
73
74       --home HOME
75
76
77       Create  a  user  inside  the toolbox container whose login directory is
78       HOME. This option is required.
79
80
81       --home-link
82
83
84       Make /home a symbolic link to /var/home.
85
86
87       --media-link
88
89
90       Make /media a symbolic link to /run/media.
91
92
93       --mnt-link
94
95
96       Make /mnt a symbolic link to /var/mnt.
97
98
99       --monitor-host
100
101
102       Ensures that certain configuration files inside the  toolbox  container
103       are  kept  synchronized  with  their counterparts on the host, and bind
104       mounts some paths from the host's file system into the container.
105
106
107       The synchronized files are:
108
109
110/etc/host.conf
111
112/etc/hosts
113
114/etc/localtime
115
116/etc/resolv.conf
117
118/etc/timezone
119
120
121
122       The bind mounted paths are:
123
124
125/etc/machine-id
126
127/run/libvirt
128
129/run/systemd/journal
130
131/run/systemd/resolve
132
133/run/udev/data
134
135/tmp
136
137/var/lib/flatpak
138
139/var/lib/libvirt
140
141/var/lib/systemd/coredump
142
143/var/log/journal
144
145/var/mnt
146
147
148
149       --shell SHELL
150
151
152       Create a user inside the toolbox container whose login shell is  SHELL.
153       This option is required.
154
155
156       --uid UID
157
158
159       Create  a  user inside the toolbox container whose numerical user ID is
160       UID. This option is required.
161
162
163       --user USER
164
165
166       Create a user inside the toolbox container whose login name  is  LOGIN.
167       This option is required.
168
169

SEE ALSO

171       toolbox(1), podman(1), podman-create(1), podman-start(1)
172
173
174
175                                                   toolbox-init-container(1)()
Impressum