wbrawner/toolbox
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

doc/toolbox-enter: Mention the underlying podman commands

Browse source 
It's useful to know things like a running toolbox container has to be
stopped before removal or 'rm --force' needs to be used, etc.. This is
implicitly tied to the fact that entering a toolbox container is
equivalent to a 'podman start' followed by a 'podman exec'.
This commit is contained in:
Debarshi Ray 2019-03-05 14:11:12 +01:00
parent 517c77a0d6
commit c9a061c7b9
1 changed files with 7 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
doc/toolbox-enter.1.md
View file

@ -11,10 +11,12 @@ toolbox\-enter - Enter an existing toolbox container for interactive use
Spawns an interactive shell inside an existing toolbox container. The
container should have been created using the `toolbox create` command.
A toolbox container is an OCI container. On Fedora the toolbox containers are
tagged with the version of the OS that corresponds to the content inside them.
Their names are prefixed with the name of the base image and suffixed with the
current user name.
A toolbox container is an OCI container. Therefore, `toolbox enter` is
analogous to a `podman start` followed by a `podman exec`.
On Fedora the toolbox containers are tagged with the version of the OS that
corresponds to the content inside them. Their names are prefixed with the name
of the base image and suffixed with the current user name.
## OPTIONS ##
@ -53,4 +55,4 @@ $ toolbox enter --container foo
## SEE ALSO
`buildah(1)`, `podman(1)`
`buildah(1)`, `podman(1)`, `podman-exec(1)`, `podman-start(1)`