origin: cluster up fails to push to the registry on Docker for Mac CE 17.12.0 and newer

Docker for Mac CE 17.12.0 introduced an internal proxy for Docker that prevents pushes into the local OpenShift registry when running a cluster with cluster up

You also get a warning when starting cluster up like:

WARNING: An HTTP proxy (docker.for.mac.http.internal:3128) is configured for the Docker daemon, but you did not specify one for cluster up
WARNING: An HTTPS proxy (docker.for.mac.http.internal:3129) is configured for the Docker daemon, but you did not specify one for cluster up
WARNING: A proxy is configured for Docker, however 172.30.1.1 is not included in its NO_PROXY list.
   172.30.1.1 needs to be included in the Docker daemon's NO_PROXY environment variable so pushes to the local OpenShift registry can succeed.

For now, the workaround is to downgrade Docker to a version prior to 17.12.0. You can find download links to previous releases in their release note page: https://docs.docker.com/docker-for-mac/release-notes/

Open Issues: https://github.com/docker/for-mac/issues/2506 https://github.com/docker/for-mac/issues/2470 https://github.com/docker/for-mac/issues/2467 https://github.com/docker/for-mac/issues/2386

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 23
Comments: 46 (12 by maintainers)

Links to this issue

Best way to copy/backup host data directory?

Most upvoted comments

FYI OpenShift 4.0 won’t run “bare” on macOS, period. Minishift is the only viable path to running a local cluster on macOS at this point.

@csrwng once minishift supports 4.0 we can probably close this issue.

adambkaplan on Oct 11, 2018

Docker Community Edition 18.03.0-ce-mac59 2018-03-26 Fix for the HTTP/S transparent proxy when using “localhost” names (e.g. host.docker.internal).

This does not fix the issue. So don’t upgrade.

mikz on Apr 6, 2018

@riuvshin cluster up works on RHEL/CentOS/Fedora, and in principle any other Linux distro that supports docker and/or cri-o.

FYI cluster up is going away with 4.0. I’d refer you to openshift/installer if you want to follow how 4.0 installations will work.

adambkaplan on Oct 11, 2018

If you head over to okd.io and download minishift, it uses the latest version of Openshift Origin…

$ minishift start $ minishift oc-env $ oc login etc

Hate having the VM but it works.

bobbydeveaux on Nov 20, 2018

Confirming that I’m still seeing this with 2018-04-30 18.03.1-ce-mac65

cmcconnell1 on May 29, 2018

@adambkaplan what about Linux? would it still be possible to run oc cluster up ? that is a significant change that will break a lot of CI testing pipelines where products are tested on local openshift clusters. For testing purposes there is no way to run whole proper OS cluster and in the same time you can’t run minishift with VM backend on CI infras due to nested virtualization issues.

riuvshin on Oct 11, 2018

@leetrout @mikz for OpenShift 3.11, the barrier is the outstanding docker for mac issue, which has been there for quite some time. Running “bare” via oc cluster up (which is what I meant) will fail if you’re using Docker for Mac > 17.09.

OpenShift 4.0 (which is currently alpha.0) is a whole different ballgame. We don’t have support for running local clusters on a Mac at present.

adambkaplan on Oct 11, 2018

@fg78nc that is gone in 3.10.

mikz on Sep 3, 2018

@cmcconnell1 I just settled on oc cluster up --create-machine.

mikz on Jun 20, 2018

same here, is there any other workaround for this? I don’t want to downgrade… adding 172.30.1.1 to no_proxy in docker prefs does not help docker Version 18.02.0-ce-mac53 (22617)

riuvshin on Feb 23, 2018

I would hold on fixing this until @deads2k finish the internal refactoring of cluster up.

mfojtik on Feb 14, 2018