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
Create a Dockerfile in your Maven project
FROM i386/maven:3.2-jdk-7-onbuild CMD ["do-something-with-built-packages"]
Put this file in the root of your project, next to the pom.xml.
This image includes multiple ONBUILD triggers which should be all you need to bootstrap. The build will
COPY . /usr/src/app and
RUN mvn install.
You can then build and run the image:
$ docker build -t my-maven . $ docker run -it --name my-maven-script my-maven
Run a single Maven command
For many simple projects, you may find it inconvenient to write a complete
Dockerfile. In such cases, 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 i386/maven:3.2-jdk-7 mvn clean install
i386/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 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).
This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run
i386/maven. Unless you are working in an environment where only the
i386/maven image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
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.