[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Still having trouble with 1.1.1

The last time I had containers starting and the logs were blank I needed to set the runAsUser to runAsAny because I use root inside my docker files.  I checked that setting and the scc privileged file is set to runAsAny.

On Sat, Feb 6, 2016 at 10:36 PM, Dean Peterson <peterson dean gmail com> wrote:
The container log is empty.  
docker logs <container id> just moves to the next line.

On Fri, Feb 5, 2016 at 2:06 PM, Clayton Coleman <ccoleman redhat com> wrote:
The deployment logs seems to be indicating that your first container did not start cleanly in 120s.  What do the logs of that container (via docker or via oc logs) show?

On Feb 5, 2016, at 10:16 AM, Dean Peterson <peterson dean gmail com> wrote:

I am still evaluating Openshift for use with the State of MN.  I am testing it on a separate project of mine.  I was fairly impressed with Openshift until I started having significant problems with no indication what is wrong.

On every new build (for every service), the subsequent deployment of the associated service fails.  The pods remain in pending state and ultimately the deployment indicates failure.  I have to manually delete the deployment config, then delete the service and delete the pods.  Then I add the service back using the same template I used to create it in the first place.  I have to do that about 4 times before the pods successfully deploy.  I did open a ticket as requested about a week ago; https://bugzilla.redhat.com/show_bug.cgi?id=1303273

The latest deployment failure is again showing no indication what is causing the problem:

Deployment Logs

Openshift console on startup

Event Log Image:
users mailing list
users lists openshift redhat com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]