Then why does their company still use docker for that? Did they fail to convince anyone else? Did they disagree? Did they not even bother bringing up their frustrations? People love to complain, but rarely try to contribute to actually make things better.

The tool doesn't have to be just better. It needs to be so much better that it's worth: changing defaults / what people use now, changing documentation, verifying it works for all projects, ensuring that nobody has use cases that asdf doesn't address, and actually spending time with the decision maker to present your idea. For a larger company that may mean days of work.

Days?

In the "big 'ol" companies I worked at, something like that takes months! If even possible...

Ironic, it would have been far more helpful to just ask OP "what are the reasons your company still uses Docker?" instead of mindlessly complaining.

Counter argument: your version is fine and may have helped to solve one particular issue in one particular company.

But countless developers in countless companies have each their own set of frustrations where they sense that something could be improved but don't know what to do with the frustration.

Frustrations are a useful symptom but learned helplessness is a terrible thing that can lead to anything from being annoyed to leaving your job to depression.

I would argue that the response was in fact a very valuable lesson.