Rancher getting 404 responses form private registry URL's

I have rancher set up. I have a private registry using a self signed certificate setup. I followed the guide at http://docs.rancher.com/rancher/configuration/registries/ to set up registry with in rancher. I have also created an ami with my self signed certificate installed. I’m using this ami to create my new hosts. I have a working docker compose file. I have built and pushed my image out to my private registry. When I run rancher compose rancher is unable to get the image from my private registry. Instead rancher is hitting a URL on the registry that is sending back a 404. Why is rancher hitting the wrong URL?

  • Docker instead of multiple VMs
  • Bash script behaves differently from Docker run command instead of inside container itself?
  • Apache Mesos + Docker + Karaf Cellar Cluster
  • How to replicate microservices when consuming same kafka topic?
  • Jenkins Declarative Pipeline - how to display Gatling results?
  • Sending signals to Golang application in Docker
  • How to use docker remote api to create container?
  • LogStash container restarts on Kube pod
  • How to set Puma workers, threads for Rails in Docker
  • kafka image build kompose
  • jBPM-Workbench-Showcase docker image: internal git accessing/ clone function does not work
  • How can I find a Checksum of a Docker Image
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.