Docker Mac Beta using insecure Private Registry

I am using Docker version 1.11.1, build 5604cbe on Mac OS X

On my Mac machine I am trying to do docker push to private docker registry running on remote VM. I am unable to get SSL to work and want to use insecure registry following instructions on How Can I specify DOCKER_OPTS on my Mac so I can push the image to private registry?

  • How do I force `docker stack` to always fetch a new image?
  • Does Docker override files?
  • “Cannot connect to the Docker daemon.” error while building docker image in gitlab-ci docker executor
  • Salt: 'dockerng' __virtual__ returned False
  • docker-compose is not setting container_name from environment variable
  • Docker-compose up causing client is newer than server error
  • Downloading images from custom registry with go-dockerclient hangs
  • What does Kubernetes actually do? [closed]
  • How to rebuild dockerfile quick by using cache?
  • Indices Red/Dangling when upgrading Elasticsearch cluster from 2.x to 5.x in docker
  • How do I connect to gcloud sql with gcloud sql proxy from GKE
  • Docker will not attach to an image
  • 3 Solutions collect form web for “Docker Mac Beta using insecure Private Registry”

    In case other people are having the same Get x509: certificate signed by unknown authority problem, I’ve posted a simple solution on my blog: it all boils down, as @manojlds has pointed out, to whitelisting the server in the Advanced preferences.

    I got the response on docker forums –

    pinata set daemon '{"storage-driver":"aufs","debug":true,"insecure-registries":[""]}'

    Pinata has been removed from more recent versions. You can setup insecure registries from Preferences -> Advanced.

    Currently there is no official CLI based way to do the update.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.