Using the latest version?
JFrog Container Registry Guide


Skip to end of metadata
Go to start of metadata

Overview

This page outlines the system requirements for setting up and running JFrog Container Registry including:

  • Recommended and required hardware
  • Supported platforms
  • Java requirements
  • Supported browsers
  • Special requirements
Page Contents


Supported Platforms

JFrog Container Registry has been tested and verified on Linux, Windows (Vista and higher), Solaris and Mac OS X.

You should be able to run JFrog Container Registry on other platforms, but these have not been tested.


Java

JFrog Container Registry must run with JDK 8 (JDK 8 update 45 and above preferred) or JDK 11.

JFrog Container Registry fully supports running with OracleJDK and OpenJDK.

Latest JDK

You can download the latest JDK from the Oracle Java SE Download Site.

JAVA_HOME and JRE_HOME

Make sure your JAVA_HOME environment variable correctly points to your JDK 8 or 11 installation.

If you also have JRE_HOME defined in your system, this will take precedence over JAVA_HOME and therefore you need to either point JRE_HOME to your JDK installation, or remove the JRE_HOME definition.

JVM Memory Allocation

While not a strict requirement, we recommend that you modify the JVM memory parameters used to run JFrog Container Registry.

You should reserve at least 512MB for JFrog Container Registry, and the recommended values for JVM parameters are as follows:

Recommended JVM parameters

The larger your repository or number of concurrent users, the larger you need to make the -Xms and -Xmx values accordingly.

Recommended values are:

 -server -Xms512m -Xmx4g -Xss256k -XX:+UseG1GC

To set your JVM parameters according to your platform, please refer to the corresponding instructions for Linux, Solaris or Mac, or Windows


Browsers

JFrog Container Registry has been tested with the latest versions:

  • Google Chrome
  • Firefox
  • Internet Explorer
  • Safari

Recommended Hardware

The following table provides hardware recommendations for a single server machine:

Number of developersOS/JVMProcessor*Memory (RAM) for JVM HeapStorage
1 - 2064 bit4 cores4GBFast disk with free space that is at least 3 times the total size of stored artifacts
20 - 10064 bit4 cores8GBFast disk with free space that is at least 3 times the total size of stored artifacts
100 - 20064 bit8 cores (16 cores recommended)12GBFast disk with free space that is at least 3 times the total size of stored artifacts (backup SAN recommended)
200+64 bitPlease contact JFrog support for a recommended setup.

Build machine

For the purposes of this table, a build machine is considered equivalent to 10 developers

*Memory (RAM) for JVM Heap

This specifies the amount of memory that JFrog Container Registry requires from the JVM heap. The server machine should have enough additional memory to run the operating system and any other processes running on the machine. 

Special Requirements

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, please contact JFrog support who will work with you to provide a recommendation for storage that is customized to your specific setup.


Database Requirements

To avoid network latency issues when reading and writing artifacts data, we strongly recommend creating the database either on a machine that is network close (latency well below 1 ms) to the machine on which JFrog Container Registry is running (database engine and storage) with fast storage. This recommendation is critical when using fullDb (whereby files are served from database BLOBs) and the file system cache is small.

For supported databases and more details, please refer to Configuring the Database.


Servlet Containers

JFrog Container Registry should be run with its bundled Tomcat 8.0.36 servlet container.  

  • No labels