Re: oc cluster up - dns issue?

Even running cluster up as root the router can't bind to ports 80 and 443. On Wed, 27 Jul 2016 at 9:52 PM, Lionel Orellana wrote: > Don't think so. > > $ sudo netstat -tulpn > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign

Re: Docker layering for jenkins image issue

ok, the changes are not present in the running container. And yes the pod is working on the latest image, which means my image is somehow not updated... So I guess I should create a new image using s2i and then try again? On Wed, Jul 27, 2016 at 1:26 PM, Ben Parees wrote: >

Re: Docker layering for jenkins image issue

On Wed, Jul 27, 2016 at 1:36 PM, Akshaya Khare wrote: > ok, the changes are not present in the running container. > And yes the pod is working on the latest image, which means my image is > somehow not updated... > > So I guess I should create a new image using s2i and

Re: Docker layering for jenkins image issue

On Wed, Jul 27, 2016 at 1:23 PM, Akshaya Khare wrote: > sorry, that was an old command, I ran this command > > *oc new-app -e JENKINS_PASSWORD=password localhost:5000/jenkins-bmi3* > ​ok, i'd certainly expect that to result in a pod running your new image. Can you

Re: Docker layering for jenkins image issue

On Wed, Jul 27, 2016 at 1:19 PM, Akshaya Khare wrote: > Hi Ben, > > Using the below commands I pushed it to my local docker registry: > > > > *# docker tag jenkins_bmi3 localhost:5000/jenkins-bmi3:latest# docker > push localhost:5000/jenkins-bmi3:latest*Then I created a

Re: Docker layering for jenkins image issue

Hi Ben, Using the below commands I pushed it to my local docker registry: *# docker tag jenkins_bmi3 localhost:5000/jenkins-bmi3:latest# docker push localhost:5000/jenkins-bmi3:latest*Then I created a new app using the below command, and a pod got deployed shortly after the app was created

Re: Docker layering for jenkins image issue

On Wed, Jul 27, 2016 at 11:48 AM, Akshaya Khare wrote: > Hi > > While going through the documentation for using *jenkins* image, I found > that we can use the updated image of jenkins by: > >- > >Use Docker layering. >- > >Use the image as a

Docker layering for jenkins image issue

Hi While going through the documentation for using *jenkins* image, I found that we can use the updated image of jenkins by: - Use Docker layering. - Use the image as a Source-To-Image builder Now i found docker layering to be ideal in my case since I have created a new project

Self-signed certificate and oadm diagnostics

Hi, I'm using a self-signed certificate for the public host names of the OpenShift API and web console. Subsequently 'oadm diagnostics' errors with: ERROR: [DCli0006 from diagnostic ConfigContexts@openshift/origin/pkg/diagnostics/client/config_contexts.go:285] For client config

Re: Disable self-provisioning

Hello Jordan It worked Thank you 2016-07-26 16:48 GMT-03:00 Jordan Liggitt : > To delete that cluster role binding: > oc delete clusterrolebinding self-provisioners > > > To just remove that role from the authenticated groups of users: > oadm policy

Re: Every user can authenticate on docker registry on openshift

Correct, the username is ignored, the password is the API token. On Wed, Jul 27, 2016 at 9:34 AM, Den Cowboy wrote: > Okay, and how is this used for Jenkins. > I have a global service account on OpenShift which provides a token which > can be used to authenticate on my

Re: Every user can authenticate on docker registry on openshift

You can authenticate - but you can only pull things you have access to. On Wed, Jul 27, 2016 at 8:59 AM, Den Cowboy wrote: > Is it normal that every user can authenticate on the docker-registry of > openshift? > I was always using the same user as my cluster-admin in my

RE: Persistent Storage MYSQL

all users and all groups which are coming from that IP-range have access. We're able to mount when we're using just a /mnt directory on our host. But not from inside our container. From: dencow...@hotmail.com To: bpar...@redhat.com; users@lists.openshift.redhat.com Subject: RE: Persistent

Re: Persistent Storage MYSQL

what about the permissions of the actual host directory you are exporting? On Wed, Jul 27, 2016 at 9:11 AM, Den Cowboy wrote: > Yeah, that's something which is different. On my master I was working with > exportfs -a etc. > But now it doesn't matter. The permissions are

RE: Persistent Storage MYSQL

Yeah, that's something which is different. On my master I was working with exportfs -a etc. But now it doesn't matter. The permissions are IP based. (we hadded the range in which are cluster is running) [3:09] From: bpar...@redhat.com Date: Wed, 27 Jul 2016 09:04:12 -0400 Subject: Re:

Re: Persistent Storage MYSQL

what are the permissions of the NFS exported volume? and what is in the export definition? On Wed, Jul 27, 2016 at 8:35 AM, Den Cowboy wrote: > I try to make my MySQL pod persistent. > I always did this on training-environmnents where my DNS-server was on my > master

Every user can authenticate on docker registry on openshift

Is it normal that every user can authenticate on the docker-registry of openshift? I was always using the same user as my cluster-admin in my openshift. But now I tried something else: docker login -u userdoesnotexist \ > -p u89cSfZVXBBxw1cYsIlGKcHHYM_ycxxxlI 172.30.xx.xx:5000 Email

Persistent Storage MYSQL

I try to make my MySQL pod persistent. I always did this on training-environmnents where my DNS-server was on my master and I had never issues. Now my NFS is on another server. My pv looks like this { "apiVersion": "v1", "kind": "PersistentVolume", "metadata": { "name": "mysql-data"

Re: oc cluster up - dns issue?

Don't think so. $ sudo netstat -tulpn Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 104.236.65.18:530.0.0.0:* LISTEN 1268/openshift tcp0 0

Re: oc cluster up - dns issue?

I had a similar issue on F23 and oc cluster up, the dns service couldn't be reached by the pods. Restarting firewalld then docker fixed it for me. On Wed, 27 Jul 2016 at 21:22 Clayton Coleman wrote: > Is anything already listening on port 80/443/1936 on your host? Did the

Re: oc cluster up - dns issue?

Is anything already listening on port 80/443/1936 on your host? Did the router pod get created successfully (oc get pods -n default)? On Jul 27, 2016, at 7:12 AM, Lionel Orellana wrote: My iptables has these rules. Is this normal? Chain KUBE-SERVICES (1 references)

Re: oc cluster up - dns issue?

My iptables has these rules. Is this normal? Chain KUBE-SERVICES (1 references) target prot opt source destination REJECT tcp -- 0.0.0.0/0172.30.52.230/* default/router:80-tcp has no endpoints */ tcp dpt:80 reject-with icmp-port-unreachable REJECT

Re: oc cluster up - dns issue?

Further info $ oc get endpoints --namespace=default --selector=router NAME ENDPOINTS AGE router 1h Router has no endpoints? On Wed, 27 Jul 2016 at 3:22 PM, Lionel Orellana wrote: > Forgot to mention > > Openshift v1.3.0-alpha.2 > Docker 1.11.2 > Ubuntu 15.10 > > On