Configuring container networking with Podman

The network layer does not have DNS resolve available between containers. This topic provides information on the network configurations needed to resolve network or DNS issues in Podman environments.

Before you begin

Ensure that the podman-compose version is 1.0.4 or higher. To update podman-compose, run the following command.
curl -o /usr/local/bin/podman-compose https://raw.githubusercontent.com/containers/podman-compose/devel/podman_compose.py
chmod +x /usr/local/bin/podman-compose

About this task

If you are using Red Hat® Enterprise Linux® and Podman, you must configure the RHEL nodes to ensure the connections are successful.
Note: All commands provided require running as ROOT or SUDO access. If not running as root user, preface the commands in steps 1 and 2 with sudo.

Procedure

  1. Run the command to install Netavark.
    dnf install netavark
  2. Place the containers.conf file in edit mode.
    vi /etc/containers/containers.conf
  3. After installation, migrate all your containers to use Netavark by running this command:
    network_backend = "netavark"
  4. Do a force reset.
    podman system reset --force
  5. Bind Sametime to port 443.
    sysctl net.ipv4.ip_unprivileged_port_start=443