Gonna repeat what I wrote in the long thread regarding wiclas issue: " Another measure we should take here is a clearly communicated decision on the access model for containers. Right now the server image supports arbitrary UIDs, but there is a lot of evidence that suggests it is supposed to be run with the puppet UID instead. This is confusing and will create more problems down the road. One example is evident in the openvoxdb containers, after the unionization effort there the image declares the OpenShift convention by using the root GID in the USER directive, but it never actually changed the group of relevant files. Additionally then, there is a PR that recommends users to chown volumes to the new UID AND GID 64604 container-openvoxdb#95 but the executing users GID is 0, not 64604. "