feat: Add pod_network setting for pod network inheritance #1354
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using pods with external networks (such as macvlan for routable IPs), containers need to inherit the pod's network namespace rather than having their own network configuration. Previously, podman-compose always added --network=_default to container commands, which overrode podman's automatic network namespace inheritance from the pod.
This change adds a new x-podman.pod_network setting that:
The feature enables use cases like:
Usage in docker-compose.yml:
The container will only inherit from pod when: