Skip to content

Commit

Permalink
networkBackend
Browse files Browse the repository at this point in the history
  • Loading branch information
pwright committed Nov 15, 2024
1 parent f8cc4c8 commit 25cb5a3
Show file tree
Hide file tree
Showing 2 changed files with 37 additions and 21 deletions.
35 changes: 35 additions & 0 deletions cli/networkBackend.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
include::../partials/attributes.adoc[]
// Category: skupper-cli
// Type: procedure
[id='podman-networkbackend']
= Configuring Podman networkBackend for {skupper-name}

By default, Podman v4 and later use Netavark which works with {skupper-name}.
However, if you upgraded from an earlier version of Podman, you might need to configure Podman to use Netavark.

If you are using CNI, for example, if you upgrade from Podman v3, you must also install the `podman-plugins` package.
For example, `dnf install podman-plugins` for RPM based distributions.

NOTE: CNI will be deprecated in the future in preference of Netavark.

.Procedure

. To install `netavark` on rpm based Linux, for example, RHEL8:
+
----
$ sudo dnf install netavark
----

. Configure podman to use `netavark` by making sure the following lines exist in the `/etc/containers/containers.conf` file:
+
----
[network]
network_backend = "netavark"
----

. Confirm that `netavark` is configured as the podman network backend:
+
----
$ podman info --format {{.Host.NetworkBackend}}
----

23 changes: 2 additions & 21 deletions cli/podman.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -68,32 +68,13 @@ See link:{cli-link} for information about using the Skupper CLI to create Podman
* `netavark` is configured as the podman network backend.
+
--
By default, Podman v4 uses Netavark which works with Skupper.

If you are using CNI, for example, if you upgrade from Podman v3, you must also install the `podman-plugins` package.
For example, `dnf install podman-plugins` for RPM based distributions.

NOTE: CNI will be deprecated in the future in preference of Netavark.

To check if `netavark` is configured as the podman network backend:

----
$ podman info | grep networkBackend
----

To install `netavark` on rpm based Linux, eg RHEL8:

----
$ sudo dnf install netavark
----

Configure podman to use `netavark` by making sure the following lines exist in the `/etc/containers/containers.conf` file:

----
[network]
network_backend = "netavark"
$ podman info --format {{.Host.NetworkBackend}}
----

If the output is something other than `netavark`, see link:networkBackend.adoc[Configuring Podman networkBackend for {skupper-name}].

--

Expand Down

0 comments on commit 25cb5a3

Please sign in to comment.