Seems to be some confusion about the difference between running a container as root without "privileged" & actually being unprivileged. This runs as root in the container.. calling it unprivileged is only in the context of the container "privileged" flag.
cloudplatform.googleblog.com/2018/04/introd…
cloudplatform.googleblog.com/2018/04/introd…
"privileged" flag set to false != Linux unprivileged user, just so that's clear.
Naming that flag privileged was a mistake. Because the inverse is not true.
Shoulda been called super duper unsafe so the inverse only "kinda unsafe" is true :p
Anyways not trying to throw shade, just trying to make sure everyone knows the difference. Also an important lesson in naming things and the fact the "privileged" flag was a design mistake to begin with because of confusion like this.
whats even worse tho is you are actually _worse_ off running this tool than you were mounting the docker socket, because at least docker uses the default seccomp profile while building and this does not have that enabled...
I drew a picture just so we are clear. 
