Re: Bad Elasticsearch queries

Hey Alex, You're right, the query is incorrect. There was a BZ opened to address this very issue[1]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1358674 On Wed, Aug 10, 2016 at 1:50 PM, Alex Wauck wrote: > When I click the "View archive" link for a pod's logs, I get a Kibana page > with a

Bad Elasticsearch queries

When I click the "View archive" link for a pod's logs, I get a Kibana page with a query like this: kubernetes_pod_name: some-pod-name && kubernetes_namespace_name: random-namespace Am I missing something, or should it instead be this: kubernetes_pod_name: "some-pod-name" && kubernetes_namespace_

Re: Problem authenticating to private docker registry

No worries. Thanks everyone for the help so far. Let me know if there's any other helpful information I can provide. I am able to pull the image down without any issues if I use the latest tag in case that helps: [root@os-node1 ~]# docker pull docker-lab.example.com:5000/testwebapp:latest Trying

Re: Problem authenticating to private docker registry

Ok, thanks. I'm not really involved with the registry any more, so I'll have to defer to Maciej and Michal. We may need to try to reproduce to see what's going on. Sorry I couldn't be more helpful. Andy On Wed, Aug 10, 2016 at 2:18 PM, Tony Saxon wrote: > [root@os-node1 ~]# docker pull docker-l

Re: Problem authenticating to private docker registry

[root@os-node1 ~]# docker pull docker-lab.example.com:5000/testwebapp@sha256:9799a25cd6fd7f7908bad740fc0c85823e38aa22afb22f687a5b8a3ed2bf9ec3 Trying to pull repository docker-lab.example.com:5000/testwebapp ... manifest unknown: manifest unknown On Wed, Aug 10, 2016 at 2:07 PM, Andy Goldstein w

Re: Problem authenticating to private docker registry

Tony, can you show the output when you try to manually 'docker pull'? On Wed, Aug 10, 2016 at 2:04 PM, Cesar Wong wrote: > Hmm, I didn't know the issue existed between 1.10 and 1.12 as well. > > Andy, what would you recommend? > > > On Aug 10, 2016, at 1:58 PM, Tony Saxon wrote: > > Ok, maybe t

Re: Problem authenticating to private docker registry

Hmm, I didn't know the issue existed between 1.10 and 1.12 as well. Andy, what would you recommend? > On Aug 10, 2016, at 1:58 PM, Tony Saxon wrote: > > Ok, maybe that is the issue. I can not do the docker pull referencing the > sha256 hash on the node. > > The docker version running on the

Re: Problem authenticating to private docker registry

Ok, maybe that is the issue. I can not do the docker pull referencing the sha256 hash on the node. The docker version running on the node is docker 1.10.3, and the docker version on the machine that pushed the image is 1.12.0. Is there a potential workaround for this, or do I need to get the docke

Re: Problem authenticating to private docker registry

Tony, The only other time that I've seen the manifest not found error was when there was a version mismatch between the Docker version that pushed the image vs the version that was consuming the image (ie. images pushed with Docker 1.9 and pulled with Docker 1.10). Are you able to pull the imag

Re: Problem authenticating to private docker registry

I'm not sure if this has anything to do with it, but I looked at the details of the imagestream that I imported and see that it has this as the docker image reference: status: dockerImageRepository: 172.30.11.167:5000/testwebapp/testwebapp tags: - items: - created: 2016-08-10T13:26:01Z

Re: Problem authenticating to private docker registry

Not a problem, can you point me in the right direction for how to get those logs? For the first one, I know I can set the USER option in the dockerfile that builds the docker image. Does it matter what user I set that as? I'm assuming that the user needs to exist on the nodes... On Wed, Aug 10, 2

Second master-api fails to start

I'm installing OpenShift for the first time on internal servers that were provisioned and then configured by me. I had to host the repos internally on our Artifactory server as the internal cluster has no direct internet access. I followed all of the steps here: https://docs.openshift.org/latest/in

Re: Problem authenticating to private docker registry

Maciej, In this case, Tony is trying to connect to the OpenShift registry, so the secret should exist; the dockercfg secret for the project's default service account. Tony, two things that may be your issue: 1) You're using a route for your registry (docker-lab.example.net

Re: Problem authenticating to private docker registry

You need to follow the docs here: https://docs.openshift.org/latest/dev_guide/managing_images.html#private-registries to setup the secret in the same project your ImageStream is created and then re-import the image. During import proper secrets will be picked automatically based on the urls of the

Re: cluster up - reuse registry address

Lionel, So is it working for you now? > On Aug 9, 2016, at 11:10 PM, Lionel Orellana wrote: > > Digging through the go libraries used for parsing the command options I found > that setting the no_proxy variable like this works: > > -e \"no_proxy=172.17.0.3,172.17.0.4\" > > It all comes down

Resolving localhost (IPv6 issue?)

Hi, We were debugging an issue yesterday where 'localhost' could not be resolved inside a container in openshift origin v1.3.0-alpha.3. I'm not sure if this is openshift or kubernetes-related, but thought I'd ask here first. We have two containers running on a pod, and one container is conne