Permissive forwarding rule leads to unintentional exposure of containers (2021)
Ouch. This is the security posture that half a billion dollars, hundreds of engineers, multiple layers of abstraction to a firewall ruleset and <i>each Stream-aligned team with an embedded Product Manager and UX Designer</i>[0] buys you. I too contributed security fixes to Docker in the early stages but soon gave up.<p>Docker is a fascinating study in hype. Containers already existed, docker wrapped them very badly, raised half a billion dollars, popularized their wrapper (I understand kubernetes is the fad-wrapper now) and then failed to obtain a revenue stream. I didn&#x27;t see them return much to open source, though perhaps they contributed to projects I don&#x27;t see.<p>Honestly, the whole thing has a plotline like a Shakespearean tragedy. Someone could do a film, starting with interviews with the guys who wrote the original Linux containers and namespacing kernel code at IBM, the maintainers of jails in FreeBSD, and an early hacker at VMWare.<p>[0] <a href="https:&#x2F;&#x2F;www.docker.com&#x2F;blog&#x2F;building-stronger-happier-engineering-teams-with-team-topologies&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.docker.com&#x2F;blog&#x2F;building-stronger-happier-engine...</a>