Summary

Add support for container network namespace sharing, specifically Podman pods and --network container:<id> / network_mode: container:<id>.

Use case
Modern container-based architectures often rely on multiple containers sharing the same network namespace, following the Kubernetes Pod model. Common patterns include sidecar containers (e.g. reverse proxies, VPN clients, observability agents, service mesh components) that must share the same IP address and port space.

In Podman, this is a first-class feature implemented via pods or via --network container:<id>. Without this capability, VyOS users are limited to one container per network namespace, which makes it difficult or impossible to implement these patterns without additional complexity (extra bridges, manual port forwarding, or external proxies).

Supporting network namespace sharing would allow VyOS to run more realistic and production-aligned container setups directly on the system.

Additional information

• This is a core feature in Podman and a fundamental concept in Kubernetes (Pod semantics).
• Even partial support (basic pod networking) would already unlock many real-world use cases.
• Relevant documentation:
• Podman pods: https://docs.podman.io/en/latest/markdown/podman-pod.1.html
• Podman network modes: https://docs.podman.io/en/latest/markdown/podman-run.1.html