Bug 1217501

Summary: Podman container to container networking does not work with multiple networks
Product: [openSUSE] openSUSE Tumbleweed Reporter: Soner Shyim <suse>
Component: ContainersAssignee: Containers Team <containers-bugowner>
Status: RESOLVED WONTFIX QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: dcermak
Version: Current   
Target Milestone: ---   
Hardware: All   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Soner Shyim 2023-11-26 10:42:13 UTC 
User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36
Build Identifier: 

Out of the Box with MicroOS and the preinstalled Podman container to container networking does not work when the containers are in multiple networks.

It can be solved by using: netavark for networking:

transactional-update --continue pkg install -y netavark

and enabling it in the podman config. 

netavark seems to be the default since Podman 4.0, https://www.redhat.com/sysadmin/podman-new-network-stack


Reproducible: Always

Steps to Reproduce:
1. Create 3 containers, put all three into the same network, put two into one
2. Try to ping the containers inside the container
3.Does not work
Actual Results:  
DNS can't be resolved

Expected Results:  
It works out of the box

TLDR: use netavark by default
Comment 1 Dan Čermák 2023-11-28 12:42:24 UTC 
Netavark is the current default in Tumbleweed & MicroOS. Unfortunately we cannot easily migrate existing installations from CNI to Netavark, hence this must be done manually.