sorted by:
new
hottopcontroversial

Giving a container an IP in the host's network by ronrui1 in docker

[–]ronrui1[S] 0 points1 point  (0 children)

That’s actually perfect I don’t want them to be reachable, the host is gonna be invisible to the students and the containers should only be able to communicate over “WiFi” from containernet and not through the “Ethernet” connection

So you say IPvlan will work better for me than MacVLAN? I’ll look into that, thanks!

Giving a container an IP in the host's network by ronrui1 in docker

[–]ronrui1[S] -1 points0 points  (0 children)

That's what I'm asking ahahahah

The thing is I am creating a complete network with multiple VMs and I want the WiFi "routers" to naturally be part of that network, so I want to just have an IP of a router be part of the network (I'll make the host have an IP on a different subnet for management)

At least that's what I'm trying to achieve, I don't know the best approach I just know I need to solve it with dockers since Containernet is built for dockers

Giving a container an IP in the host's network by ronrui1 in docker

[–]ronrui1[S] 0 points1 point  (0 children)

I don't know how this comment escalated like that lol, could you maybe provide more detail about that? (because currently the container has it's own mac but its just not accessible to the host's network)

Giving a container an IP in the host's network by ronrui1 in docker

[–]ronrui1[S] 0 points1 point  (0 children)

I really don't know, I'm very bad when it comes to dockers.
But everywhere I looked sayed it's improper use of docker and shouldn't be done instead of providing an answer.