Quickstart with Nuxeo Platform and Docker

Updated: June 14, 2024

This page details the fundamental commands you need to deploy your Nuxeo application in Docker in a development environment. It also provides a checklist when going on Production with Docker.

Starting With Docker in a Development Environment

We recommend to use the default Nuxeo Docker image in development mode (NUXEO_DEV=true), allowing you to hot reload your instance, and stop the server without shutting down the container.

Get and Run the LTS 2021 Docker Image

In terms of software, the only requirement to run the Nuxeo Docker image is Docker itself: Java, as well as all the external software, are integrated in the Docker image.

You should have access to our private Docker registry. If you are a Nuxeo client, please ask access to the Docker image through a support ticket. Once provided, follow these instructions. If not, contact your Nuxeo Administrator or Nuxeo sales representative to get access to this image.

Execute the following command line:

$ docker run --name nuxeo \
   -p 8080:8080 \
   -e NUXEO_DEV=true \
   -e NUXEO_PACKAGES="nuxeo-web-ui" \

Few notes:

  • You can add --rm option if your container should be deleted when shut down
  • To have different containers, change the name of your container

Start and Stop Nuxeo Instance

To start/stop your Nuxeo instance, use this command:

docker start/stop nuxeo

Remember that the nuxeo value corresponds to the name of the container you have set when running the container. To run different Nuxeo instances, simply run the container with a different name.

Use the nuxeoctl Script

nuxeoctl is made available in dev mode, and the container is not shut down when stopping the server in development mode:

docker exec nuxeo nuxeoctl stop

Install Packages

Either edit the NUXEO_PACKAGES values when running the container, or use the nuxeoctl script:

  1. docker exec nuxeo nuxeoctl stop
  2. docker exec nuxeo nuxeoctl mp-install <package_name>
  3. docker exec nuxeo nuxeoctl start

View Logs

By default, the server logs are printed to the standard output when running the Nuxeo container. If you've run the Nuxeo container with a different command than the default one, e.g. docker exec nuxeo nuxeoctl start, you can view the logs with:

docker logs -f nuxeo


docker exec  nuxeo tail -n500 -f /var/log/nuxeo/server.log

Access Nuxeo Server with Bash

If you need to explore the Nuxeo installation folder:

docker exec -it nuxeo bash

Going Further

For now, the entire Nuxeo stack, 3rd party software and data are hosted inside the same Docker container. This configuration won't allow you:

  • To test / repeat / rollback a Nuxeo upgrade because you'll be inevitably altering the database and files
  • To validate a "production-like" architecture:
    • Use an external database as MongoDB
    • Use an Elasticsearch cluster
    • Use Kafka to run the stream-related features

Let's review the key elements which should be taken into account when going into more complex architecture.

Build a Custom Dockerfile

First, it is important to customize the Nuxeo Docker Image by building a Docker image from the Nuxeo one to have immutable images configured at build time.

It is necessary then:

  • To build a custom Dockerfile
  • To install the Nuxeo packages and set your configuration properties on build time (Dockerfile), not runtime.

Once you have your Dockerfile is ready, you can quickly build the same image over and over, without having to take the time to do it manually. This is a much more efficient and standard method for creating new images than is committing changes to a pulled image.

Add Data Persistence

Persisting your data is interesting when you need to share resources between different containers. In the case of Nuxeo, this is interesting to store the data inside the same location.

→ More information here.

Manage Nuxeo Properties

It is a good practice to externalize the Nuxeo properties which should be added to the nuxeo.conf file. You can easily append the values set by default.

→ More information here.

Adjust Container Settings

Adapt the JAVA_OPTS value for your container

→ More information here.

Follow General Best Practices

Independently of the Nuxeo deployment (ZIP or Docker), you need to follow:

The setup best practices

The security recommendations

It is also important to ensure that you monitor correctly your Nuxeo instance.

Finally, when deploying your Nuxeo infrastructure in production, you will need to manage scaling.

To comply with those requirement, consider using Kubernetes to manage and automate your Nuxeo deployment (or Docker Swarm).