System requirements#

Your server must meet the requirements for hardware, software, security and network. Please review and verify that you have met all system requirements before beginning your installation.

Hardware requirements#

  • Physical server or virtual machine.

  • CPU: 2 x 64-bit, 2.8 GHz, 8.00 GT/s CPUs or better. Verify machine architecture.

  • Memory: minimum RAM size of 32 GB, or 16 GB RAM with 1600 MHz DDR3 installed, for a typical installation with 50 regular users. Verify memory requirements.

  • Storage: Recommended minimum of 650 GB for a mirror of or at least 1.5 TB for an air gapped environment. Additional space is recommended if Repository is used to store packages built by your organization. Verify storage requirements.

  • Internet access to download the files from, or a USB drive containing all of the files you need with alternate instructions for air gapped installations.

Software requirements#

Security requirements#

  • Root access or sudo capabilities. Verify root access and sudo privileges.

  • OPTIONAL: Ability to make IPTables modifications.

  • SELinux policy edit privileges.

    NOTE: SELinux does not have to be disabled for Repository operation.

Network requirements#

TCP ports are used as follows:

  • Inbound TCP 8080, 8443: Anaconda Enterprise 4 Repository.

  • Inbound TCP 22: SSH.

  • Outbound TCP 443:

  • Outbound TCP 25: SMTP.

  • Outbound TCP 389/636: LDAP(s).

You need your—Repository in the cloud—account username and password and the installation token provided to you by Anaconda at the time of purchase. If you did not receive your token, please contact your sales representative or our Professional Support Team.

Hardware verification#

Machine architecture#

Repository is built to operate only on 64-bit computers.

To verify that you have a 64-bit or x86_64 computer, in a terminal window, run:


This command displays what your system is: 32-bit “i686” or 64-bit “x86_64.”

Memory requirements#

You need a minimum RAM size of 32 GB, or 16 GB RAM with 1600 MHz DDR3.

In a terminal window, run:

free -m

This command returns the free memory size in MB.

Storage requirements#

To check your available disk space—hard drive or virtual environment size—use the built-in Linux df utility with the -h parameter for human readable format:

df -h

Software verification#

Other versions of the Linux environment#

Please contact us by filing a GitHub issue if you have problems with a version other than Redhat, CentOS or Ubuntu. Prompts may vary slightly depending on your version.

cURL access for Ubuntu users#

RedHat and CentOS Linux distributions have cURL pre-installed, but Ubuntu does not.

To verify cURL access, in a terminal window, run:

curl --version

If cURL is not found, Ubuntu users can use the Advanced Packaging Tool (APT) to get and install cURL:

sudo apt-get install curl

TIP: If you already have Miniconda or Anaconda installed, in all versions of Linux you can use the conda command:

conda install curl

MongoDB version 2.4+ installed#

MongoDB version 2.4 or higher must installed as root and running. Versions through 3.4 are supported. To check for the existence of MongoDB and its version number, in a terminal window, run:

mongod --version

If you get a “not found” message or if the MongoDB version is 2.3 or earlier, then install MongoDB 2.4 or higher using the official installation instructions. Remember to install as root with the sudo command.

MongoDB must always be running before Repository can be started.

To start MongoDB:

sudo service mongod start

To verify that MongoDB is running:

mongo --eval 'db.serverStatus().ok'

bzip2 is installed#

To check for the existence of bzip2 and its version number, in a terminal window, run:

bzip2 --version

Security verification#

Root access and sudo privileges#

The Repository installation process cannot be completed without root access.

To verify that you have sudo privileges, in a terminal window, run:

sudo -v

Enter your root password when prompted and press Enter.

If you receive a message like the following, contact your system administrator for root access:

Sorry, user [username] may not run sudo on [hostname].