Supported tags and respective
Where to file issues:
the Docker Community
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
What is Tomcat?
Apache Tomcat (or simply Tomcat) is an open source web server and servlet container developed by the Apache Software Foundation (ASF). Tomcat implements the Java Servlet and the JavaServer Pages (JSP) specifications from Oracle, and provides a "pure Java" HTTP web server environment for Java code to run in. In the simplest config Tomcat runs in a single operating system process. The process runs a Java virtual machine (JVM). Every single HTTP request from a browser to Tomcat is processed in the Tomcat process in a separate thread.
Logo © Apache Software Fountation
How to use this image.
Run the default Tomcat server (
CMD ["catalina.sh", "run"]):
$ docker run -it --rm tomcat:8.0
You can test it by visiting
http://container-ip:8080 in a browser or, if you need access outside the host, on port 8888:
$ docker run -it --rm -p 8888:8080 tomcat:8.0
You can then go to
http://host-ip:8888 in a browser.
The default Tomcat environment in the image for versions 7 and 8 is:
CATALINA_BASE: /usr/local/tomcat CATALINA_HOME: /usr/local/tomcat CATALINA_TMPDIR: /usr/local/tomcat/temp JRE_HOME: /usr CLASSPATH: /usr/local/tomcat/bin/bootstrap.jar:/usr/local/tomcat/bin/tomcat-juli.jar
The default Tomcat environment in the image for version 6 is:
CATALINA_BASE: /usr/local/tomcat CATALINA_HOME: /usr/local/tomcat CATALINA_TMPDIR: /usr/local/tomcat/temp JRE_HOME: /usr CLASSPATH: /usr/local/tomcat/bin/bootstrap.jar
The configuration files are available in
/usr/local/tomcat/conf/. By default, no user is included in the "manager-gui" role required to operate the "/manager/html" web application. If you wish to use this app, you must define such a user in
tomcat 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).
View license information for the software contained in this image.
perhaps extending the image and setting JAVA_ALPINE_VERSION variable in yours?
Please do note that it is unadvisable the run this tomcat image as-is because it runs as root
this image is considered a base-image for your service should should be altered for your needs (e.g. add a tomcat user and set rights accordingly) before being production-ready
I'm running a SpringBoot App with Docker environment variables (
docker run -e sping.profiles.active=... ) inside a
tomcat:alpine based image.
Today, my docker client updated the OpenJDK base image from
8u131-jre-alpine and since then this environment mechanism does not work anymore, which seems to be an issue with 8u131.
Is there a better way to force tomcat-alpine to use the 8u121 tag than copying Tomcat's Dockerfile content and switching to openjdk:8u121-jdk-alpine by myself?
you can run a tomcat with no app.
only use command "docker run -d -v [mount volume] tomcat:latest"
can mount folder conf to out site. but remember that when you mount an out file will replace all file in folder mount in docker.
Hey everyone. Newcomer here. I'm trying to override the tomcat-user.xml file and restart the container after that. I tried mounting a volume to map a local folder to "/user/local/tomcat/conf", but I end up erasing all config files, thus causing the container to fail it's restart. Anyone found a way to do that? Thanks!
@saint31337 your comment is misleading, because this is simply not the config which is included with the image.
You can find out the actual one with
docker run --rm tomcat cat conf/tomcat-users.xml, and realize there is no default user or password for security reasons.
Login and passwd for tomcat 8.0
<user username="tomcat" password="secret" roles="manager-gui,manager-script,manager-jmx,manager-status,admin-script,admin-gui"/>
@migyecla only the environment variables supported by catalina.sh can be used as-is: http://svn.apache.org/repos/asf/tomcat/tc8.5.x/trunk/bin/catalina.sh. For configuring Tomcat further you have you have to push your own configuration files. See also: http://stackoverflow.com/a/23957805/4716370
How can I set up Tomcat manager login? I set TOMCAT_USERNAME and TOMCAT_PASSWORD but cant login to Tomcat Manager :-(
Hi. I have pulled the latest tomcat and successfully deployed. I can reach tomcat server, but the problem is it is using 1.7 as JVM. But my application is running on 1.8. When I try to deploy, it gives an error. Is it possible to change it 1.8?
I cannot find the catalina.out log file anywhere
where I can find it?