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 7.0 Community
Edition on macOS using a downloaded
This tutorial installs MongoDB 7.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
brew 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 brew Package Manager for instructions.
MongoDB 7.0 Community Edition supports macOS 11 or later.
For more information, see Platform Support.
Before deploying MongoDB in a production environment, consider the Production Notes document which offers performance considerations and configuration recommendations for production MongoDB deployments.
To manually install MongoDB Community Edition from the
.tgz, select the tab
that corresponds with your Mac's processor and complete the following steps:
- 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
Follow these steps to run MongoDB Community Edition. These instructions assume that you are using the default settings.
Before you start MongoDB for the first time, you must create the
directory to which the
mongod process will write data.
For example, to create the
sudo mkdir -p ~/data/db
Ensure that the user account running
mongod has read
and write permissions for these two directories. If you are running
mongod as your own user account, and you just created
the two directories above, they should already accessible to your
user. Otherwise, you can use
chown to set ownership,
substituting the appropriate user:
sudo chown <user> ~/data/db sudo chown <user> ~/data/log/mongodb
To run MongoDB, run the
mongod process at the system
prompt, providing the two parameters
from above, and the
fork parameter to run
in the background. Alternatively, you may choose to store the values
fork, and many other parameters in a
mongod process at the system prompt,
providing the three necessary parameters directly on the
mongod --dbpath ~/data/db --logpath ~/data/log/mongodb/mongo.log --fork
mongod --config /usr/local/etc/mongod.conf
macOS Prevents mongod From Opening
macOS may prevent
mongod from running after installation. If
you receive a security error when starting
indicating that the developer could not be identified or verified,
do the following to grant
mongod access to run:
Open System Preferences
Select the Security and Privacy pane.
Under the General tab, click the button to the right of the message about
mongod, labelled either Open Anyway or Allow Anyway depending on your version of macOS.
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 the
default port of 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
not be able to initialize a replica set unless this value is set
to a valid network interface.
This value can be configured either: