Hi,

Could you please isolate your problem with following tests? I would like
you to check if they could reproduce your issue or not.

test#1. Build and Deploy from internal registry (with openshift project's
php test image).

  $ oc new-app https://github.com/openshift/sti-php.git
--context-dir=5.5/test/test-app --strategy=source

test#2. Deploy from docker hub w/o build

  $ oc new-app openshift/hello-openshift

test#3. Deploy from docker hub w/o build,deploymentConfig

 NOTE: Please delete previous app by "oc delete all -l
app=hello-openshift", before running test#3.
 $ oc create -f
https://raw.githubusercontent.com/openshift/origin/master/examples/hello-openshift/hello-pod.json

If test#1 succeeded, your image has some issue. (it also might be
privilege.)
If test#1 failed but test#2 succeeded, the deployment from your internal
registry has some issue.
If test#1,#2 failed but test#3 succeeded, your deploymentConfig has some
issue.
If test#1,#2,#3 failed, most probably your docker infrastructure has some
issue.

Thanks,
Kenjiro

On Sun, Feb 7, 2016 at 1:52 PM, Dean Peterson <[email protected]>
wrote:

> Actually, I meant I changed runAsUser to runAsAny in scc restricted.
>
> On Sat, Feb 6, 2016 at 10:48 PM, Dean Peterson <[email protected]>
> wrote:
>
>> 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 <[email protected]>
>> 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 <[email protected]>
>>> 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 <[email protected]>
>>>> 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
>>>> https://gist.github.com/deanpeterson/27db87427a15a5c7421c
>>>>
>>>> Openshift console on startup
>>>> https://gist.github.com/anonymous/0973fa19361337891110
>>>>
>>>> Event Log Image:
>>>> <image.png>
>>>>
>>>> _______________________________________________
>>>> users mailing list
>>>> [email protected]
>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>>>
>>>>
>>>
>>
>
> _______________________________________________
> users mailing list
> [email protected]
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>


-- 
Kenjiro NAKAYAMA <[email protected]>
GPG Key fingerprint = ED8F 049D E67A 727D 9A44  8E25 F44B E208 C946 5EB9
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to