Bug 1212282 - podman 4 has optional dependency on netvark
Summary: podman 4 has optional dependency on netvark
Status: RESOLVED INVALID
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Containers (show other bugs)
Version: Current
Hardware: Other openSUSE Tumbleweed
: P5 - None : Enhancement (vote)
Target Milestone: ---
Assignee: Containers Team
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-13 15:37 UTC by Luna D Dragon
Modified: 2023-06-14 05:50 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Luna D Dragon 2023-06-13 15:37:18 UTC 
as per this article https://www.redhat.com/sysadmin/podman-new-network-stack podman seems to be moving towards replacing CNI with netvark due to divering needs and a dependcy on deperciated features in CNI. I have discovered we don't package netvark i believe we should to ensure podman has 100% functionality. podman should also have a hard dep on netvark as networking will not function properly(dns via container name fails unless either netvark or podman-cni-config are installed)
Comment 1 Dan Čermák 2023-06-13 20:43:36 UTC 
Netavark has been packaged in openSUSE Tumbleweed and SLE for a while now.
Comment 2 Danish Prakash 2023-06-14 05:50:07 UTC 
As mentioned above, we've been packaging Netavark and Aardvark-dns for a while in openSUSE and SLE.

The reason we still don't have a hard dependency for both these packages on Podman right now is that we're currently working on a migration to the new network stack, starting with openSUSE, and this shouldn't be a binary flip as that can hamper existing workflows customers might have in place.