Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 11. Setting container network modes
The chapter provides information about how to set different network modes.
11.1. Running containers with a static IP Copier lienLien copié sur presse-papiers!
The podman run command with the --ip option sets the container network interface to a particular IP address (for example, 10.88.0.44). To verify that you set the IP address correctly, run the podman inspect command.
Prerequisites
-
The
container-toolsmeta-package is installed.
Procedure
Set the container network interface to the IP address 10.88.0.44:
podman run -d --name=myubi --ip=10.88.0.44 registry.access.redhat.com/ubi9/ubi
# podman run -d --name=myubi --ip=10.88.0.44 registry.access.redhat.com/ubi9/ubi efde5f0a8c723f70dd5cb5dc3d5039df3b962fae65575b08662e0d5b5f9fbe85Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Verification
Check that the IP address is set properly:
podman inspect --format='{{.NetworkSettings.IPAddress}}' myubi# podman inspect --format='{{.NetworkSettings.IPAddress}}' myubi 10.88.0.44Copy to Clipboard Copied! Toggle word wrap Toggle overflow
11.2. Running the DHCP plugin for Netavark using systemd Copier lienLien copié sur presse-papiers!
Prerequisites
-
The
container-toolsmeta-package is installed.
Procedure
Enable the DHCP proxy by using the systemd socket:
systemctl enable --now netavark-dhcp-proxy.socket Created symlink /etc/systemd/system/sockets.target.wants/netavark-dhcp-proxy.socket
/usr/lib/systemd/system/netavark-dhcp-proxy.socket. systemctl enable --now netavark-dhcp-proxy.socket Created symlink /etc/systemd/system/sockets.target.wants/netavark-dhcp-proxy.socket/usr/lib/systemd/system/netavark-dhcp-proxy.socket. Copy to Clipboard Copied! Toggle word wrap Toggle overflow Optional: Display the socket unit file:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Create a macvlan network and specify your host interface with it. Typically, it is your external interface:
podman network create -d macvlan --interface-name <LAN_INTERFACE> mv1
# podman network create -d macvlan --interface-name <LAN_INTERFACE> mv1 mv1Copy to Clipboard Copied! Toggle word wrap Toggle overflow Run the container by using newly created network:
podman run --rm --network mv1 -d --name test alpine top
# podman run --rm --network mv1 -d --name test alpine top 894ae3b6b1081aca2a5d90a9855568eaa533c08a174874be59569d4656f9bc45Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Verification
Confirm the container has an IP on your local subnet:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Inspect the container to verify it uses correct IP addresses:
podman container inspect test --format {{.NetworkSettings.Networks.mv1.IPAddress}}# podman container inspect test --format {{.NetworkSettings.Networks.mv1.IPAddress}} 192.168.188.36Copy to Clipboard Copied! Toggle word wrap Toggle overflow
When attempting to connect to this IP address, ensure the connection is made from a different host. Connections from the same host are not supported when using macvlan networking.
11.3. The macvlan plugin Copier lienLien copié sur presse-papiers!
Most of the container images do not have a DHCP client, the dhcp plugin acts as a proxy DHCP client for the containers to interact with a DHCP server.
The host system does not have network access to the container. To allow network connections from outside the host to the container, the container has to have an IP on the same network as the host. The macvlan plugin enables you to connect a container to the same network as the host.
This procedure only applies to rootfull containers. Rootless containers are not able to use the macvlan and dhcp plugins.
You can create a macvlan network using the podman network create --driver=macvlan command.