{"id":831,"date":"2018-12-06T16:21:55","date_gmt":"2018-12-06T16:21:55","guid":{"rendered":"https:\/\/www.appservgrid.com\/paw93\/?p=831"},"modified":"2018-12-06T23:45:53","modified_gmt":"2018-12-06T23:45:53","slug":"setting-up-a-docker-registry-with-jfrog-artifactory-and-rancher","status":"publish","type":"post","link":"https:\/\/www.appservgrid.com\/paw93\/index.php\/2018\/12\/06\/setting-up-a-docker-registry-with-jfrog-artifactory-and-rancher\/","title":{"rendered":"Setting Up a Docker Registry with JFrog Artifactory and Rancher"},"content":{"rendered":"

\"\"For any team using
\ncontainers \u2013 whether in development, test, or production \u2013 an
\nenterprise-grade registry is a non-negotiable requirement. JFrog
\nArtifactory<\/a> is much beloved by Java
\ndevelopers, and it\u2019s easy to use as a Docker registry as well. To make
\nit even easier, we\u2019ve put together a short walkthrough to setting things
\nup Artifactory in Rancher.<\/p>\n

Before you start<\/h3>\n

For this article, we\u2019ve assumed that you already have a Rancher
\ninstallation up and running (if not, check out our Quick Start
\nguide<\/a>), and
\nwill be working with either Artifactory Pro or Artifactory Enterprise.
\nChoosing the right version of Artifactory depends on your development
\nneeds. If your main development needs include building with Maven
\npackage types, then Artifactory open source may be suitable. However,
\nif you build using Docker, Chef Cookbooks, NuGet, PyPI, RubyGems, and
\nother package formats then you\u2019ll want to consider Artifactory Pro.
\nMoreover, if you have a globally distributed development team with HA
\nand DR needs, you\u2019ll want to consider Artifactory Enterprise. JFrog
\nprovides a detailed
\nmatrix<\/a>
\nwith the differences between the versions of Artifactory. There\u2019s
\nseveral values you\u2019ll need to select in order to set Artifactory up as
\na Docker registry, such as a public name, or public port. In this
\narticle, we refer to them as variables; just substitute the values you
\nchoose in for the variables throughout this post. To deploy Artifactory,
\nyou\u2019ll first need to create (or already) have a wildcard imported into
\nRancher for \u201c*.$public_name\u201d. You\u2019ll also need to create DNS entries
\nto the IP address for artifactory-lb, the load balancer for the
\nArtifactory high availability architecture. Artifactory will be reached
\nvia $publish_schema:\/\/$public_name:$public_port, while the Docker
\nregistry will be reachable at
\n$publish_schema:\/\/$docker_repo_name.$public_name:$public_port
\n\"\"<\/p>\n

Installing Artifactory<\/h3>\n

While you can choose to install Artifactory on your own with the
\ndocumented
\ninstructions<\/a>,
\nyou also have the option of using Rancher catalog. The Rancher community
\nhas recently contributed a template for Artifactory, which deploys the
\npackage, the Artifactory server, its reverse proxy, and a Rancher load
\nbalancher.<\/p>\n

**A note on reverse proxies: **to use Artifactory as a Docker registry,
\na reverse proxy is required. This reverse proxy is automatically
\nconfigured using the Rancher catalog item. However, if you need to apply
\na custom nginx configuration, you can do so by upgrading the
\nartifactory-rp container in Rancher.<\/p>\n

Note that installing Artifactory is a separate task from setting up
\nArtifactory to serve as a Docker registry, and from connecting that
\nDocker registry to Rancher (we\u2019ll cover how to do these things as
\nwell). To launch the Artifactory template, navigate to the community
\ncatalog in Rancher. Choose \u201cPro\u201d as the Artifactory version to launch,
\nand set parameters for schema, name, and port:
\n\"\"<\/p>\n

Once the package is deployed, the service is accessible through
\n[$publish_schema:\/\/$publish_name:$publish_port]<\/p>\n

Configure Artifactory<\/h3>\n

At this point, we\u2019ll need to do a bit more configuration with
\nArtifactory to complete the setup. Access the Artifactory server using
\nthe path above. The next step will be to configure the reverse proxy and
\nto enable Docker image registry integration. To configure the reverse
\nproxy, set the following parameters:<\/p>\n