Closed bschonec closed 4 months ago
I'll take a look at this.
I found this article that explains what's happening. I don't yet have enough OpenShift experience to make any recommendations or changes but I'll continue to investigate a possible fix.
Is Kubernetes close enough to OpenShift that that Kubernetes users would be experiencing the same problem?
hmm don't know if K8S is close to OS. I removed the file and added the vars to the Dockerfile. I hope this will fix this issue.
you can test this with 7.16.0-main or 8.3.0-main container tag. build should finish any minute.
Somewhat related to #60.
When creating an application using the Docker image (not a full build), the pod fails with:
/docker-entrypoint.sh: line 6: /etc/puppetlabs/puppetdb/conf.d/.dockerenv: Permission denied
Steps to reproduce:
Again, I'm novice at Openshift but I believe this may be something related to rootless containers. The /docker-entrypoint.sh runs as a non-root, non-puppetdb user (in my case, UID 1001650000). Since /etc/puppetlabs/puppetdb directory and children are owned by puppetdb:puppetdb, the /docker-entrypoint.sh script fails.
This behavior does not happen with Podman on the command line as the only users that are running processes are root and puppetdb.
This behavior happens on both ghcr.io/voxpupuli/container-puppetdb:8.3.0-latest and ghcr.io/voxpupuli/container-puppetdb:7.16.0-latest images.