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 and microservices
  • Run asp.net 4.5 in Docker
  • External Storage for Docker
  • Updating a Symfony app with Docker-compose without losing data
  • Is it possible to allow docker use the host machines dnses?
  • Step by Step Setup Guide to Neo4j Mazerunner in Windows
  • Where can I configure the start user UID for Docker containers?
  • Unable to run docker commands
  • How to manage command line arguments in docker run command?
  • Docker EE Admin UI vs Portainer
  • Spotify docker maven build multiple images
  • Executing bash then running commands in docker
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.