silverblue
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
silverblue [2025/07/21 08:28] me |
silverblue [2025/07/21 08:35] (current) me |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ======Silverblue42====== | ======Silverblue42====== | ||
| + | |||
| + | ====Toolbox (toolbx)==== | ||
| + | |||
| + | From: https:// | ||
| + | |||
| + | The other, more flexible way to create a container based on a system of our choice, is to use --image option and provide the path of the container image we want to use. Some community-maintained images are developed on github and are hosted on the Quay.io register. Just as an example, to create a container based on the Archlinux image, we would run: | ||
| + | |||
| + | $ toolbox create --image quay.io/ | ||
| + | |||
| + | To retrieve the list of the toolbox container we created and the images they are based on, we can use the list sub-command: | ||
| + | |||
| + | $ toolbox list | ||
| + | |||
| + | To enter a container built on one of the supported systems, we can, again, use the corresponding arguments for the --distro and --release options. To enter the container based on RHEL 9.1, for instance, we would run: | ||
| + | |||
| + | $ toolbox enter --distro rhel --release 9.1 | ||
| + | |||
| + | Finally, to enter a container based on a custom image, or more generally reference a container by its name, all we need to do is to pass the name as the last argument. We already built a container based on the “quay.io/ | ||
| + | |||
| + | $ toolbox enter archlinux-toolbox-latest | ||
| + | |||
| + | ===Removing containers and images=== | ||
| + | |||
| + | Once we are done using a container we may want to remove it, perhaphs together with its base image. In order to do that we can use the rm and rmi commands, respectively. Sticking to previous examples, let’s suppose we want to remove the “archlinux-toolbox-latest” container. Here is the command we would run: | ||
| + | |||
| + | $ toolbox rm archlinux-toolbox-latest | ||
| + | |||
| + | The command will fail if the container we are trying to remove is still running. This may happen due to a know issue that makes containers not stopping after exiting. To be able to remove the container anyway we could either stop it directly with “podman”: | ||
| + | |||
| + | $ podman stop archlinux-toolbox-latest | ||
| + | |||
| + | Or use the --force option: | ||
| + | |||
| + | $ podman rm --force archlinux-toolbox-latest | ||
| + | |||
| + | To remove all the containers we created with toolbox at once, all we have to do is to use the --all option: | ||
| + | |||
| + | $ podman rm --force --all | ||
| + | |||
| + | To remove images instead of containers the procedure is the same as the options which can be used. The only thing that changes is the subcommand itself, which in this case is rmi. To remove the image on which the archlinux-toolbox-latest container is based on, we would run: | ||
| + | |||
| + | $ podman rmi quay.io/ | ||
| + | |||
| + | |||
| + | |||
| ====Stopping and Remove Podman Container==== | ====Stopping and Remove Podman Container==== | ||
silverblue.1753086509.txt.gz · Last modified: 2025/07/21 08:28 by me
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
