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
Operating Systems - End of Support
As part of JFrog commitment to maintain the security and reliability of the JFrog Platform, from Q1-2024, JFrog Artifactory will officially run with Node.js 20.x on all installation types.
Node.js 20.x provided with Linux Archive/Debian/RPM installations (non-containerized distributions) is not supported on the following operating systems:
Hence, these operating systems are no longer supported for JFrog Artifactory.
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 the current server.
docker-compose -p rt stop
Extract the contents of the compressed archive and go to the extracted folder.
tar -xvf jfrog-artifactory-<pro|oss|cpp-ce>-<version>-compose.tar.gz cd artifactory-<pro|oss|cpp-ce>-<version>
Copy the contents of the
.envfile in the previous installation to the newly created
.envfile in this archive without copying the versions, as this affects the upgrade.
Run the config.sh script to setup folders with required ownership.
Manage Artifactory using native Docker Compose commands,
docker-compose -p rt <action> command.
# Starting from Artifactory 7.8.x, PostgreSQL needs to be started before starting the other services. # if PostgreSQL 9.6.11 running docker-compose -p rt-postgres -f docker-compose-postgres-9-6.11v.yaml up -d # if PostgreSQL 10.13 running docker-compose -p rt-postgres -f docker-compose-postgres-10-13v.yaml up -d # if PostgreSQL 12.3 running docker-compose -p rt-postgres -f docker-compose-postgres.yaml up -d docker-compose -p rt up -d docker-compose -p rt ps docker-compose -p rt down
Access Artifactory from your browser at:
http://SERVER_HOSTNAME:8082/ui/. For example, on your local machine:
Check Artifactory Log.
tail -f $ROOT_DATA_DIR/var/log/console.log