Prerequisite installation for Podman users

Depending on your networking backend in use in your Podman installation, you might need to install dnsmasq from your Linux® distribution repository.

Procedure

  1. Determine what networking backend is in use in your Podman installation with the following command: 
    podman info | grep networkBackend
  2. Complete the following steps based on your backend.
    • If the backend is netavark, no further prerequisites are required.
    • If the backend is cni, you must check whether the dnsname plugin is already installed. To check the dnsname plugin, inspect the contents of the CNI installation directory, which is typically /usr/libexec/cni/.
      If the dnsname binary is already present and executable, no further actions are needed. You can validate dnsname by running the following command:
      /usr/libexec/cni/dnsname -?
      The output contains a short description and a version of the dnsname plugin.
      If dnsname is not yet installed, perform the following steps:
      1. Ensure that dnsmasq is installed. For example, on a RHEL system, run the following command:
        rpm -qa | grep dnsmasq
        If dnsmasq is already installed, the output is similar to the following:
        dnsmasq-2.79-26.el8.s390x
        An empty output indicates that dnsmasq is not yet installed.
      2. If dnsmasq is not yet installed, install dnsmasq from your Linux distribution repository. For example, on a RHEL system, run the following command:
        sudo yum install dnsmasq
      3. Copy the dnsname package that is suitable for the hardware architecture of your system from the TEMP_WORK_DIR_ZOA/prereqs directory into /usr/libexec/cni/. For example, on zLinux (s390x architecture), run the following command:
        sudo cp TEMP_WORK_DIR_ZOA/prereqs/dnsname.s390x /usr/libexec/cni/dnsname