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 to use SERVICE_CHECK_HTTP with progrium/consul check-http script?
  • “rsync” was not detected as installed in your guest machine
  • Docker: Unable to commit a built docker image
  • How to deploy jar/war to nexus in the docker build?
  • What's the meaning of docker hub's url design?
  • Can I reference the service name docker-compose.yml
  • Arbitrary Code Execution with Docker
  • Docker images proxy server (private docker registry) using Nexus OSS and reusing its dependency images
  • How to reduce time required by docker image to install dependencies?
  • Unable to run an Android application in a Docker container with Gitlab-CI
  • How do I find a conflicting container that docker reports is not running?
  • Jenkins store workspace outside docker container
  • 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.