You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Create a service account specific for Atlas, e.g. oc create sa apache-atlas
Grant the anyuid security context constraint (SCC) to this service account, e.g. oc adm policy add-scc-to-user anyuid -z apache-atlas
Ensure that your deployment mechanism for the Atlas container uses this service account created in (1), e.g.
kind: DeploymentapiVersion: apps/v1metadata: ...spec:
template:
spec:
# use name of service account created in (1) belowserviceAccountName: apache-atlascontainers:
- name: atlasimage: 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
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
The text was updated successfully, but these errors were encountered: