Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-Root user #31

Open
ghost opened this issue Apr 27, 2021 · 1 comment
Open

Non-Root user #31

ghost opened this issue Apr 27, 2021 · 1 comment

Comments

@ghost
Copy link

ghost commented Apr 27, 2021

Are you able to ensure this runs as a non-root user (e.g. 'atlas') so that it can be deployed to services such as Openshift?

Thanks

@cmgrote
Copy link

cmgrote commented May 19, 2021

While the suggestion above would certainly be the ideal solution, just wanted to point out a (less secure) workaround that you could use in the meantime that will at least technically work:

  1. Create a service account specific for Atlas, e.g.
    oc create sa apache-atlas
  2. Grant the anyuid security context constraint (SCC) to this service account, e.g.
    oc adm policy add-scc-to-user anyuid -z apache-atlas
  3. Ensure that your deployment mechanism for the Atlas container uses this service account created in (1), e.g.
    kind: Deployment
    apiVersion: apps/v1
    metadata: ...
    spec:
      template:
        spec:
          # use name of service account created in (1) below
          serviceAccountName: apache-atlas
          containers:
            - name: atlas
              image: sburn/apache-atlas
    ...

The container should then at least be run-able inside OpenShift. (You'll need to confirm for yourself that it's OK running with the anyuid SCC in your specific cluster and situation.)

aefo added a commit to aefo/docker-apache-atlas that referenced this issue Mar 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant