Re: Hard Disk is full because of OpenShift Origin

I have checked the volumes already using the docker command docker volume ls. However, everything seems pretty normal there. Furthermore, I have checked my images with docker images ls. I have found a lot of old images created by OpenShift, which used a lot of GBs on my Hard Disk. That‘s why I

Re: Hard Disk is full because of OpenShift Origin

See if you have a lot of docker volumes that haven't been cleaned up properly. docker volume ls Maybe that is hanging onto space. Graham > On 27 Oct 2017, at 8:37 am, Tien Hung Nguyen wrote: > > Hi everybody, > > I have a problem with my hard drive space. Since

Hard Disk is full because of OpenShift Origin

Hi everybody, I have a problem with my hard drive space. Since I'm using OpenShift locally with Docker, I have the problem that my hard drive space gets full very fast and I can't remove it. I have already run the commands 'oc cluster down' and the 'docker rmi [imageip] commands to deleted unused

Re: OCP: Failed to push image: unauthorized: authentication req, uired

Ah I think when I first installed the Origin cluster there were all these problems with the registry ip and the proxy so I created the registry form a yml file (to keep the ip consistent) and that yml file didn't set the proxy vars. These problems are gone now that the default registry is set to

Re: OCP: Failed to push image: unauthorized: authentication req, uired

On Thu, Oct 26, 2017 at 10:45 PM, Lionel Orellana wrote: > I have an Origin 3.6 cluster and the proxy vars are not set in the > registry pod at all. > > -bash-4.2$ oc rsh docker-registry-9-c9mgd env | grep PROXY > > -bash-4.2$ > > Whereas in the OCP 3.6 cluster they are. > >

Re: OCP: Failed to push image: unauthorized: authentication req, uired

I have an Origin 3.6 cluster and the proxy vars are not set in the registry pod at all. -bash-4.2$ oc rsh docker-registry-9-c9mgd env | grep PROXY -bash-4.2$ Whereas in the OCP 3.6 cluster they are. -bash-4.2$ oc rsh docker-registry-1-9z8p2 env | grep PROXY

Re: OpenShift on AWS - Playbooks

On 26.10.2017 15:23, Clayton Coleman wrote: > The latter is still being actively developed - that will be the future > direction but is not yet ready for genera use. Our work towards > leveraging node bootstrapping and using pre-baked AMIs is also not > completely finalized, so no expectation of

Re: OpenShift on AWS - Playbooks

The latter is still being actively developed - that will be the future direction but is not yet ready for genera use. Our work towards leveraging node bootstrapping and using pre-baked AMIs is also not completely finalized, so no expectation of stability on the latter. > On Oct 26, 2017, at 9:18

OpenShift on AWS - Playbooks

Hi, There are at least two different "official" approaches to get OpenShift on AWS up and running: 1. https://github.com/openshift/openshift-ansible-contrib/tree/master/reference-architecture/aws-ansible 2. https://github.com/openshift/openshift-ansible/tree/master/playbooks/aws Which one of

Re: OCP: Failed to push image: unauthorized: authentication req, uired

On Thu, Oct 26, 2017 at 12:43 PM, Lionel Orellana wrote: > This works.Would have thought the api server address was added > automatically to NO_PROXY? > it's supposed to be, but i do think there is a bug open where people have seen it not be added:

Re: OCP: Failed to push image: unauthorized: authentication req, uired

This works.Would have thought the api server address was added automatically to NO_PROXY? -bash-4.2$ oc rsh docker-registry-1-9z8p2 sh-4.2$ export NO_PROXY=$NO_PROXY,172.23.192.1 sh-4.2$ oc whoami system:serviceaccount:default:registry sh-4.2$ On 26 October 2017 at 20:54, Ben Parees

Re: OCP: Failed to push image: unauthorized: authentication req, uired

On Thu, Oct 26, 2017 at 11:50 AM, Lionel Orellana wrote: > I didn't put it there. > > I another cluster this works. > > -bash-4.2$ oc rsh docker-registry-9-c9mgd oc whoami > system:serviceaccount:default:registry > > -bash-4.2$ oc rsh docker-registry-9-c9mgd which oc >

Re: OCP: Failed to push image: unauthorized: authentication req, uired

On Thu, Oct 26, 2017 at 10:53 AM, Lionel Orellana wrote: > Interestingly > > -bash-4.2$ oc rsh router-1-bf95x oc whoami > system:serviceaccount:default:router > -bash-4.2$ oc rsh docker-registry-1-9z8p2 oc whoami > Unable to connect to the server: Service Unavailable >

Re: OCP: Failed to push image: unauthorized: authentication req, uired

Well this works from one of the hosts (using a token from oc whoami) curl -X GET -H "Authorization: Bearer $TOKEN" https://172.23.192.1/oapi/v1/users/~ In the error msg msg="*invalid token*: Get https://172.23.192.1:443/oapi/v1/users/~ : Service

Re: OCP: Failed to push image: unauthorized: authentication req, uired

On Thu, Oct 26, 2017 at 8:11 AM, Lionel Orellana wrote: > Hi, > > In a new OCP 3.6 installation I'm trying to deploy JBoss EAP 7.0 from the > catalog. > > This is in a project for which I am the admin. > > It's failing to push the image to the registry > > Pushing image

Re: oc cluster up - router not starting

Hi Cesar, I stopped apache and now it works. Thanks a lot for help. Best Regards, Jan On Wed, Oct 25, 2017 at 8:06 PM, Cesar Wong wrote: > Hi Jan, > > So I see this in your log: > > E1025 15:45:01.4085336242 pod_workers.go:182] Error syncing pod >

Re: OCP: Failed to push image: unauthorized: authentication req, uired

I've seen the issue where this error happens on the first build attempt. However I'm getting the error on subsequent builds. This is the first cluster I configure with the openshift-ovs-multitenant plugin. Could that be

OCP: Failed to push image: unauthorized: authentication req,uired

Hi, In a new OCP 3.6 installation I'm trying to deploy JBoss EAP 7.0 from the catalog. This is in a project for which I am the admin. It's failing to push the image to the registry Pushing image docker-registry.default.svc:5000/bimorl/jboss-eap70:latest ... Registry server Address: Registry