Comment 3 for bug 1996221

I think we should be looking deeper into this. I can't see a particular reason why `jujud` needs to run as root in the context of a Kubernetes deployment.

In this particular case, just adding a `juju` user to the container as part of the Dockerfile, pre-creating the `/var/lib/juju` directory and ensuring it's owned by the right user would probably allow jujud to run as a non-privileged user, no?

I think things are different on machines, but I can't see a particularly compelling reason to require root on Kubernetes?