openshift-origin

List of all environment variables for a Pod

由 拈花ヽ惹草 提交于 2019-12-11 06:37:01
问题 I have a web app on OpenShift v3 (all-in-One), using the Wildfly Builder Image. In addition, I created a service named xyz, to point to an external host+IP. Something like this: "kind": "Service", "apiVersion": "v1", "metadata": { "name": "xyz" }, "spec": { "ports": [ { "port": 61616, "protocol": "TCP", "targetPort": 61616 } ], "selector": {} } I also have an endpoint, pointing externally, but that is not relevant for this question. When deployed, my program can access an environment variable

Making openshift origin docker containers persistent after reboot

由 穿精又带淫゛_ 提交于 2019-12-11 06:28:37
问题 I am new to openshift and need to know if it is possible to make all containers in openshift origin persistent after restarting the oc cluster or rebooting the server. The tutorial i followed requires one do the following in order to create a cluster oc cluster up The problem i am running into now is that login into my openshift application after, doing an oc cluster down && oc cluser up doesn't show any of my running containers. I tried restarting all of them by doing a docker start $(docker

Unable to resolve github.com from OpenShift origin pods

由 独自空忆成欢 提交于 2019-12-10 17:47:27
问题 I have a basic OpenShift origin cluster started with oc cluster up Now, in the default 'MyProject' i wanted to build a source from git repo and it's failing with the error Could not resolve host: github.com; Name or service not known Even I tried setting up gogs and migrate the public hosted source code on github.com to gogs pod but throwing same error. Kindly advise if there are any additional network settings required during OpenShift cluster setup in order to access github.com or any other

Minishift: Could not resolve: *.192.168.64.2.nip.io

由 强颜欢笑 提交于 2019-12-10 16:36:13
问题 I have installed minishift on OSX with brew: brew cask install minishift-beta ... $ minishift version Minishift version: 1.0.0 I have sucessfuly started minishift, and created node-ex example application and exported it: $ oc get route NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD nodejs-ex nodejs-ex-myproject.192.168.64.2.nip.io nodejs-ex 8080-tcp None However I can not reach .192.168.64.2.nip.io : $ curl nodejs-ex-myproject.192.168.64.2.nip.io curl: (6) Could not resolve host:

Importing Docker Images Images From The Public Registry Into OpenShift

由 落花浮王杯 提交于 2019-12-10 12:06:29
问题 I am trying to deploy an Ubuntu Image from the here on OpenShift Online (Next Generation). These are the steps I followed in doing so $ oc new-project test $ oc new-app jedisct1/phusion-baseimage-latest I then deployed from the WebConsole However I get a failed deploy and an error status of "image pulled back off" on the pod page. Any particular thing that I may be doing wrong? Below are the logs of the entire proccess. root@home:~# oc new-project test Now using project "test" on server

How to Enable Systemd service in openshift/jenkins-1-centos7 docker container?

由 跟風遠走 提交于 2019-12-10 11:37:54
问题 I have a situation where I need to start some services within this jenkins container to make it work in our project. So i need Systemd enabled in order to do that... As of now I get the below error when I try to run "systemctl" command within this container: Failed to get D-Bus connection: Operation not permitted Which is expected. Now on my research, I found that if we use the below docker file to create an image and then run a container, we should be able to run systemctl commands: FROM

Error running openshift/origin docker: Error running 'chcon' to set the kubelet volume root directory SELinux context

由 泪湿孤枕 提交于 2019-12-10 11:34:57
问题 When I run the openshift/origin docker image , I see this error in logs of the container ( $ docker logs origin ). Error running 'chcon' to set the kubelet volume root directory SELinux context Is this a known issue or can it be ignored or did I miss anything? The commandline I used is as docker run -d --name "origin" -e "http_proxy=$http_proxy" -e "https_proxy=$https_proxy" -e "no_proxy=$no_proxy" --privileged --pid=host --net=host -v /:/rootfs:ro -v /var/run:/var/run:rw -v /sys:/sys

OpenShift V3 vs. OpenShift V2 [closed]

由 大憨熊 提交于 2019-12-10 01:36:31
问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed 4 years ago . I'm searching for a main difference between OpenShift V3 and V2. Is OpenShift V2 working like this?: https://www.openshift.com/walkthrough/how-it-works And how are Docker and Kubernetes working in V3? Can someone give me a clear explanation about the build-up of OpenShift V2 and

How to Enable Systemd service in openshift/jenkins-1-centos7 docker container?

由 爷，独闯天下 提交于 2019-12-08 23:38:29
I have a situation where I need to start some services within this jenkins container to make it work in our project. So i need Systemd enabled in order to do that... As of now I get the below error when I try to run "systemctl" command within this container: Failed to get D-Bus connection: Operation not permitted Which is expected. Now on my research, I found that if we use the below docker file to create an image and then run a container, we should be able to run systemctl commands: FROM docker.io/openshift/jenkins-1-centos7 MAINTAINER "you" your@email.here ENV container docker RUN (cd /lib

What is CrashLoopBackOff status for openshift pods?

由 被刻印的时光 ゝ 提交于 2019-12-08 18:48:33
问题 There is more than one example where I have seen this status from a pod running in openshift origin. In this case it was the quickstart for the cdi camel example. I was able to successfully build and run it locally (non - openshift) but when I try to deploy on my local openshift (using mvn -Pf8-local-deploy ), I get this output for that particular example (snipped for relevance) :- [vagrant@vagrant camel]$ oc get pods NAME READY STATUS RESTARTS AGE cdi-camel-z4czs 0/1 CrashLoopBackOff 4 2m
订阅 openshift-origin