Install MongoDB Community on Ubuntu using .tgz Tarball
On this page
Use this tutorial to manually install MongoDB 3.6 Community Edition on LTS (long-term support) releases of Ubuntu Linux using a downloaded
This tutorial installs MongoDB 3.6 Community Edition. To install a different version of MongoDB Community, use the version drop-down menu in the upper-left corner of this page to select the documentation for that version.
While MongoDB can be installed manually via a downloaded
.tgz tarball as described in this document, it is recommended to use the
apt package manager on your system to install MongoDB if possible. Using a package manager automatically installs all needed dependencies, provides an example
mongod.conf file to get you started, and simplifies future upgrade and maintenance tasks.
➤ See Install MongoDB using the apt Package Manager for instructions.
- MongoDB 3.6.4 Enterprise Edition removes support for Ubuntu 12.04 (“Precise”) on x86_64
MongoDB 3.6 Community Edition supports the following 64-bit Ubuntu LTS (long-term support) releases on x86_64 architecture:
- 16.04 LTS (“Xenial”)
- 14.04 LTS (“Trusty”)
MongoDB only supports the 64-bit versions of these platforms.
MongoDB 3.6 Community Edition on Ubuntu also supports the ARM64 architecture on select platforms.
See Supported Platforms for more information.
Windows Subsystem for Linux (WSL) - Unsupported
MongoDB does not support the Windows Subsystem for Linux (WSL).
Before deploying MongoDB in a production environment, consider the Production Notes document which offers performance considerations and configuration recommendations for production MongoDB deployments.
Use the following command to install the dependencies required for the MongoDB Community
Follow these steps to manually install MongoDB Community Edition from the
Download the tarball for your system from the MongoDB Download Center .
Using an archive manager program or the
tar command, extract the files.
For example, to extract from the terminal shell, you can use the following
If you downloaded a different MongoDB 3.6 point release, be sure to modify the command to reflect the correct
.tgz file name.
The MongoDB binaries are in the
To avoid having to specify the path to the MongoDB binaries, you can copy these binaries into a directory listed in your
PATH variable such as
- ulimit Considerations
- Most Unix-like operating systems limit the system resources that a session may use. These limits may negatively impact MongoDB operation. See UNIX ulimit Settings for more information.
- You can configure the MongoDB instance (such as the data directory and log directory specifications) using either the command-line options or a configuration file.
Follow these steps to run MongoDB Community Edition. These instructions assume that you are using the default settings.
Create a directory where the MongoDB instance stores its data. For example:
Create a directory where the MongoDB instance stores its log. For example:
The user that starts the MongoDB process must have read and write permission to these directories. For example, if you intend to run MongoDB as yourself:
Verify that MongoDB has started successfully by checking the process output for the following line in the log file
You may see non-critical warnings in the process output. As long as you see the log line shown above, you can safely ignore these warnings during your initial evaluation of MongoDB.
mongo shell on the same host machine as the
mongod. You can run the
mongo shell without any command-line options to connect to a
mongod that is running on your localhost with default port 27017:
By default, MongoDB launches with
bindIp set to
127.0.0.1, which binds to the localhost network interface. This means that the
mongod can only accept connections from clients that are running on the same machine. Remote clients will not be able to connect to the
mongod, and the
mongod will not be able to initialize a replica set unless this value is set to a valid network interface.
This value can be configured either:
Before binding to a non-localhost (e.g. publicly accessible) IP address, ensure you have secured your cluster from unauthorized access. For a complete list of security recommendations, see Security Checklist. At minimum, consider enabling authentication and hardening network infrastructure.