Ce contenu n'est pas disponible dans la langue sélectionnée.

Chapter 17. 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.

17.1. Creating a container checkpoint in the web console

To save the exact current state of a running container, create a container checkpoint in the Red Hat Enterprise Linux web console. You can safely pause operations, migrate workloads to another host, or restore the container later without losing your progress by setting this checkpoint.

Prerequisites

Procedure

  1. Log in to the RHEL 10 web console.
  2. Click Podman containers in the main menu.
  3. In the Containers table, select the container you want to modify and click the overflow icon menu and select Checkpoint.
  4. 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 Checkpoint/Restore In Userspace (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
  5. Click Checkpoint.

    Note

    Creating a checkpoint is available only for system containers.

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.

17.2. Restoring a container checkpoint in the web console

To resume operations from a previously saved state, you can restore a container checkpoint in the Red Hat Enterprise Linux web console. You can also quickly recover workloads after a host reboot or bring migrated containers back online without losing data.

Prerequisites

Procedure

  1. Log in to the RHEL 10 web console.
  2. Click Podman containers in the main menu.
  3. In the Containers table, select the container you want to modify and click the overflow menu and select Restore.
  4. 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 user started the container with an IP address, the restored container also tries to use that IP address. The restore operation 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 a MAC address, the restored container also tries to use that MAC address. The restoration fails if that MAC address is already in use.
  5. Click Restore.

    Note

    Creating a checkpoint is available only for system containers.

Verification

  • Click the Podman containers in the main menu. You can see that the restored container in the Containers table is running.

17.3. Creating pods in the web console

To group and manage related containers as a single unit, you can create container pods in the Red Hat Enterprise Linux web console interface. .Prerequisites

Procedure

  1. Log in to the RHEL 10 web console.
  2. Click Podman containers in the main menu.
  3. Click Create pod.
  4. Provide required 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 Add port mapping to add port mapping between container and host system.

      • Enter the IP address, Host port, Container port and Protocol.
    • Click Add volume 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.
  5. Click Create.

Verification

  • Click Podman containers in the main menu. You can see the newly created pod in the Containers table.

17.4. Creating containers in the pod in the web console

You can create a container in a pod by using the RHEL web console GUI.

Prerequisites

Procedure

  1. Log in to the RHEL 10 web console.
  2. Click Podman containers in the main menu.
  3. Click Create container in pod.
  4. In the Name field, enter the name of your container.
  5. 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.
  6. Provide the required information in the Integration tab.

    • Click Add port mapping to add port mapping between the container and host system.

      • Enter the IP address, Host port, Container port and Protocol.
    • Click Add volume 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 Add variable to add environment variable.

      • Enter the Key and Value.
  7. Provide the required information in the Health check tab.

    • In the Command fields, enter the health check command.
    • Specify the health check 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.

          Note

          The owner of the container and pod are the same. 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.
Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de la documentation Red Hat

Legal Notice

Theme

© 2026 Red Hat
Retour au début