Timeline for How to bridge a virtual interface inside docker container?

7 events

when toggle format	what		by	license	comment
Jul 7, 2020 at 4:12	comment	added	dirkt		You still have not explained why you want different network interfaces, and why you want to access the host network. What is your use case? Is something on the host running you want to access? Do you want extra filtering on the network interfaces? What do you hope to gain from doing it this way, instead of following the docker model and exposing ports for services to the outside world, and letting services within containers communicate with each other?
Jul 7, 2020 at 0:59	comment	added	jackion		@dirkt Thank you very much for your reply. I have updated my question. Hope it's more clear now. I have tried to define one more network in docker-compose yaml, but it could not specify the network interface name inside docker container.
Jul 7, 2020 at 0:58	history	edited	Attie	CC BY-SA 4.0	added 42 characters in body
Jul 7, 2020 at 0:56	history	edited	jackion	CC BY-SA 4.0	added 512 characters in body
Jul 5, 2020 at 9:36	comment	added	dirkt		There's LOTS of `iptables` stuff inside the containers, so even if you add veth pairs, I'd doubt it would work well. Instead, consider using custom networks in your docker compose file. (You didn't describe your actual use case, see XY questions, but chances your original problem X can be solved through this are high).
Jul 5, 2020 at 4:07	review	First posts
Jul 5, 2020 at 6:26
Jul 5, 2020 at 3:59	history	asked	jackion	CC BY-SA 4.0