Project

General

Profile

Actions

action #124631

closed

Usage of netavark and aardvark in podman networks

Added by jlausuch over 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
2023-02-15
Due date:
% Done:

0%

Estimated time:

Description

As of podman 4, we can make use of a network stack based on Netavark and Aardvark instead of former CNI:
https://www.redhat.com/sysadmin/podman-new-network-stack
https://blog.podman.io/2023/04/lease-dynamic-ips-with-netavark/

Danish Prakash has compiled some information about how this new network backend can be tested:
https://confluence.suse.com/display/~danishprakash/Podman+Networking+Features+to+Test

Packages to be installed:

zypper in netavark aardvark-dns

To do so, /etc/containers/containers.conf needs to be changed to:

[Network]
network_backend="netavark"

and it's possible to check which network stack it's using:

podman info --format {{.Host.NetworkBackend}}

(by default it should be cni)

We don't need to implement new tests with this, but do the change and then run podman network tests.

Affected versions:

  • 15-SP3
  • 15-SP4
  • 15-SP5
  • Tumbleweed
  • Leap 15.4
  • Leap 15.3

Acceptance criteria


Related issues 4 (0 open4 closed)

Related to Containers - action #129961: podman_netavark fails in SLE Micro 5.1 with SELinux enabledResolvedph03nix2023-05-28

Actions
Related to Containers - action #129910: New podman_netavark test fails everywhere in aarch64 and s390xResolvedjlausuch2023-05-26

Actions
Related to Containers - action #130141: test fails in podman_netavark on SLEM on AzureResolvedph03nix2023-05-31

Actions
Related to Containers - action #130255: podman_netavark: package does not exist on ppc64leClosedmloviska2023-06-01

Actions
Actions

Also available in: Atom PDF