We usually can't see the same problems happening in front of our noses. Why shouldn't we discuss why docker images run as root by default then?
This issue, along with its related issues with permissions on persistent storage, is one of the major reasons I'm hoping to move away from Docker as soon as possible.
Re root permisions I guess if you're running a typical network daemon (Apache, say), then requiring Docker to run as root is no worse than running the service on the host; root would be a requisite anyway for the daemon to open privileged ports/gain logging permissions etc. before dropping to "nobody" or what have you.
If you are not using docker, you can manually add the specific privilege to open low-numbered ports without running the program in question as root.