docker-maven

Note to Ident Engineering

amazoncorretto-11 has been modified to include git in the image. The image is published @ identsolutions/maven:3.6.1-amazoncorretto-11-git

To update maven/jdk, consider the following steps:

1. See if the original git repository as updates
2. Merge original git repository into this repo
3. Add git to new image by modifying the Dockerfile
4. cd into directory with the desired Dockerfile and run: docker build --tag maven:<change me 3.6.1>-amazoncorretto-<change me too 11>-git .
5. tag the docker image: docker tag maven:-amazoncorretto--git identsolutions/maven:-amazoncorretto--git
6. login into docker hub (docker id: identsolutions)
7. push docker image to docker hub: docker push identsolutions/maven:-amazoncorretto--git

Supported tags and respective Dockerfile links

All images are published under csanchez/maven and the ones extending Docker official images also under maven.

Linux Based Images

See Docker Hub maven and csanchez/maven for an updated list of tags

• openjdk-8
• openjdk-8-slim
• openjdk-11
• openjdk-11-slim
• openjdk-14
• openjdk-15
• adoptopenjdk-8
• adoptopenjdk-8-openj9
• adoptopenjdk-11
• adoptopenjdk-11-openj9
• ibmjava-8
• ibmjava-8-alpine
• amazoncorretto-8
• amazoncorretto-11
• azulzulu-11

Windows Based Images

See Docker Hub csanchez/maven for an updated list of tags

• openjdk-8-windows
• openjdk-8-windows-nanoserver
• openjdk-11-windows
• openjdk-11-windows-nanoserver
• openjdk-14-windows
• adoptopenjdk-8-openj9-windows
• adoptopenjdk-11-openj9-windows
• amazoncorretto-8-windows
• amazoncorretto-11-windows
• azulzulu-11-windows

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:

Linux

docker run -it --rm --name my-maven-project -v "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:3.3-jdk-8 mvn verify

Windows

docker run -it --rm --name my-maven-project -v "$(Get-Location)":C:/Src -w C:/Src csanchez/maven:3.3-jdk-8-windows mvn verify

Windows

docker run -it --rm --name my-maven-project -v "$(Get-Location)":C:/Src -w C:/Src maven:3.3-jdk-8-windows 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:

Linux

docker build --tag my_local_maven:3.6.0-jdk-8 .

Windows

docker build -f Dockerfile.windows --tag my_local_maven:3-jdk-9-windows --build-arg WINDOWS_DOCKER_TAG=1803 .

Multi-stage Builds

You can build your application with Maven and package it in an image that does not include Maven using multi-stage builds.

# build
FROM maven
WORKDIR /usr/src/app
COPY pom.xml .
RUN mvn -B -e -C -T 1C org.apache.maven.plugins:maven-dependency-plugin:3.1.1:go-offline
COPY . .
RUN mvn -B -e -o -T 1C verify

# package without maven
FROM openjdk
COPY --from=0 /usr/src/app/target/*.jar ./

Reusing the Maven local repository

The local Maven repository can be reused across containers by creating a volume and mounting it in /root/.m2.

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 package  

Packaging a local repository with the image

The $MAVEN_CONFIG dir (default to /root/.m2 or C:\Users\ContainerUser\.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/ (or C:\ProgramData\Maven\Reference) exists, and anything in that directory will be copied on container startup to $MAVEN_CONFIG.

To create a pre-packaged repository, create a pom.xml with the dependencies you need and use this in your Dockerfile. /usr/share/maven/ref/settings-docker.xml (C:\ProgramData\Maven\Reference\settings-docker.xml) is a settings file that changes the local repository to /usr/share/maven/ref/repository (C:\Programdata\Maven\Reference\repository), but you can use your own settings file as long as it uses /usr/share/maven/ref/repository (C:\ProgramData\Maven\Reference\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 tests dir

Running as non-root (not supported on Windows)

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

Image Variants

The maven images come in many flavors, each designed for a specific use case.

maven:<version>

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.

Building

Build with the usual

docker build -t maven .

Tests are written using bats for Linux images and pester for Windows images (requires Pester 4.x) under the tests dir.

Use the env var TAG to choose what image to run tests against.

Linux

TAG=jdk-11 bats tests

Windows

$env:TAG="jdk-11" ; Invoke-Pester -Path tests

or run all the tests with

Linux

for dir in $(/bin/ls -1 -d */ | grep -v 'tests\|windows'); do TAG=$(basename $dir) bats tests; done

Windows

Get-ChildItem -Path windows\* -File -Include "Dockerfile.windows-*" | ForEach-Object { Push-Location ; $env:TAG=$_.Name.Replace('Dockerfile.windows-', '') ; Invoke-Pester -Path tests ; Pop-Location }

Windows

Get-ChildItem -Path windows\* -File -Include "Dockerfile.windows-*" | ForEach-Object { Push-Location ; $env:TAG=$_.Name.Replace('Dockerfile.windows-', '') ; Invoke-Pester -Path tests ; Pop-Location }

Bats can be easily installed with brew install bats on OS X.

Note that you may first need to:

git submodule init
git submodule update

Pester comes with most modern Windows (Windows 10 and Windows Server 2019), but is an older version than required. You may need to follow this tutorial on upgrading Pester to 4.x.

Publishing to Docker Hub

In order to publish the images a PR needs to be opened against docker-library/official-images

For that we use publish.sh that runs generate-stackbrew-library.sh

License

View license information for the software contained in this image.

User Feedback

Issues

If you have any problems with or questions about this image, please contact us through a GitHub issue.

You can also reach many of the official image maintainers via the #docker-library IRC channel on Freenode.

Contributing

You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.

Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.