14.3. Creating a rootful container with Podman volume by using the podman RHEL system role

Procedure

1. Create a playbook file, for example, ~/playbook.yml, with the following content:

   - name: Configure Podman
     hosts: managed-node-01.example.com
     tasks:
       - name: Start Apache server on port 8080
         ansible.builtin.include_role:
           name: redhat.rhel_system_roles.podman
     vars:
       podman_firewall:
         - port: 8080/tcp
           state: enabled
       podman_kube_specs:
         - state: started
           kube_file_content:
             apiVersion: v1
             kind: Pod
             metadata:
               name: ubi10-httpd
             spec:
               containers:
                 - name: ubi10-httpd
                   image: registry.access.redhat.com/ubi10/httpd-24
                   ports:
                     - containerPort: 8080
                       hostPort: 8080
                   volumeMounts:
                     - mountPath: /var/www/html:Z
                       name: ubi10-html
               volumes:
                 - name: ubi10-html
                   persistentVolumeClaim:
                     claimName: ubi10-html-volume

   The settings specified in the example playbook include the following:

   kube_file_content

   Contains a Kubernetes YAML file defining the first container named db. You can generate the Kubernetes YAML file by using the podman kube generate command.

   • The ubi10-httpd container is based on the registry.access.redhat.com/ubi10/httpd-24 container image.
   • The ubi10-html-volume maps the /var/www/html directory on the host to the container. The Z flag labels the content with a private unshared label, therefore, only the ubi10-httpd container can access the content.
   • The pod mounts the existing persistent volume named ubi10-html-volume with the mount path /var/www/html.

   For details about all variables used in the playbook, see the /usr/share/ansible/roles/rhel-system-roles.podman/README.md file on the control node.

2. Validate the playbook syntax:

   $ ansible-playbook --syntax-check ~/playbook.yml

   Note that this command only validates the syntax and does not protect against a wrong but valid configuration.

3. Run the playbook:

   $ ansible-playbook ~/playbook.yml