Open stonegatebi opened 7 years ago
Chown all files under /biserver-ce will likely double the image size, so I need to avoid that.
Maybe I should not add non-root user in the container. But the problem I'm trying to resolve is to map users in container and host, so that a non-root user on host can view files(usually logs) exposed by the container. Maybe it's not necessary to do this anymore since logs can be captured by logspout and fluentd/syslog/elk.
So we could chown the directories in the && stack of commands (making only that layer). I'll report back how that went. Another possibility is using the sticky bit on the host's bind directory to set default permissions compatible with whomever on your system needs to read logs. I am just now starting to look into how I could ingest logs with an ELK stack.
After studying the docker container produced from Dockerfile, I discovered why the resulting image has problems with not only Marketplace, but also schema publishing. There is a mixture of permissions between root and say the user 'pentaho'. This is easily fixed near the end of the build by 'chown -R $BISERVER_USER.$BISERVER_USER /biserver-ce'