Hmmm... It's as though running root privelege daemons with open sockets could go wrong. Who could have known.<p><a href="https://developers.redhat.com/blog/2020/09/25/rootless-containers-with-podman-the-basics#why_podman_" rel="nofollow">https://developers.redhat.com/blog/2020/09/25/rootless-conta...</a>
Are there really good use cases for dockerd being exposed to the network?<p>I would assume (many/most) users who run docker directly run it without api access on the network (i.e. on a single host).<p>Even those that do want network deployments of docker, probably run it through something like k8s where again kubernetes is handling the networking side, and each dockerd doesn't need to expose a network accessible api).<p>just wondering the use case for this.
> The vulnerability was addressed with the release of Docker Engine v18.09.1, but it was not included in subsequent major versions, causing a regression.<p>Without further information, this sounds like code introduced in a hotfix that wasn't merged back to feature branches.<p>Surely it's not that simple?