title: Run jhipster-registry in production
body: <p>This is a continuation of my previous question about running a <a href="https://stackoverflow.com/questions/36544921/jhipster-docker-compose-deploy-to-aws">jhipster microservices application on AWS</a>. </p>
  
  <p>I've used <code>docker-machine</code> to create a new VM with Docker installed.</p>
  
  <p>I have setup docker registry, and pushed my images to it, as well as logged into this registry on the AWS-VM.</p>
  
  <p>I attempted to copy the contents of the <code>/docker-composer</code> directory I generated using <code>yo jhipster:docker-compose</code> and attempted to run:</p>
  
  <p><code>docker-compose up -d</code></p>
  
  <p>But I receive the error:</p>
  
  <pre><code>ubuntu@aws-test:~/docker-compose$ sudo docker-compose up
  Unsupported config option for services service: 'jhipster-registry'
  </code></pre>
  
  <p>I can manually run the jhipster-registry with docker, but as there are many other underlying services I'd prefer to create a production <code>docker-compose.yml</code> file.</p>