1toolbox-enter(1)() toolbox-enter(1)()
2
3
4
6 toolbox-enter - Enter a toolbox container for interactive use
7
8
10 toolbox enter [--container NAME | -c NAME]
11 [--release RELEASE | -r RELEASE]
12
13
15 Spawns an interactive shell inside a toolbox container. The container
16 should have been created using the toolbox create command. If there
17 aren't any containers, toolbox enter will offer to create one for you.
18 When invoked with the default parameters, and if there's only one con‐
19 tainer available, it will fall back to it, even if it doesn't match the
20 default name.
21
22
23 A toolbox container is an OCI container. Therefore, toolbox enter is
24 analogous to a podman start followed by a podman exec.
25
26
27 On Fedora the toolbox containers are tagged with the version of the OS
28 that corresponds to the content inside them. Their names are prefixed
29 with the name of the base image and suffixed with the current user
30 name.
31
32
34 The following options are understood:
35
36
37 --container NAME, -c NAME
38
39
40 Enter a toolbox container with the given NAME. This is useful when
41 there are multiple toolbox containers created from the same base image,
42 or entirely customized containers created from custom-built base
43 images.
44
45
46 --release RELEASE, -r RELEASE
47
48
49 Enter a toolbox container for a different operating system RELEASE than
50 the host.
51
52
54 Enter a toolbox container using the default image matching the host OS
55 $ toolbox enter
56
57
58
59 Enter a toolbox container using the default image for Fedora 30
60 $ toolbox enter --release f30
61
62
63
64 Enter a custom toolbox container using a custom image
65 $ toolbox enter --container foo
66
67
68
70 buildah(1), podman(1), podman-exec(1), podman-start(1)
71
72
73
74 toolbox-enter(1)()