Bug 1217501 - Podman container to container networking does not work with multiple networks
Summary: Podman container to container networking does not work with multiple networks
Status: RESOLVED WONTFIX
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Containers (show other bugs)
Version: Current
Hardware: All Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Containers Team
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-26 10:42 UTC by Soner Shyim
Modified: 2023-11-28 12:42 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 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.