Seraphys Posted August 2 Share Posted August 2 So I'm currently using macvlan with bridging turn off on eth0. When I create a custom docker network it is being listed as a bridge network even though I have bridging turned off. Can someone explain what is going on and what the newly created custom docker network is? Quote Link to comment
JorgeB Posted August 2 Share Posted August 2 It uses macvtap, if you upgrade to 6.12.11 you should be able to use macvaln with bridging enabled without issues. Quote Link to comment
Seraphys Posted August 2 Author Share Posted August 2 (edited) 11 minutes ago, JorgeB said: It uses macvtap, if you upgrade to 6.12.11 you should be able to use macvaln with bridging enabled without issues. So is eth0 macvlan and all created custom docker networks are macvtap or are both macvtap. I only ask this because while eth0 uses static ip addresses the newly created docker networks seem to all use the host ip like when bridge is enabled. Edited August 2 by Seraphys Quote Link to comment
JorgeB Posted August 2 Share Posted August 2 IIRC macvtap is used to replaced the bridging, so that VMs can still use that interface, containers should all use macvlan. Quote Link to comment
bmartino1 Posted August 3 Share Posted August 3 Unraid network setting bridging off is different bridge form docker network bridge. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.