User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/118.0
Build Identifier: 

I had a raspberry pi 4b running opensuse tumbleweed on which I installed podman a while ago (probably before netavark became the default networking system. After updating podman recently to 4.x.x and installing podman-compose-python311, I couldn't get inter-container communication to work due to dns issues. This turned out to be due to podman-compose (the current version) using different flags than what podman 4.x.x in CNI networking mode was compatible with. Setting the networking mode to 'netavark' in the podman configuration resulted in podman becoming unusable because netavark was not installed alongside podman-compose.

Reproducible: Always

Steps to Reproduce:
1. Install podman (4.x.x) and podman-compose (any version)
2. Create a simple docker-compose.yml with two alpine containers
3. try reach 1 container from the other with e.g. curl


Actual Results:  
Failure to resolve dns

Expected Results:  
the curl fails because there is no server responding in the other container

This is almost a duplicate of bug https://bugzilla.opensuse.org/show_bug.cgi?id=1212282, but in my opinion, netavark should be a dependency of podman-compose and not of podman itself.