Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
include::modules/con_installing-and-configuring-insights-iop.adoc[]

include::modules/proc_configuring-podman-network-backend-for-insights.adoc[leveloffset=+1]

ifdef::installing-satellite-server-connected[]
include::modules/proc_configuring-podman-to-use-an-http-proxy.adoc[leveloffset=+1]

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ When you install {insights-iop} locally, you can generate {Insights} recommendat
Enabling {insights-iop} prevents you from using any {RHCloud} services on hosts registered to {Project}.
* If you install {Project} with external databases, you cannot enable {insights-iop}.
Enabling {insights-iop} prevents you from using external databases.
* Podman must be configured to use the netavark network backend.
====

{insights-iop} follows the standard lifecycle policy for {ProjectName}.
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,81 @@
:_mod-docs-content-type: PROCEDURE

[id="configuring-podman-network-backend-for-{insights-iop-id}"]
= Configuring Podman network backend for {insights-iop}

[role="_abstract"]
{insights-iop} requires the netavark network backend for Podman.
Before enabling {insights-iop}, verify that the Podman backend is configured to use netavark.
The Container Network Interface (CNI) network backend and other network backends are not supported.

.Prerequisites
* Podman is installed.
ifdef::satellite[]
For more information, see {RHELDocsBaseURL}9/html/building_running_and_managing_containers/assembly_starting-with-containers_building-running-and-managing-containers#proc_getting-container-tools_assembly_starting-with-containers[Getting container tools] in _{RHEL}{nbsp}9 Building, running, and managing containers_.
endif::[]
ifndef::satellite[]
For more information, see https://podman.io/docs/installation#installing-on-linux[Installing Podman on Linux].
endif::[]

.Procedure
. Verify your current Podman network backend configuration:
+
[options="nowrap", subs="+quotes,verbatim,attributes"]
----
# podman info | grep networkBackend
Comment thread
maximiliankolb marked this conversation as resolved.
----
+
If the output shows `networkBackend: netavark`, your system is configured correctly.
You can proceed to enable {insights-iop}.

. If the output shows a different network backend, such as `networkBackend: cni`, migrate to netavark:
.. Copy the Podman configuration file if it does not exist:
+
[options="nowrap", subs="+quotes,verbatim,attributes"]
----
# cp /usr/share/containers/containers.conf /etc/containers/
----

.. Edit `/etc/containers/containers.conf` and add or modify the `network_backend` setting in the `[network]` section:
+
[source, ini, options="nowrap", subs="+quotes,verbatim,attributes"]
----
[network]
network_backend="netavark"
----

.. Reset the Podman storage to apply the new backend:
+
[WARNING]
====
This command stops all existing containers and removes all container storage.
Ensure that you back up any important container data before proceeding.
====
+
[options="nowrap", subs="+quotes,verbatim,attributes"]
----
# podman system reset
----

.. Reboot the system:
+
[options="nowrap", subs="+quotes,verbatim,attributes"]
----
# reboot
----

.Verification
* Verify that the network backend is set to netavark:
+
[options="nowrap", subs="+quotes,verbatim,attributes"]
----
# podman info | grep networkBackend
Comment thread
maximiliankolb marked this conversation as resolved.
----
+
The output should show `networkBackend: netavark`.

ifdef::satellite[]
.Additional resources
* https://access.redhat.com/solutions/7055981[How to switch to netavark network backend in Podman in the Red{nbsp}Hat Knowledgebase]
* https://access.redhat.com/solutions/7029361[Alternative workaround for Podman network backend configuration in the Red{nbsp}Hat Knowledgebase]
endif::[]
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,8 @@ ifndef::satellite[]
# {project-package-install} podman
----
endif::[]
* Ensure that Podman on the disconnected {ProjectServer} is configured to use the netavark network backend.
For more information, see xref:configuring-podman-network-backend-for-{insights-iop-id}[].

.Procedure
. On the connected system, log in to the container registry:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -18,13 +18,8 @@ endif::[]
ifndef::satellite[]
* Ensure that the {ProjectServer} has access to the Quay container registry.
endif::[]
* Ensure that Podman is installed.
ifdef::satellite[]
For more information, see {RHELDocsBaseURL}9/html/building_running_and_managing_containers/assembly_starting-with-containers_building-running-and-managing-containers#proc_getting-container-tools_assembly_starting-with-containers[Getting container tools] in _{RHEL}{nbsp}9 Building, running, and managing containers_.
endif::[]
ifndef::satellite[]
For more information, see https://podman.io/docs/installation#installing-on-linux[Installing Podman on Linux].
endif::[]
* Ensure that Podman is installed and configured to use the netavark network backend.
For more information, see xref:configuring-podman-network-backend-for-{insights-iop-id}[].

Comment thread
jafiala marked this conversation as resolved.
.Procedure
ifdef::satellite[]
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,8 @@ ifndef::satellite[]
# {project-package-install} skopeo
----
endif::[]
* Ensure that Podman is configured to use the netavark network backend.
For more information, see xref:configuring-podman-network-backend-for-{insights-iop-id}[].

.Procedure
. Download and mount the {Project} ISO image:
Expand Down
Loading