Hi Tien, Docker for Mac introduced an internal proxy with Docker CE version 17.12.x. This has been causing problems with apps that didn't expect to see a proxy there, and certain settings like the NO_PROXY env var are ignored. Issues have been reported on github and they seem to be working on them. Until they have a fix, I would recommend downgrading to a pre- 17.12.0 version. You can find download links in their release notes page: https://docs.docker.com/docker-for-mac/release-notes/
Version 17.09.0-ce-mac35 should work fine. On Wed, Feb 7, 2018 at 9:22 AM, Tien Hung Nguyen <[email protected]> wrote: > I have rechecked it and there are indeed no persistent volumes available > by default. All what I did was just to execute this commands 'oc cluster up > --host-data-dir /Users/user/oc-data' on Docker for Mac following this > tutorial: https://github.com/openshift/origin/blob/master/ > docs/cluster_up_down.md > My Docker for Machine has just the Insecure Registry 172.30.0.0/16 added. > > Furthermore, when I start openshift with the command 'oc cluster up > --host-data-dir /Users/user/oc-data' it shows me the following output > message after it has successfully started: > > oc cluster up --host-data-dir /Users/user/oc-data > > Starting OpenShift using openshift/origin:v3.7.1 ... > > Pulling image openshift/origin:v3.7.1 > > Pulled 1/4 layers, 26% complete > > Pulled 1/4 layers, 80% complete > > Pulled 2/4 layers, 81% complete > > Pulled 3/4 layers, 92% complete > > Pulled 4/4 layers, 100% complete > > Extracting > > Image pull complete > > OpenShift server started. > > > The server is accessible via web console at: > > https://127.0.0.1:8443 > > > You are logged in as: > > User: developer > > Password: <any value> > > > To login as administrator: > > oc login -u system:admin > > > 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. > > I'm sure that I don't have a proxy enabled since I'm working from home > where is no proxy configured. > > Please, could tell me how to solve this problem? I didn't have these > problems when I used OpenShift version 3.6 CLI. > > Now, I'm using the following version: > > oc v3.7.1+ab0f056 > > kubernetes v1.7.6+a08f5eeb62 > > features: Basic-Auth > > > Server https://127.0.0.1:8443 > > openshift v3.7.1+ab0f056 > > kubernetes v1.7.6+a08f5eeb62 > > > Regards > Tien > > > 2018-02-04 15:17 GMT+01:00 Michail Kargakis <[email protected]>: > >> Used to be in default as the rest of the infra components. >> >> On Sat, Feb 3, 2018 at 8:53 PM, Clayton Coleman <[email protected]> >> wrote: >> >>> There’s a job that oc cluster up runs to create host PVs. You may want >>> to check that that job ran successfully. I don’t remember exactly what >>> namespace it was created it in >>> >>> On Feb 3, 2018, at 1:10 PM, Tien Hung Nguyen <[email protected]> >>> wrote: >>> >>> Hello, >>> >>> I'm using OpenShift Origin v3.7.1 Client and Server installed on my >>> local Computer (Mac) via Docker on Mac. I started OpenShift using the >>> command oc cluster up --host-data-dir /Users/username/oc-data and tried to >>> deploy my appliocations using a .yml template. However, the deployment >>> stucks because it gives me the following error: >>> >>> Events: >>> >>> FirstSeen LastSeen Count From SubObjectPath Type Reason Message >>> >>> --------- -------- ----- ---- ------------- -------- ------ ------- >>> >>> 17m 1m 63 persistentvolume-controller Normal FailedBinding no >>> persistent volumes available for this claim and no storage class is set >>> >>> >>> After checking my persistent volumes with the command oc get pv, I >>> realized that my containers don't have any pvs available (Message: No >>> resources found. ). Please, could you tell me why the new OpenShift >>> Origin 3.7.1 version doesn't create any pvs by default at the beginning? >>> When I used the old OpenShift Origin 3.6.1 version, I never had that >>> problem when using the same .yaml template for deployment. >>> >>> How can I fix that problem? >>> >>> Regards >>> Tien >>> >>> _______________________________________________ >>> users mailing list >>> [email protected] >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >>> >>> >>> _______________________________________________ >>> users mailing list >>> [email protected] >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >>> >>> >> > > _______________________________________________ > users mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
