Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Enable embedding container in image, then install the image in to VM. Connect to VM, then run "sudo podman run ubi8-minimal:latest cat /etc/redhat-release" failed with the following error:
WARN[0005] Failed to load cached network config: network podman not found in CNI cache, falling back to loading network podman from disk
WARN[0005] 1 error occurred:
* plugin type="tuning" failed (delete): failed to find plugin "tuning" in path [/usr/local/libexec/cni /usr/libexec/cni /usr/local/lib/cni /usr/lib/cni /opt/cni/bin]
Error: plugin type="bridge" failed (add): failed to find plugin "bridge" in path [/usr/local/libexec/cni /usr/libexec/cni /usr/local/lib/cni /usr/lib/cni /opt/cni/bin]
But run "podman run ubi8-minimal:latest cat /etc/redhat-release" without any error.
Get network backend info:
podman info -> networkBackend: netavark
sudo podman info -> networkBackend: cni
In root mode, the podman keeps using cni not netavark.
Do not have this issue if embedding container does not enabled.
Version-Release number of selected component (if applicable):
podman version
Client: Podman Engine
Version: 4.2.0
API Version: 4.2.0
Go Version: go1.18.4
Built: Mon Aug 22 08:37:10 2022
OS/Arch: linux/amd64
How reproducible:
Steps to Reproduce:
1. git clone https://github.com/virt-s1/rhel-edge.git
2. cd rhel-edge
3. ./ostree.sh
Actual results:
run "sudo podman run ubi8-minimal:latest cat /etc/redhat-release" failed
Expected results:
no error found
Additional info:
Comment 1Achilleas Koutsou
2022-09-01 10:42:29 UTC
In podman 4.2.0 the default network is netavark but it falls back to CNI in some cases
From the default config file (/usr/share/containers/containers.conf)
> # The default value is empty which means that it will automatically choose CNI or netavark. If there are
> # already containers/images or CNI networks preset it will choose CNI.
When we embed a container in the image, podman uses CNI, but this requires containernetworking-plugins which we do not install in our images.
We should add containernetworking-plugins whenever we add podman to cover all use cases.
Comment 2Achilleas Koutsou
2022-09-01 10:47:44 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Low: Image Builder security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2022:7950
Description of problem: Enable embedding container in image, then install the image in to VM. Connect to VM, then run "sudo podman run ubi8-minimal:latest cat /etc/redhat-release" failed with the following error: WARN[0005] Failed to load cached network config: network podman not found in CNI cache, falling back to loading network podman from disk WARN[0005] 1 error occurred: * plugin type="tuning" failed (delete): failed to find plugin "tuning" in path [/usr/local/libexec/cni /usr/libexec/cni /usr/local/lib/cni /usr/lib/cni /opt/cni/bin] Error: plugin type="bridge" failed (add): failed to find plugin "bridge" in path [/usr/local/libexec/cni /usr/libexec/cni /usr/local/lib/cni /usr/lib/cni /opt/cni/bin] But run "podman run ubi8-minimal:latest cat /etc/redhat-release" without any error. Get network backend info: podman info -> networkBackend: netavark sudo podman info -> networkBackend: cni In root mode, the podman keeps using cni not netavark. Do not have this issue if embedding container does not enabled. Version-Release number of selected component (if applicable): podman version Client: Podman Engine Version: 4.2.0 API Version: 4.2.0 Go Version: go1.18.4 Built: Mon Aug 22 08:37:10 2022 OS/Arch: linux/amd64 How reproducible: Steps to Reproduce: 1. git clone https://github.com/virt-s1/rhel-edge.git 2. cd rhel-edge 3. ./ostree.sh Actual results: run "sudo podman run ubi8-minimal:latest cat /etc/redhat-release" failed Expected results: no error found Additional info: