Configuring a docker repository as a subdomain in artifactory

We are trying to set up a docker repository within artifactory version 4.11.1, following is the set up

-- Created a local docker repo - docker-local
-- Created a virtual dokcer repo - docker-virtual
-- Created a remote docker repo - docker-hub
-- Configured docker-local to be the default deployment repo

We are using a multidomain certificate that supports reverse-proxy.company.com and docker-virtual.reverse-proxy.company.com

  • Docker Compose Image Failing
  • ClassNotFoundException when submitting yamr job to remote cluster
  • How to limit IO speed in docker with ceph rbd?
  • Not able to connect to mongodb replica set running in docker in different machine
  • Authenticating a dockerized Spring Boot app against a dockerized & linked ActiveMQ
  • Error with Loadbalancing, Websockets and NodeJS
  • The question is
    Should the nginx configuration be set to the following

    server {
    listen 80;
    listen 443;
    server_name docker-virtual.reverse-proxy.company.com reverse-proxy.company.com;
     ..... other confug
    
    }
    

    With this set up I expect the lients to connect to the virtual repo

    docker push docker-virtual.reverse-proxy.company.com/<my-image>
    

    Is this a valid set up?
    Note that we dont have a wildcard certificate and its not an option.
    Does the multidomain certificate need to support the default deployment directory as well?

  • How to launch a docker with fleet given a dockerfile?
  • Run docker as non-root in a development environment for an specific process
  • How to inform Maven/JVM options for S2I build in OpenShift3
  • How do you add authentication to a docker image?
  • container exit with code 0 while using docker compose file
  • Docker build/push every time - is it practical for continuous deployment?
  • One Solution collect form web for “Configuring a docker repository as a subdomain in artifactory”

    So you can do it that way by having multiple servername statements instead of the wildcard, and then using our wild-card rewrite rule as-is as you suggested.
    There is no need to support anything other than the docker-virtual.reverse-proxy.company.com and the reverse-proxy.company.com as the forward from docker-virtual to the local is internal to artifactory.

    You could also have separate server statements, which would make it easier to have single domain certs separately. The docker one would then be:

    server {
    listen 443;  //docker is ssl only
    server_name docker-virtual.reverse-proxy.company.com;
     ..... other confug
    
    }
    
    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.