Before you proceed, see System Requirements for information on supported platforms, supported browsers, and other requirements.
Operating Systems and Platform Support
The following table lists the supported operating systems and the versions.
7.x, 8.x, 9.x
18.04, 20.04, 22.04
2016 or 2019
Amazon Linux 2023, Amazon Linux 2
Breaking Change Affecting RPM/Yum/Linux Archive Installations on Centos 7.x*
As part of our commitment to our customers to maintain the security and reliability of your JFrog Platform, from Artifactory version v7.43.x, JFrog Artifactory will officially run with JDK 17 and Tomcat 9.x on all installation types. Note that JDK 17 and Tomcat 9.x are not supported on all Centos 7.x versions.
CentOS 8.x Support
CentOS 8.x reached its end-of-life in December 2021. CentOS 8.x support for JFrog products has been deprecated by the end of June 2022.
The following table lists the supported platforms.
Installation on Kubernetes environments is through Helm Charts. Supported Helm version is Helm 3+.
From version 7.41.4, Artifactory supports installation on ARM64 architecture through Helm and Docker installations. You must set up an external database as the Artifactory database since Artifactory does not support the bundled database with the ARM64 installation. Artifactory installation pulls the ARM64 image automatically when you run the Helm or Docker installation on the ARM64 platform.
ARM64 support is also available for Xray, Distribution, and Insight. ARM64 support is not available for Pipelines.
Artifactory Database Requirements
You can configure your own database from the following list.
Artifactory supports the following databases.
Microsoft SQL Server
Artifactory HA requires an external database, which is fundamental to management of binaries and is also used to store cluster wide configuration files.
Since Artifactory HA contains multiple Artifactory cluster nodes, your database must be powerful enough to service all the nodes in the system. Moreover, your database must be able to support the maximum number of connections possible from all the Artifactory cluster nodes in your system.
If you are replicating your database you must ensure that at any given point in time all nodes see a consistent view of the database, regardless of which specific database instance they access. Eventual consistency, and write-behind database synchronization is not supported.
Artifactory File Store
The filestore is where binaries are physically stored.
Artifactory provides the following options to store binaries.
Local file system in which binaries are stored with redundancy using a binary provider, which manages synchronizing files between the cluster nodes according to the redundancy defined.
Cloud storageAmazon S3 and Google Cloud Storage
Network File System (NFS)
For detailed information, see Filestore Configuration.
While Artifactory can use a Networked File System (NFS) for its binary storage, you should do not install the application itself on an NFS. The Artifactory application needs very fast, reliable access to its configuration files. Any latency from an NFS will result in poor performance when the application fails to read these files. Therefore, install Artifactory on a local disk mounted directly to the host.
To use an NFS to store binaries, use the "file-system" binarystore.xml configuration with the additional "<baseDataDir>" setting.
Working with Very Large Storage
In most cases, our recommendation is for storage that is at least 3 times the total size of stored artifacts in order to accommodate system backups.
However, when working with a very large volume of artifacts, the recommendation may vary greatly according to the specific setup of your system. Therefore, when working with over 10 TB of stored artifacts, contact JFrog support, who will work with you to provide a recommendation for storage that is customized to your specific setup.
Allocated storage space may vary
Xray downloads and then deletes fetched artifacts after indexing. However, in order to have more parallel indexing processes, and thereby more temporary files at the same time would require more space.
This is especially applicable for large BLOBs such as Docker images.
Artifactory Network Ports
Artifactory uses external network ports to communicate with services outside Artifactory and internal networks to communicate with Artifactory and other JFrog Platform microservices.
External Network Ports
Artifactory uses the following external network ports by default.
Internal Network Ports
Artifactory uses the following internal network ports.
8040 and 8045
8048 and 9092
8082, 8046, 8047, 8049, and 8091
8061, and 8062
8071 and 8072
In addition, review the Docker requirements.
For Docker and Docker Compose installations, JFrog services require Docker 20.10.10 and above, and Docker Compose v1.24 and above to be installed on the machine on which you want to run on.
Stop and remove Artifactory using native Docker commands.
docker stop artifactory docker rm -f artifactory
Set the path to your current Artifactory home, and make sure the directory permissions are set correctly.
export ARTIFACTORY_HOME=<Mount Path to your current Artifactory data directory> chown -R 1030:1030 $ARTIFACTORY_HOME
Start the Artifactory container
docker run --name artifactory -v $ARTIFACTORY_HOME:/var/opt/jfrog/artifactory -d -p 8081:8081 -p 8082:8082 releases-docker.jfrog.io/jfrog/artifactory-<pro|oss|cpp-ce>:latest
Access Artifactory from your browser at:
For example, on your local machine:
Check Artifactory Log.
docker logs -f artifactory