Re: Recent Docker update breaks OpenShift Origin/OKD installation.
On Tue, Dec 4, 2018 at 11:29 PM Gilles Le Bris wrote: > Can someone confirm that the recent docker update from docker-1.13.1-75 to > docker-1.13.1-84 in the CentOS extras package repository breaks OpenShift > Origin/OKD installation in v3.9 and v3.11? > There is an issue with latest docker update and here is the bugzilla for the same https://bugzilla.redhat.com/show_bug.cgi?id=1655214 -Lala > ___ > dev mailing list > dev@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Origin 3.10 release
Hi, We are working on code changes required for running (cluster up) Origin3.10 in Minishift. So wondering when can we expect v3.10 alpha (or any) release? Thanks, Lala ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Re: Unpredictable oc binary path for Origin version v3.7.0
On Thu, Nov 30, 2017 at 8:41 PM, Clayton Coleman <ccole...@redhat.com> wrote: > I can publish them to github for 3.7. We’re looking to reduce the amount > of effort required to publish binaries so we can do it more often > Please do publish them to github for 3.7. It will give us sometime to prepare for the modification on Minishift end. Also I did not understand how not publishing to github is helping to reduce the amount of effort to publish binaries. I guess you are using automated release process anyway, isn't it? > . Expect binaries to be published to GCS in the future. > > On Nov 30, 2017, at 2:05 AM, Lalatendu Mohanty <lmoha...@redhat.com> > wrote: > > Hi, > > Till v3.7.0-rc.0 release oc binaries were published in github release > page [1] but with 3.7.0 the location has changed and causing minishift > start --openshift-version v3.7.0 to fail. > > From Minishift side we can change the code to point it to the new location > but the new location is difficult to guess programmatically because It > seems to contain a build id "1032" which makes it hard for third parties > to determine. > > If we can not predict the location then Minishift users can not use a new > version of Origin without code changes in Minishift which is not desirable. > > Filed an github issue on the same : https://github.com/openshift/ > origin/issues/17527 > > Is this going to be the normal going forward? Is there a way to predict > the oc binary path from Origin version? Do you have plan to setup a mirror > some place with predictable URL? > > [1] https://github.com/openshift/origin/releases/tag/v3.7.0-rc.0 > > [2] https://gcsweb-ci.svc.ci.openshift.org/gcs/origin-ci- > test/branch-logs/origin/v3.7.0/builds/test_branch_origin_ > cross/1032/artifacts/zips/ > > Thanks, > > Lala > > ___ > dev mailing list > dev@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Unpredictable oc binary path for Origin version v3.7.0
Hi, Till v3.7.0-rc.0 release oc binaries were published in github release page [1] but with 3.7.0 the location has changed and causing minishift start --openshift-version v3.7.0 to fail. >From Minishift side we can change the code to point it to the new location but the new location is difficult to guess programmatically because It seems to contain a build id "1032" which makes it hard for third parties to determine. If we can not predict the location then Minishift users can not use a new version of Origin without code changes in Minishift which is not desirable. Filed an github issue on the same : https://github.com/openshift/origin/issues/17527 Is this going to be the normal going forward? Is there a way to predict the oc binary path from Origin version? Do you have plan to setup a mirror some place with predictable URL? [1] https://github.com/openshift/origin/releases/tag/v3.7.0-rc.0 [2] https://gcsweb-ci.svc.ci.openshift.org/gcs/origin-ci-test/branch-logs/origin/v3.7.0/builds/test_branch_origin_cross/1032/artifacts/zips/ Thanks, Lala ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Issues exposing the docker registry
Hi, We are trying to expose the OpenShift docker registry to users of Minishift and will automate the steps in a way that it would be easier for an user to use it as a local docker registry. I have manually tried the steps [1] [2] on minishift but getting the following error i.e. "unauthorized: authentication required" when I am trying to push a docker image. $ docker login -u developer -p 5lsWLLaKeIpXUGtGnPMzK7R0aUDojW8o91wfLojqrGw docker-registry-default.192.168.42.83.nip.io:80 Login Succeeded $ docker push docker-registry-default.192.168.42.83.nip.io:80/myproject/busybox The push refers to a repository [docker-registry-default.192.168.42.83.nip.io:80/myproject/busybox] 38ac8d0f5bb3: Pushing [==>] 1.143 MB unauthorized: authentication required Any pointers to fix the issue will be appreciated. FYI, Minishift uses "cluster up" mechanism to boot strap the OpenShift instance. [1] https://github.com/minishift/minishift/issues/254#issuecomment-284985284 [2] https://github.com/minishift/minishift/issues/254#issuecomment-285591570 Thanks, Lala ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
SELinux and OC cluster up/down
Hi, As per documentation [2] SELinux is a prerequisite for OpenShift installation. However for "oc cluster up/down" environment there is no mention of SELinux [2]. Is it ok if an application developed in OpenShift environment provided by "oc cluster up" that is without SELinux or SELinux disabled and then we try to run it in a proper OpenShift environment with SELinux enabled? Going by my SELinux experience, I think we should keep SELinux enabled in the development environment as it would in the production environment, else it can completely break the application. But the lack of documentation and understanding around role of SELinux in "oc cluster up" environment led to some confusion [3]. Can someone shed some light on this? Thanks a lot in advance. [1] https://docs.openshift.org/latest/install_config/install/prerequisites.html#prereq-selinux [2] https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md [3] https://github.com/minishift/minishift-centos-iso/issues/1 Thanks, Lala ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Enabling Incremental Builds
Hi, Can I enable "incremental builds" for the whole OpenShift setup? I have gone through the Origin documentation [1] and it seems I need to change the build configuration of individual application to enable incremental builds. [1] https://docs.openshift.org/latest/dev_guide/builds.html#incremental-builds Thanks, Lala ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
