Tools for the Nuxeo Platform

Nuxeo DevContainer

Updated: May 27, 2021

The Nuxeo DevContainer allows you to speed up your development flow by bootstrapping, developing and deploying your Nuxeo Custom Application in a containerized environment and continuing using your preferred IDE.

This project is still under heavy development.


You need to install the following tools:

Before going further, you need to understand a few concepts and have a basic knowledge of the following tools and be comfortable on how to bootstrap a Nuxeo Custom Application:


The first step is to run our new bootstrap shell script that can create a custom project using Docker; without any other tool installed. For now, it is only designed to work on NIX system, but will be adapted to Windows:

/bin/bash -c "$(curl -fsSL my-first-project"

You will be asked for the required credentials for authenticated access to Nuxeo Online Service and (Nuxeo artifacts repository), the Studio project you want to bind, as well as a CLID for registering the Nuxeo instance that will be used.

During the generation process, you will be prompted for which version of the Nuxeo Platform you want to create your project for. You can use any version starts from 11.4, or the 2021.1 version.

The output of this execution, in your current working directory:

  • new empty custom plugin project my-first-project.
  • a script to help you start the containerized development environment as a shell:

The containerized development environment is a Docker image that contains Nuxeo recommended tools:

  • Development tooling: Git, NodeJS, NPM, Maven, Docker CLI, Docker Compose, Zulu OpenJDK8, Zulu OpenJDK11 and Nuxeo CLI.
  • Third parties CLIs: Kafka CLI and Mongo Shell, GCloud SDK, Azure CLI and AWS CLI.

It also adds into the image tmux and ohmyzsh that you will use for shell interactions.

Using our prebuilt startup scripts, the authentication for private registries of Maven, NPM and Docker against will be wired. The maven exec of the docker image will bind its repository in your local Maven repository, which will be created if missing. It also binds the container to your local Docker daemon to allow building and starting other containers from the development environment using the Docker in Docker pattern.

After bootstrap is finished, we strongly recommend executing “” to build your project once (maven package); and fill your local Docker registry with a first custom project Docker image that will be used afterwards in the docker-compose.yaml file.

Then, if you use Visual Studio Code as your IDE, you can directly open the project and you will be prompted to start the development environment as a devcontainer. It allows you to open your project inside a container and take advantage of Visual Studio Code's full feature set, including an in-container shell. Starting the devcontainer definition from Visual Studio Code will start the project's docker-compose file, and will run both the development environment and the custom application’s image.

For other IDEs, we recommend you to let the container’s shell (started with ./ script) open to run the necessary Nuxeo CLI commands described hereafter, or any other tools command.


  • Cannot jump to VSCode devcontainer right after executing the bootstrap script; as it starts the project docker-compose file and it requires a first build of the project Docker Image.
  • CLID is required to bootstrap, but it is a chicken and egg issue, as you need to start a server before having a CLID.
  • Prompting validation is very limited for now; for instance there is no check if your credentials have access, or not, to the Studio project you enter.

Usage with Visual Studio Code

Ensure your project root folder contains a .devcontainer folder, if not you can bootstrap it using nuxeo b devcontainer. Meanwhile, ensure Visual Studio Code Remote Development Extension is installed too.

VSCode: Open the devcontainer

Open your project root folder with Visual Code, and you must see a popup at the bottom right saying:
"Folder contains a Dev Container configuration file.", click on Open in Container button.

Visual Studio Code must restart and start both your Docker Image and the Dev Environment. More informations: Visual Code Remote - Containers.

After that step, we assume you execute commands from Visual Code with the integrated terminal.

VSCode: Build Your Project

Using the integrated terminal, everything has been configured and you only have to execute:

mvn package

Usage with Shell

For the next steps; we assume you are executing the commands within the development environment shell (using script); either from the devcontainer or from the start script.

Shell: Build Your Project

When building your project, the regular mvn package will build as well the Docker Image. It can be disabled by using -PskipDocker property.

During the Image build, your package dependencies will be resolved and might require a correct CLID if required dependencies are restricted.

NB: If you are not using the development environment; and your package depends on other restricted Nuxeo packages, you will need to pass NUXEO_CLID (format: NUXEO_CLID=XXXX—XXXX—) as an environment variable to build command.

[NUXEO_CLID=XXXX--XXXX--] mvn package

Shell: Start the Custom Application Image

The docker-compose generator creates a basic Docker Compose description file that starts your custom image and forward the container’s port 8080 to 8080 on localhost. You can update the docker-compose file to start a MongoDB, Elasticsearch, ...

docker-compose up

For development purposes, some Nuxeo server’s configurations can easily be set up in the compose file by creating a volume bound to container’s /etc/nuxeo/conf.d folder. During the container entry point execution, all file present in that directory are append to the final nuxeo.conf file (

    image: <your_custom_image>
      - my-local-conf.d:/etc/nuxeo/conf.d

Advanced Usage

Update/Fix Bootstrap or Shell variable Afterwards

If you need to update any value (like using a new CLID); all the secrets are stored in a dotenv file: .env.nuxeo-cli in your project root folder. Its content is straightforward and is injected as an environment variable within the development shell.

This file MUST not be committed, and must be kept as ignored. When several people are working on the same project; each developer must use his own file.

How to Generate Custom Application Docker Image in a Local Development Environment

Nuxeo CLI is still working as a standalone tool if installed locally.

Note that some updates have been done on the way Studio is bound to your Customer Java plugin. Studio project is now installed using Project’s package dependency to enforce application dependencies resolution at runtime time.

Otherwise, regular commands still work:

nuxeo b multi-module operation studio package
nuxeo studio link
nuxeo b docker-compose docker

The result is:

  • core module holding Java custom code.
  • package module building the project’s Nuxeo Package.
  • docker module distributing the application as a Docker container.
  • docker-compose file to start deploy and configure project.

NB: You can use nuxeo studio import to create a Constant Java class that contains your available Studio configuration.

How to Start Containerized Development Environment from any Project

You can create your own “” script in any project, following this content:

#!/usr/bin/env sh
set -e

CWD=$(realpath $(dirname $0))

exec docker run --rm -it \
  --privileged -v "/var/run/docker.sock:/var/run/docker.sock" \
  --mount "type=bind,source=${CWD},destination=/home/nuxeo/workspace/${PROJECT}" \
  --mount "type=volume,source=${PROJECT}_m2repo,destination=/home/nuxeo/.m2/repository" \

How to Start Containerized Online IDE Based on our Development Environment from any Project

This script starts an online IDE (Code Server) on top of the development environment. Using the initial bootstrap method, you just have to run script; otherwise you can create a similar script in any project, following this content:

B64_PROJECT=$(echo -n ${PROJECT} | md5)
CWD=$(realpath $(dirname $0))

exec docker run --rm -it \
  -p 8080:8080 \
  --privileged -v "/var/run/docker.sock:/var/run/docker.sock" \
  --mount "type=bind,source=${CWD},destination=/home/nuxeo/workspace/${PROJECT}" \
  --mount "type=volume,source=${PROJECT}_m2repo,destination=/home/nuxeo/.m2/repository" \
  --mount "type=volume,source=cs-settings-${B64_PROJECT},target=/home/nuxeo/.local/share/code-server/User" \

We'd love to hear your thoughts!

All fields required