hello
i solved it giving the oc user cluster-admin role .. i do not really like this
way but it works :/
Best regards
> El 22 mar 2016, a las 12:03, Julio Saura escribió:
>
> i forgot saying that my pod is running process under user jboss and that unix
> user exists in my nodes ..
>
> so i
i forgot saying that my pod is running process under user jboss and that unix
user exists in my nodes ..
so i create pods under unix user developer ( loged in Openshift master as
developer too ) but the pod has runAs jboss..
thanks in advance
> El 22 mar 2016, a las 11:46, Julio Saura escrib
sorry for the necro post but i have the problem again
now i don’t want to use root account ( cluster admin ) for deploying pods, so i
created a new unix user ( developer ) for deploying on a new project ( project1
)
the pods running under this new unix user are owned by
UID PID PPID
ahh i see
thank you very much, now i see the difference
thanks!
> El 3 mar 2016, a las 17:27, Clayton Coleman escribió:
>
> When you create a pod directly as a cluster admin, you have permission
> to run as any user. So the check allows you to create that process.
> When you run under a repli
When you create a pod directly as a cluster admin, you have permission
to run as any user. So the check allows you to create that process.
When you run under a replication controller, permission has to be
delegated to ensure that the controller (which is acting on your
behalf) can create a pod tha
btw now is working inside the RC with de policies you told me, thanks ;)
but i do not understand that is the difference in running in a RC, it is
supposed that is a controller for handling pods, and in the pod wait worked
fine..
> El 1 mar 2016, a las 16:28, Julio Saura escribió:
>
> hello
hello
thanks for answering
but why is running without problem if i run my image as a POD without doing
that and failing when i use RC instead of POD?
thanks
> El 1 mar 2016, a las 16:21, Clayton Coleman escribió:
>
> Regular Openshift users don't have permission to run as arbitrary
> UIDs.
Regular Openshift users don't have permission to run as arbitrary
UIDs. You can read more here:
https://docs.openshift.org/latest/architecture/additional_concepts/authorization.html#security-context-constraints
To give yourself access as a root user (if you are an admin) run
oadm policy add-
Hello
i have a working open shift running and maybe is my misunderstanding but i have
a problem with RC
so,
i have an own docker image for my app, my entry point in my docker file
creates some directories that are needed for my app to work and starts a
jboss,, so far so good
the image is ru