Edit - Super User

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Rev

1

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).
– dirkt
Commented Jul 5, 2020 at 9:36
@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.
– jackion
Commented Jul 7, 2020 at 0:59
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?
– dirkt
Commented Jul 7, 2020 at 4:12

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author