Questo contenuto non è disponibile nella lingua selezionata.
Chapter 15. Managing containers by using the RHEL web console
You can use the RHEL web console to manage your containers and pods. With the web console, you can create containers as a non-root or root user.
- As a root user, you can create system containers with extra privileges and options.
As a non-root user, you have two options:
- To only create user containers, you can use the web console in its default mode - Limited access.
- To create both user and system containers, click Administrative access in the top panel of the web console page.
For details about differences between root and rootless containers, see Special considerations for rootless containers.
15.1. Creating a container checkpoint in the web console Copia collegamentoCollegamento copiato negli appunti!
With the web console, you can set a checkpoint on a running container or an individual application and store its state to disk.
Creating a checkpoint is available only for system containers.
Prerequisites
- The container is running.
You have installed the RHEL 10 web console.
For instructions, see Installing and enabling the web console.
The
cockpit-podman
add-on is installed:dnf install cockpit-podman
# dnf install cockpit-podman
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Procedure
- Log in to the RHEL 10 web console.
- Click Podman containers in the main menu.
- In the Containers table, select the container you want to modify and click the overflow icon menu and select Checkpoint.
Optional: In the Checkpoint container form, check the options you need:
- Keep all temporary checkpoint files: keep all temporary log and statistics files created by CRIU during checkpointing. These files are not deleted if checkpointing fails for further debugging.
- Leave running after writing checkpoint to disk: leave the container running after checkpointing instead of stopping it.
- Support preserving established TCP connections
- Click .
Verification
- Click the Podman containers in the main menu. Select the container you checkpointed, click the overflow menu icon and verify that there is a Restore option.
15.2. Restoring a container checkpoint in the web console Copia collegamentoCollegamento copiato negli appunti!
You can use data saved to restore the container after a reboot at the same point in time it was checkpointed.
Creating a checkpoint is available only for system containers.
Prerequisites
- The container was checkpointed.
You have installed the RHEL 10 web console.
For instructions, see Installing and enabling the web console.
The
cockpit-podman
add-on is installed:dnf install cockpit-podman
# dnf install cockpit-podman
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Procedure
- Log in to the RHEL 10 web console.
- Click Podman containers in the main menu.
- In the Containers table, select the container you want to modify and click the overflow menu and select Restore.
Optional: In the Restore container form, check the options you need:
- Keep all temporary checkpoint files: Keep all temporary log and statistics files created by CRIU during checkpointing. These files are not deleted if checkpointing fails for further debugging.
- Restore with established TCP connections
- Ignore IP address if set statically: If the container was started with IP address the restored container also tries to use that IP address and restore fails if that IP address is already in use. This option is applicable if you added port mapping in the Integration tab when you create the container.
- Ignore MAC address if set statically: If the container was started with MAC address the restored container also tries to use that MAC address and restore fails if that MAC address is already in use.
- Click .
Verification
- Click the Podman containers in the main menu. You can see that the restored container in the Containers table is running.
15.3. Creating pods in the web console Copia collegamentoCollegamento copiato negli appunti!
You can create pods in the RHEL web console interface.
Prerequisites
You have installed the RHEL 10 web console.
For instructions, see Installing and enabling the web console.
The
cockpit-podman
add-on is installed:dnf install cockpit-podman
# dnf install cockpit-podman
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Procedure
- Log in to the RHEL 10 web console.
- Click Podman containers in the main menu.
- Click .
Provide desired information in the Create pod form:
- Available only with the administrative access: Select the Owner of the container: System or User.
- In the Name field, enter the name of your container.
Click
to add port mapping between container and host system.- Enter the IP address, Host port, Container port and Protocol.
Click
to add volume.- Enter the host path, Container path. You can check the Writable checkbox to create a writable volume. In the SELinux drop down list, select one of the following options: No Label, Shared or Private.
- Click .
Verification
- Click Podman containers in the main menu. You can see the newly created pod in the Containers table.
15.4. Creating containers in the pod in the web console Copia collegamentoCollegamento copiato negli appunti!
You can create a container in a pod.
Prerequisites
You have installed the RHEL 10 web console.
For instructions, see Installing and enabling the web console.
The
cockpit-podman
add-on is installed:dnf install cockpit-podman
# dnf install cockpit-podman
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Procedure
- Log in to the RHEL 10 web console.
- Click Podman containers in the main menu.
- Click .
- In the Name field, enter the name of your container.
Provide the required information in the Details tab.
- Available only with the administrative access: Select the Owner of the container: System or User.
In the Image drop down list select or search the container image in selected registries.
- Optional: Check the Pull latest image checkbox to pull the latest container image.
The Command field specifies the command. You can change the default command if you need.
- Optional: Check the With terminal checkbox to run your container with a terminal.
- The Memory limit field specifies the memory limit for the container. To change the default memory limit, check the checkbox and specify the limit.
- Available only for system containers: In the CPU shares field, specify the relative amount of CPU time. Default value is 1024. Check the checkbox to modify the default value.
Available only for system containers: In the Restart policy drop down menu, select one of the following options:
- No (default value): No action.
- On Failure: Restarts a container on failure.
- Always: Restarts container when exits or after system boot.
Provide the required information in the Integration tab.
Click
to add port mapping between the container and host system.- Enter the IP address, Host port, Container port and Protocol.
Click
to add volume.- Enter the host path, Container path. You can check the Writable option checkbox to create a writable volume. In the SELinux drop down list, select one of the following options: No Label, Shared, or Private.
Click
to add environment variable.- Enter the Key and Value.
Provide the required information in the Health check tab.
- In the Command fields, enter the healthcheck command.
Specify the healthcheck options:
- Interval (default is 30 seconds)
- Timeout (default is 30 seconds)
- Start period
- Retries (default is 3)
When unhealthy: Select one of the following options:
- No action (default): Take no action.
- Restart: Restart the container.
- Stop: Stop the container.
- Force stop: Force stops the container, it does not wait for the container to exit.
The owner of the container is the same as the owner of the pod.
In the pod, you can inspect containers, change the status of containers, commit containers, or delete containers.
Verification
- Click Podman containers in the main menu. You can see the newly created container in the pod under the Containers table.