I understand using the option --net:container:some_container one can create a new container and give access to an existing containers network namespace. Is there a way to prevent another container from sharing a specific containers’ network name space through SELinux or any other method.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Shared network namespaces using --net=container: | 3 | 16729 | February 7, 2019 | |
| Privately share network port between containers on host and custom bridge network | 0 | 604 | April 26, 2020 | |
| Possible to connect container to another container's network after creation? | 4 | 353 | May 23, 2025 | |
| Having containers on a shared network | 0 | 1493 | March 25, 2016 | |
| Docker restrict container network access | 0 | 587 | September 18, 2020 |