Deploy docker registry in Jelastic

I wish to deploy a private Docker registry in Jelastic environment.

I’ve deployed the registry:2 image from the marketplace and, once logged via ssh into the container, generated the CRT and KEY file.

  • Trouble connecting to a SQL Server Database through a JBoss 6 EAP docker container
  • How to get docker 'objects' completion on mintty-bash from git for windows
  • Access container name in Nginx configuration file
  • Docker stops working inside Vagrant When I Update Guest Additions
  • docker 1.9.1,, doesn't stop docker container
  • Refresh net.core.somaxcomm (or any sysctl property) for docker containers
  • I’ve defined REGISTRY_HTTP_TLS_CERTIFICATE and REGISTRY_HTTP_TLS_KEY pointing to their respective files into the container.

    I’ve exposed the 5000 port through Jelastic’s “endpoint” (resulting mapped to 11000)

    But still when I run:

    $ docker push node4878-lrkwz-registry.jc.neen.it:11000/dockersymfony_application
    The push refers to a repository [node4878-lrkwz-registry.jc.neen.it:11000/dockersymfony_application] (len: 1)
    unable to ping registry endpoint https://node4878-lrkwz-registry.jc.neen.it:11000/v0/
    v2 ping attempt failed with error: Get https://node4878-lrkwz-registry.jc.neen.it:11000/v2/: x509: certificate is valid for , not node4878-lrkwz-registry.jc.neen.it
    v1 ping attempt failed with error: Get https://node4878-lrkwz-registry.jc.neen.it:11000/v1/_ping: x509: certificate is valid for , not node4878-lrkwz-registry.jc.neen.it
    

  • WSO2 Governance Registry, Docker and boot2docker
  • Why don't docker use the host OS for all purposes
  • Dockerizing an SSH Daemon Service using my own key
  • Docker stop exit code -1 if the default CMD is a shell script
  • Dockerfile for tomcat
  • Spring Cloud service Look up error: Load balancer does not have available server for client
  • One Solution collect form web for “Deploy docker registry in Jelastic”

    There are few possible reasons:

    1. As I see there is no Common Name (CN) in your certificate. Try to
      recreate certificate with CN.
    2. Your local daemon has wrong configuration.Try this with info how to use self-signed certificates

    As for me, I’m using option “–insecure-registry”. To add it you need to edit file /etc/default/docker on your local PC and add string (in your case): DOCKER_OPTS="--insecure-registry node4878-lrkwz-registry.jc.neen.it:11000/
    OR INSECURE_REGISTRY='--insecure-registry node4878-lrkwz-registry.jc.neen.it:11000'
    File also can be located at /etc/sysconfig/docker

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.