Install MongoDB Community on Debian using .tgz Tarball
On this page
MongoDB Atlas is a hosted MongoDB service option in the cloud which requires no installation overhead and offers a free tier to get started.
Use this tutorial to manually install MongoDB 6.0 Community
Edition on Debian Linux using a downloaded
This tutorial installs MongoDB 6.0 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
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.
When you use the
.tgz package to install the server, you need to
follow the mongosh installation instructions to
download and install mongosh separately.
MongoDB 6.0 Community Edition supports the following 64-bit Debian releases on x86_64 architecture:
Debian 11 "Bullseye"
Debian 10 "Buster"
MongoDB only supports the 64-bit versions of these platforms.
See Platform Support for more information.
Before deploying MongoDB in a production environment, consider the Production Notes document which offers performance considerations and configuration recommendations for production MongoDB deployments.
Install MongoDB Community Edition
Use the following command to install the dependencies required for the
Follow these steps to manually install MongoDB Community Edition from
Download the tarball.
After you have installed the required prerequisite packages, download
the MongoDB Community
tgz tarball from the following link:
In the Version dropdown, select the version of MongoDB to download.
In the Platform dropdown, select your operating system version and architecture.
In the Package dropdown, select tgz.
Ensure the binaries are in a directory listed in your
PATH environment variable.
The MongoDB binaries are in the
bin/ directory of the tarball.
You can either:
Copy the binaries into a directory listed in your
PATHvariable, such as
/path/to/the/mongodb-directory/with your installation directory as appropriate)
sudo cp /path/to/the/mongodb-directory/bin/* /usr/local/bin/
Create symbolic links to the binaries from a directory listed in your
PATHvariable, such as
/path/to/the/mongodb-directory/with your installation directory as appropriate):
sudo ln -s /path/to/the/mongodb-directory/bin/* /usr/local/bin/
Install the MongoDB Shell (
mongosh then use the MongoDB Shell
to connect to your deployment.
Download the package for the version of
mongosh you need from the
MongoDB Download Center and uncompress the package.
Run MongoDB Community Edition
- ulimit Considerations
- Most Unix-like operating systems limit the system resources that a
process may use. These limits may negatively impact MongoDB operation,
and should be adjusted. See UNIX
ulimitSettings for the recommended settings for your platform.
NoteStarting in MongoDB 4.4, a startup error is generated if the
ulimitvalue for number of open files is under
- By default, a MongoDB instance stores:
its data files in
its log files in
mkdir -p <directory>or
sudo mkdir -p <directory>depending on the user that will run MongoDB. (See your linux man pages for information on
sudo.)By default, MongoDB runs using the
mongodbuser account. If you change the user that runs the MongoDB process, you must also modify the permission to the
/var/log/mongodbdirectories to give this user access to these directories.To specify a different log file directory and data file directory, edit the
storage.dbPathsettings in the
/etc/mongod.conf. Ensure that the user running MongoDB has access to these directories.
Follow these steps to run MongoDB Community Edition. These instructions assume that you are using the default settings.
Create the data and log directories.
Create a directory where the MongoDB instance stores its data. For example:
sudo mkdir -p /var/lib/mongo
Create a directory where the MongoDB instance stores its log. For example:
sudo mkdir -p /var/log/mongodb
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:
sudo chown `whoami` /var/lib/mongo # Or substitute another user sudo chown `whoami` /var/log/mongodb # Or substitute another user
Verify that MongoDB has started successfully.
Verify that MongoDB has started successfully by
checking the process output for the following line in the
[initandlisten] waiting for connections on port 27017
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.
Begin using MongoDB.
mongosh session on the same host machine as the
mongod. You can run
without any command-line options to connect to a
mongod that is running on your localhost with default
For more information on connecting using
such as to connect to a
mongod instance running
on a different host and/or port, see the
To help you start using MongoDB, MongoDB provides Getting Started Guides in various driver editions. For the driver documentation, see Start Developing with MongoDB.
Localhost Binding by Default
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
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.
For more information on configuring