Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


Available as:

Image inheritance


See also tozd/meteor-testing.


  • ubuntu-xenial-*: Meteor versions using Ubuntu 16.04 LTS (Xenial) as base
  • ubuntu-bionic-*: Meteor versions using Ubuntu 18.04 LTS (Bionic) as base
  • ubuntu-focal-*: Meteor versions using Ubuntu 20.04 LTS (Focal) as base
  • ubuntu-jammy-*: Meteor versions using Ubuntu 22.04 LTS (Jammy) as base

Some versions are not build because they have issues.


  • /var/log/meteor: Log files.


  • ROOT_URL: Used by Meteor to construct absolute URLs. It should not contain a trailing /. Example:
  • MAIL_URL: Used to configure e-mail server. Example: smtp://user:password@mailhost:port/.
  • METEOR_SETTINGS: JSON string of your Meteor settings.
  • MONGO_URL: MongoDB database URL. Example: mongodb://mongodb/meteor.
  • MONGO_OPLOG_URL: MongoDB database oplog URL. Example: mongodb://mongodb/local.
  • LOG_TO_STDOUT: If set to 1 output logs to stdout (retrievable using docker logs) instead of log volumes.


  • 3000/tcp: HTTP port on which Meteor app listens.


Image which can serve as a base Docker image for dockerizing Meteor applications.

In the root directory of your Meteor application (the one with .meteor directory) create a Dockerfile file with the following content:

FROM<Meteor version>

For example:


Meteor version should be the version of Meteor you want to use to build your Meteor application. By using a fixed version of Meteor you achieve reproducible builds of your application. You can also specify the Ubuntu LTS version you want to use as the basis of your Docker image. In the example above, this is Ubuntu Focal. See all available tags on Docker Hub.

And your Meteor application is dockerized. To optimize image building, especially if you are building the image from a directory where you are also developing the application, add .dockerignore file with something like:


The intended use of this image is that it is run alongside the tozd/meteor-mongodb image for MongoDB database for your Meteor application. You will probably want a HTTP reverse proxy in front. You can use tozd/docker-nginx-proxy image which provides nginx configured as a reverse proxy with automatic SSL support provided by Let's encrypt.

When running Docker image with your Meteor application, you should configure at least ROOT_URL, MONGO_URL, and MONGO_OPLOG_URL environment variables.

You can specify those environment variables when running an image, but you can also export them from the script file volume mounted under /etc/service/meteor/run.config.

Example of a run.config file:


export MONGO_URL="mongodb://meteor:${MONGODB_CREATE_PWD}@mongodb/meteor"
export MONGO_OPLOG_URL="mongodb://oplogger:${MONGODB_OPLOGGER_PWD}@mongodb/local?authSource=admin"

Only export lines are necessary for this image, but others are used by tozd/meteor-mongodb image. You can export also other environment variables.

When you are extending this image, you can add a script /etc/service/meteor/run.initialization which will be run at a container startup, after the container is initialized, but before the Meteor application is run.

If you have to do anything to the base Docker image, before your Meteor application starts building (e.g., installing an Ubuntu package), add a file to the root of your Meteor application and it will be run before the build.

When LOG_TO_STDOUT is set to 1, Docker image logs output to stdout and stderr. All stdout output is JSON.

Testing image

For testing Meteor applications, use tozd/meteor-testing Docker image instead.

GitHub mirror

There is also a read-only GitHub mirror available, if you need to fork the project there.