artifactory as docker registry

I tried to set up artifactory as docker registry as shown in this video: http://www.jfrog.com/video/artifactory-docker-integration/

However, I don’t have SSL installed in artifactory so I’m using the –insecure-registry flag. (as shown in error in docker build publish plugin and Remote access to a private docker-registry)

  • How to install Material Design Lite Documentation Offline?
  • How to add postgresql library pgroonga when make docker compose?
  • error while loadingDocker: shared libraries: libsystemd-journal.so.0: cannot open shared object file: No such file or directory
  • docker compose vs docker run - node container
  • Docker run returning “snmpd is neither service nor target!? ” while trying to restart it
  • Possible to run Google Standard Managed VM Locally with Docker for Development?
  • Anyway, I don’t know how to figure out the artifactory as docker registry url so I can do this:
    curl -k -uusername:password “http://sdpvvrwm812.ib.tor.company.com:8081/artifactory/api/docker/docker-images”

    This page, http://www.jfrog.com/confluence/display/RTF/Docker+Repositories, shows at the bottom that something called a reverse proxy might be needed? Is this true and if so how do I install such a thing?

  • SonarQube in Docker failes to resolve local host
  • Docker - Access linked Container
  • After Moving Laravel directory to parent, can't see files on Laradock workspace
  • Marathon Docker Tasks Failing
  • curl can get web content hosted in local docker but browser cannot open the page
  • What is the meaning of the IDs shown when a Docker image is pulled?
  • One Solution collect form web for “artifactory as docker registry”

    The reason behind requiring a reverse proxy in front of Artifactory is related to a Docker client limitation – you cannot use a context path when providing the registry path, e.g sdpvvrwm812.ib.tor.company.com:8081/artifactory/api/docker/docker-images is not valid.
    The Docker client assumes you are working with one big registry for all images, while Artifactory allows you to manage multiple registries (repositories) on the same server.

    To overcome this issue you should setup a reverse proxy which will allow the Docker client to send requests to the root context and forward those requests to the correct repository path in Artifactory. For example, forwarding requests from sdpvvrwm812.ib.tor.company.com:8888/ to sdpvvrwm812.ib.tor.company.com:8081/artifactory/api/docker/docker-images

    The Artifactory documentation contains configuration examples for NginX, Apache and HAProxy.
    Notice that there are different configurations for Docker registry API v1 and v2.

    After setting up the reverse proxy, the Docker client should use the proxy in order to access Artifactory.

    If you are using the –insecure-registry flag there is no need to configure an SSL certificate. With older versions of Docker, before this flag was introduced (Docker 1.3.2) it was a mandatory requirement.

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