3 ms·
https://podman.io/getting-started/network https://podman.io/getting-started/network > By definition, all containers in the same Podman pod share the same netwo
by 2OEH8eoCRo0 5y ago
https://podman.io/getting-started/network https://podman.io/getting-started/network
> By definition, all containers in the same Podman pod share the same network namespace. Therefore, the containers will share the IP Address, MAC Addresses and port mappings. You can always communicate between containers in the same pod, using localhost.
I'm a noob here but why wouldn't you use IPC?
https://docs.podman.io/en/latest/markdown/podman-run.1.html#sharing-ipc-between-containers https://docs.podman.io/en/latest/markdown/podman-run.1.html#...
- miketheman 5y agoFor one, I'm not using `podman`. I'm using Amazon Elastic Container Service (Amazon ECS) on top of the Fargate compute layer, so I don't have to manage much beyond my application.
- 2OEH8eoCRo0 5y agoAh gotcha. I understand some of those words.
- kodah 5y agoNetwork and IPC namespacing are just two different ways of communicating using namespaces. I can't imagine that the overhead of either is significant. I can see, from a design perspective, that network namespacing is likely more scalable. Network addresses can be local or WAN while unix sockets would tie you to a single node. That implies a very different and slightly more rigid scaling strategy with IPC based communication.