JFrog Artifactory

Note: The JFrog Artifactory service is deprecated, and no further development will be made against this tile.

Docker Registry

The JFrog Artifactory product includes a fully featured Docker Registry, supporting both v1 and v2 APIs, with built-in security and the ability to proxy to remote images.

For more details on how to use the Docker Registry see here.

Two URLs are registered to access to the Docker Registry:

  1. https://artifactory-docker-dev.system-domain.my-pcf.com
  2. https://aritfactory-docker-prod.system-domain.my-pcf.com

At the moment these route names are not configurable.

Currently each route goes to a docker-v1 repository and a virtual repository for v2.

For artifactory-docker-dev, it points at: docker-dev-local v1 docker local repository and the docker-dev v2 docker virtual repository.

For artifactory-docker-prod, it points at: docker-prod-local v1 docker local repository and the docker-prod v2 docker virtual repository.

Important Note: If you want to use a new docker client (greater than 1.6) to push docker v1 images for use with v1 tools such as diego or cf push, the only way to do this is to disable the virtual repository for the end point. If, for example, I want to use a new docker client to push to docker-dev-local, I should delete the docker-dev virtual repository.

Additional Note: The virtual repositories come pre-configured with a specific configuration, described below; however, you may update this configuration with any virtual repository behavior you desire, provided you do not change the name, for access to docker v2 registries. As noted above, if you want a plain v1 repository, you may wish to delete the virtual repository.

docker-dev is configured as a virtual repository which includes the following repositories:

  • docker-dev-local2 (default deployment) a local repository for storing your docker images
  • docker-prod the docker virtual repository below and
  • dockerhub a remote repository that points to dockerhub.

docker-prod is configured as a virtual repository which includes:

  • docker-prod-local2 (default deployment) a local repository for storing your docker images for use in production and
  • dockerhub a remote repository that points to dockerhub.

You may change the configuration by going to the admin tab and modifying virtual repositories.

Both docker-prod and docker-dev, by default, include dockerhub, so you can use artifactory as a pull-through cache either by using the –registry-mirror on your docker daemon, or by pulling tags prefixed by artifactory-docker-dev.system-domain.my-pcf.com. For example: artifactory-docker-dev.system-domain.my-pcf.com/busybox will pull busybox from artifactory, retrieving it from dockerhub if necessary.

Final Note: By default, the Pivotal tile will configure artifactory so that the standard repository configuration is deployed. This only creates or changes repositories if repositories of that name do not exist. If you do not want this behavior when you redeploy, you should simply change the admin password (which is a good practice). If you DO want this behavior, just change the credentials of the admin account during the deploy to admin/password.

Was this helpful?
What can we do to improve?
Create a pull request or raise an issue on the source for this page in GitHub