Score:0

Configure network namespace of rootless containers

uz flag
TRH

Let's say I created a new custom network namespace with admin rights:

$ ip netns add container
$ ip link add wg0 type wireguard
$ ip link set wg0 netns container
$ ip -n container addr add 192.168.4.33/32 dev wg0
$ ip netns exec container wg setconf wg0 /etc/wireguard/wg0.conf
$ ip -n container link set wg0 up
$ ip -n container route add default dev wg0

From the perspective of an unprivileged user (e.g. rootless docker or podman) - how could I configure/create a container (or container network) so that said container(s) will 'use' the custom network namespace?

If thats not possible, could I - as admin - add/configure simplifications to allow those intends?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.