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 5.0 Community
Edition on SUSE Linux Enterprise Server (SLES) using a downloaded
This tutorial installs MongoDB 5.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
zypper 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 zypper Package Manager for instructions.
- MongoDB 5.0 Community Edition removes support for SLES12 on s390x
MongoDB 5.0 Community Edition supports the following 64-bit SUSE Linux Enterprise Server (SLES) releases on x86_64 architecture:
- SLES 15
- SLES 12
MongoDB only supports the 64-bit versions of these platforms.
To run MongoDB in Windows Subsystem for Linux (WSL), refer to the WSL documentation.
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
Follow these steps to manually install MongoDB Community Edition from
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.
- Click Download.
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/
mongosh then use the MongoDB Shell
to connect to your deployment.
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:
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 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.
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: