News for hackers. Stuff that matters.

A comment on What Has Docker Become?. Parent comment

Re:What Has Docker Become? by justsomehnguy on Friday January 23, 2026 @05:58PM (#46739153)
'Bridge' was and still is an established network term for joining two broadcast domains into one. Why the hell you decided to name your NAT'ed network layer a 'bridge'?
[ Parent | on HN ]
Re:What Has Docker Become? by shykes on Friday January 23, 2026 @06:25PM (#46739354)
As far as I know, Docker uses the term "bridge" in the standard way, to designate the use of Linux bridge interfaces (basically virtual ethernet switches) to interconnect containers. Containers connect to each other via a layer 2 bridge, not NAT.
[ Parent | on HN ]
Re:What Has Docker Become? by justsomehnguy on Saturday January 24, 2026 @07:38AM (#46743066)
It has as much sense as calling all the car roads in the world 'bridges'. They are interconnecting some areas via a physical connection, not some 5th dimension magik, after all.

It's even more egregious with 'ipvlan' and 'macvlan' drivers:

> ipvlan Connect containers to external VLANs.

Duh, that's a 'routed network' and nobody cares if it's on a separate vlan or not.

> macvlan Containers appear as devices on the host's network.

And this is a bridge!

[ Parent | on HN ]
Re:What Has Docker Become? by Avamander on Friday January 23, 2026 @06:02PM (#46739178)
Which reminds me that BuildKit does not have support for specifying a network which is crazy given how you can configure the daemon to not attach one by-default.
[ Parent | on HN ]