I think this is one of many instances where Github's issue system doesn't enable good communication between developers and end users. - You shouldn't have to r

I think this is one of many instances where Github's issue system doesn't enable good communication between developers and end users. - You shouldn't have to read through pages of posts to find potential workarounds. - You shouldn't have to count comments to guess if there are a lot of people affected by an issue. - You shouldn't have to read comments, then wonder which posts were an official developer response or a comment from another end user. - There should be some way to communicate easily that "this issue has our attention, but dealing with it is de-prioritized because ..." In this instance, you can see it's a security issue and it will be tough to convince Docker to change it, but at this point it's two years later and people are still griping about it, so maybe it's time to put some attention on it. There are a few suggestions for seemingly reasonable updates, but nobody is championing any of them, presumably because there's no indication other than comment activity that Docker will consider any updates on this issue whatsoever. I'm not sure myself what the right thing to do from Docker's perspective would be, but this is clearly one of those issues that has worn through the attention span of the development team. Someone either needs to stand up and say "we're not changing anything here" or "we're looking for a solution" - no bug report should be open that long.