Artifactory Repository - install and configure using Docker
Feature availability
Integration with Artifactory Repository is available only with Enterprise plans. For more information, see plans and pricing.
Before installing, review the prerequisites and the general instructions for installation using Docker.
This integration is useful to ensure a secure connection with your on-premise Artifactory Repository deployment.
For information about non-brokered integration with Artifactory Repository see Artifactory Repository setup. For information about brokered integration with Artifactory Container Registry see Snyk Broker -Container Registry Agent.
Configure Broker to be used for Artifactory Registry
To use the Broker client with an Artifactory Registry deployment, run docker pull snyk/broker:artifactory
. Refer to Artifactory Repository - environment variables for Snyk Broker for definitions of the environment variables.
Docker run commands to set up a Broker Client for Artifactory Repository
Multi-tenant settings for regions other than the default When you set up Snyk Broker for use in regions other than the default, additional environment variables with specific URLs are required. For the URLs and examples, see Regional hosting and data residency, Broker URLs.
Copy the following command to set up a fully configured Broker Client to use with Artifactory Registry. You can run the Docker container by providing the relevant configuration:
For an npm or Yarn integration, use the following command.
As an alternative to using the Docker run command, you can use a derived Docker image to set up the Broker Client integration. See Derived Docker images for the environment variables to override for the Artifactory integration.
Start the Broker Client container and verify the connection with Artifactory Repository
Paste the Broker Client configuration to start the Broker Client container.
You can check the status of the connection by refreshing the Artifactory Integration Settings page. When the connection is set up correctly, there is no connection error.
Last updated