Supported tags and respective
Where to file issues:
the Maven Project
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
What is Maven?
Apache Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting and documentation from a central piece of information.
How to use this image
You can run a Maven project by using the Maven Docker image directly, passing a Maven command to
$ docker run -it --rm --name my-maven-project -v "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:3.3-jdk-8 mvn clean install
Building local Docker image (optional)
This is a base image that you can extend, so it has the bare minimum packages needed. If you add custom package(s) to the
Dockerfile, then you can build your local Docker image like this:
$ docker build --tag my_local_maven:3.5.2-jdk-8 .
Reusing the Maven local repository
The local Maven repository can be reused across containers by creating a volume and mounting it in
docker volume create --name maven-repo docker run -it -v maven-repo:/root/.m2 maven mvn archetype:generate # will download artifacts docker run -it -v maven-repo:/root/.m2 maven mvn archetype:generate # will reuse downloaded artifacts
Or you can just use your home .m2 cache directory that you share e.g. with your Eclipse/IDEA:
$ docker run -it --rm -v "$PWD":/usr/src/mymaven -v "$HOME/.m2":/root/.m2 -v "$PWD/target:/usr/src/mymaven/target" -w /usr/src/mymaven maven mvn clean package
Packaging a local repository with the image
$MAVEN_CONFIG dir (default to
/root/.m2) could be configured as a volume so anything copied there in a Dockerfile at build time is lost. For that reason the dir
/usr/share/maven/ref/ exists, and anything in that directory will be copied on container startup to
To create a pre-packaged repository, create a
pom.xml with the dependencies you need and use this in your
/usr/share/maven/ref/settings-docker.xml is a settings file that changes the local repository to
/usr/share/maven/ref/repository, but you can use your own settings file as long as it uses
/usr/share/maven/ref/repository as local repo.
COPY pom.xml /tmp/pom.xml RUN mvn -B -f /tmp/pom.xml -s /usr/share/maven/ref/settings-docker.xml dependency:resolve
To add your custom
settings.xml file to the image use
COPY settings.xml /usr/share/maven/ref/
For an example, check the
Running as non-root
Maven needs the user home to download artifacts to, and if the user does not exist in the image an extra
user.home Java property needs to be set.
For example, to run as user
1000 mounting the host' Maven repo
$ docker run -v ~/.m2:/var/maven/.m2 -ti --rm -u 1000 -e MAVEN_CONFIG=/var/maven/.m2 maven mvn -Duser.home=/var/maven archetype:generate
maven images come in many flavors, each designed for a specific use case.
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run
maven. Unless you are working in an environment where only the
maven image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
This image is based on the popular Alpine Linux project, available in the
alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
This variant is highly recommended when final image size being as small as possible is desired. The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn't have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
To minimize image size, it's uncommon for additional related tools (such as
bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the
alpine image description for examples of how to install packages if you are unfamiliar).
View license information for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.