Yeah that seems to work for now, thanks. I will see if need a newer version though.
Posts made by nicholas
Replication Controllers are not cleaned up
I am currently constantly reaching the replication controller quota limit of 30.
oc getshows that most of them have a desired count of 0 and a current count of 0. It seems that the replication controllers of old deployments don't get cleaned up. Am I doing something wrong here or is this a bug?
NAME DESIRED CURRENT AGE demoapi-55 0 0 19h demoapi-62 0 0 17h demoapi-63 0 0 17h demoapi-64 0 0 17h demoapi-65 0 0 16h demoapi-66 0 0 1h demoapi-67 0 0 1h demoapi-68 0 0 1h demoapi-69 0 0 1h demoapi-70 1 1 32m demodashboard-29 0 0 18h demodashboard-30 0 0 17h demodashboard-31 0 0 17h demodashboard-32 0 0 17h demodashboard-33 0 0 17h demodashboard-34 0 0 16h demodashboard-35 0 0 1h demodashboard-36 0 0 1h demodashboard-37 0 0 1h demodashboard-38 0 0 33m demodashboard-39 1 1 32m elasticsearch-5 0 0 18h elasticsearch-6 1 1 18h mariadb-1 0 0 23d mariadb-2 0 0 16d mariadb-3 0 0 6d mariadb-4 1 1 6d mariadb-5 0 0 4d openshift-rabbitmq-1 0 0 16d openshift-rabbitmq-2 1 1 5d
I am currently trying to spin up an elasticsearch service. I tried to start with the official elasticsearch docker image (https://hub.docker.com/_/elasticsearch/) but the problem is that it runs either under the user elasticsearch or under the user root.
Are there any convenient ways of modifying such an image to work under openshift? Can I somehow find all files that are accessible to the elasticsearch user and change the permissions such that it works under openshift?
Or did anyone have any luck with a different elasticsearch image?
RE: Docker Registry accessible from outside OpenShift
For me the login works but when I try to push an image I get:
unauthorized: authentication required
source2image with custom builder image
I am currently trying to create a source2image build using a custom private underlying builder image. I first try to upload an already built docker image to the registry using docker login and docker push. I got an authentication required message even though the login was successfull.
Then my next approach was to create the image on openshift using a docker build. I uploaded my Dockerfile to a private repostiory and created a new build on openshift that pulls that repository and builds the Dockerfile. The problem is that that build is stuck with the following message:
Connected to APPUiO build vm manager
Verifying service account permissions with OpenShift
Service account is authorized to access namespace '<myproject>', queueing build job
I tried shutting down all the other processes that I have running in order to make sure its not a problem with my quota but nothing happens.
Am I doing something wrong or is this an internal problem?