aarch64/maven
Apache Maven is a software project management and comprehension tool.
991
The aarch64
organization is deprecated in favor of the more-specific arm64v8
organization, as per https://github.com/docker-library/official-images#architectures-other-than-amd64. Please adjust your usages accordingly.
Dockerfile
links** THESE IMAGES ARE VERY EXPERIMENTAL; THEY ARE PROVIDED ON A BEST-EFFORT BASIS WHILE docker-library/official-images#2289 IS STILL IN-PROGRESS (which is the first step towards proper multiarch images) **
** PLEASE DO NOT USE THEM FOR IMPORTANT THINGS **
This image is built from the source of the official image of the same name (maven
). Please see that image's description for links to the relevant Dockerfile
s.
If you are curious about specifically how this image differs, see the Jenkins Groovy DSL scripts in the tianon/jenkins-groovy
GitHub repository, which are responsible for creating the Jenkins jobs which build them.
Where to get help:
the Docker Community Forums, the Docker Community Slack, or Stack Overflow
Where to file issues:
https://github.com/carlossg/docker-maven/issues
Maintained by:
the Maven Project
Published image artifact details:
repo-info repo's repos/maven/
directory (history)
(image metadata, transfer size, etc)
Image updates:
official-images PRs with label library/maven
official-images repo's library/maven
file (history)
Source of this description:
docs repo's maven/
directory (history)
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
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.
FROM 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
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
:
$ docker run -it --rm --name my-maven-project -v "$PWD":/usr/src/mymaven -w /usr/src/mymaven maven:3.2-jdk-7 mvn clean install
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.
maven:onbuild
This image makes building derivative images easier. For most use cases, creating a Dockerfile
in the base of your project directory with the line FROM maven:onbuild
will be enough to create a stand-alone image for your project.
While the onbuild
variant is really useful for "getting off the ground running" (zero to Dockerized in a short period of time), it's not recommended for long-term usage within a project due to the lack of control over when the ONBUILD
triggers fire (see also docker/docker#5714
, docker/docker#8240
, docker/docker#11917
).
Once you've got a handle on how your project functions within Docker, you'll probably want to adjust your Dockerfile
to inherit from a non-onbuild
variant and copy the commands from the onbuild
variant Dockerfile
(moving the ONBUILD
lines to the end and removing the ONBUILD
keywords) into your own file so that you have tighter control over them and more transparency for yourself and others looking at your Dockerfile
as to what it does. This also makes it easier to add additional requirements as time goes on (such as installing more packages before performing the previously-ONBUILD
steps).
maven:alpine
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 git
or 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.
docker pull aarch64/maven