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?

  • Why are my multiple containers of a Neo4j image sharing data with Docker?
  • How to send logs from tomcat docker container to catalina.out?
  • How to access a host port (bind with ssh -R) from a container?
  • How can I run an arbitrary MySQL command from within a docker container?
  • Calling IdentityServer4 from application behind a HAProxy LoadBalancer
  • xhost command for docker GUI apps (Eclipse)
  • Unable to connect to containers of a swarm in docker-in-docker
  • how to consume rest api of apache nutch docker
  • Dokku installation fails
  • Deploying a network of containers in a single K8s pod
  • Using AWS Simple Workflow to start a docker container
  • how to attach a EBS volume to my container using docker-compose.yml and ecs-cli
  • 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.