Subject: Grouper Users - Open Discussion List
- From: Darren Boss <>
- Subject: Re: [grouper-users] Openshift Deployment
- Date: Wed, 22 Apr 2020 09:42:22 -0400
Even if not running under Openshift and just upstream Kubernetes, please retool the Docker images to not run as root (this applies to the other TAP images as well).
Containers are not vms and unless you are running with uid translation/mapping in place, the grouper process would be running at root on the system as well. From what I've read, running within a user namespace and remapping uids can impart a performance penalty.
On Wed, Apr 22, 2020 at 3:22 AM Oliver Trieu <> wrote:
Dear Grouper Team,
I think its great that Grouper is now running on containers.
This is definitely a step in the right direction.
I was wondering if you could prepare your Container Image to run on the
The issue here is that the current Image wants to run as the root user.
It would be great if you could run it as an unpriviledged user.
Is it possible to obtaiin the Dockerfiles you used to create the images?
- [grouper-users] Openshift Deployment, Oliver Trieu, 04/22/2020
- Re: [grouper-users] Openshift Deployment, Darren Boss, 04/22/2020
Archive powered by MHonArc 2.6.19.