17.5. Running Buildah in a container

Procedure

1. Log in to the registry.redhat.io registry:

   $ podman login registry.redhat.io
   Username: myuser@mycompany.com
   Password: <password>
   Login Succeeded!

2. Pull and run the registry.redhat.io/rhel10/buildah image:

   # podman run --rm --device /dev/fuse -it \
     registry.redhat.io/rhel10/buildah /bin/bash

   • The --rm option removes the registry.redhat.io/rhel10/buildah image after the container exits.
   • The --device option adds a host device to the container.
   • The sys_chroot - capability to change to a different root directory. It is not included in the default capabilities of a container.

3. Create a new container using a registry.access.redhat.com/ubi10/ image:

   # buildah from registry.access.redhat.com/ubi10/
   ...
   ubi10/-working-container

4. Run the ls / command inside the ubi10/-working-container container:

   # buildah run --isolation=chroot ubi10/-working-container ls /
   bin  boot  dev  etc  home  lib  lib64  lost+found  media  mnt  opt  proc  root  run  sbin  srv

5. Optional: List all images in a local storage:

   # buildah images
   REPOSITORY                        TAG      IMAGE ID       CREATED       SIZE
   registry.access.redhat.com/ubi10/   latest   ecbc6f53bba0   5 weeks ago   211 MB

6. Optional: List the working containers and their base images:

   # buildah containers
   CONTAINER ID  BUILDER  IMAGE ID     IMAGE NAME                       CONTAINER NAME
   0aaba7192762     *     ecbc6f53bba0 registry.access.redhat.com/ub... ubi10/-working-container

7. Optional: Push the registry.access.redhat.com/ubi10/ image to the a local registry located on registry.example.com:

   # buildah push ecbc6f53bba0 registry.example.com:5000/ubi10/ubi