Setting aside the (rather scary) issue of crafted external packets being bridged into the internal docker subnet - the “0.0.0.0” fw-bypassing default for publis

Setting aside the (rather scary) issue of crafted external packets being bridged into the internal docker subnet - the “0.0.0.0” fw-bypassing default for published ports in a developer-oriented tool is a complete nightmare for infosec teams at software engineering companies. I’ve seen of thousands of employee hours wasted chasing that down.