Infra containers receive IP addresses implicitly from unused network #4908
The package cni I use installs a bridge network by default into location
I found this issue during #4907 All details which should relevant here can be found in the referenced issue.
I am not sure whether is this a problem with podman or cni.
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Package info (e.g. output of
Additional environment details (AWS, VirtualBox, physical, etc.):
This does not sound like a bug, then. Pods presently do not support being attached to user-specified networks, and if this was supported, it would have to be done at pod creation time; attaching containers that specify custom networks should not be allowed. Your pods have joined the default network, and are receiving IP addresses from it; this sounds correct. There are separate issues for the ability to have pods join a non-default CNI network.
What is the purpose of attaching a pod to a network from podman's perspective?
Sorry, I may not get everything right as I am kinda new to the concept of pods.
Containers in a pod all share the same network namespace - they use the same network stack and IP. Containers may allow you to specify things like CNI network if they are doing this, but that is a bug - it will be ignored, and the container will join the pod network, which is already configured.