bitnami/tomcat Docker 镜像 - 轩辕镜像 | Docker 镜像高效稳定拉取服务

Bitnami Secure Image for Apache Tomcat

What is Apache Tomcat?

Apache Tomcat is an open-source web server designed to host and run Java-based web applications. It is a lightweight server with a good performance for applications running in production environments.

Overview of Apache Tomcat Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.

TL;DR

console
docker run --name tomcat REGISTRY_NAME/bitnami/tomcat:latest

You can find the default credentials and available configuration options in the Environment Variables section.

How to deploy Apache Apache Tomcat in Kubernetes?

Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami Apache Apache Tomcat Chart GitHub repository.

Why use a non-root container?

Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers in our docs.

Supported tags and respective Dockerfile links

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.

Get this image

The recommended way to get the Bitnami Apache Tomcat Docker Image is to pull the prebuilt image from the Docker Hub Registry.

console
docker pull REGISTRY_NAME/bitnami/tomcat:latest

To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.

console
docker pull REGISTRY_NAME/bitnami/tomcat:[TAG]

If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the docker build command. Remember to replace the APP, VERSION and OPERATING-SYSTEM path placeholders in the example command below with the correct values.

console
git clone [***]
cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t REGISTRY_NAME/bitnami/APP:latest .

Persisting your application

If you remove the container all your data and configurations will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.

For persistence you should mount a directory at the /bitnami path. If the mounted directory is empty, it will be initialized on the first run.

console
docker run -v /path/to/tomcat-persistence:/bitnami REGISTRY_NAME/bitnami/tomcat:latest

Alternatively, modify the docker-compose.yml file present in this repository:

yaml
services:
  tomcat:
  ...
    volumes:
      - /path/to/tomcat-persistence:/bitnami
  ...

NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID 1001.

Deploying web applications on Apache Tomcat

The /bitnami/tomcat/data directory is configured as the Apache Tomcat webapps deployment directory. At this location, you either copy a so-called exploded web application, i.e. non-compressed, or a compressed web application resource (.WAR) file and it will automatically be deployed by Apache Tomcat.

Additionally a helper symlink /app is present that points to the webapps deployment directory which enables us to deploy applications on a running Apache Tomcat instance by simply doing:

console
docker cp /path/to/app.war tomcat:/app

In case you want to create a custom image that already contains your application war file, you need to add it to the /opt/bitnami/tomcat/webapps folder. In the example below we create a forked image with an extra .war file.

Dockerfile
FROM REGISTRY_NAME/bitnami/tomcat:latest
COPY sample.war /opt/bitnami/tomcat/webapps

Note! You can also deploy web applications on a running Apache Tomcat instance using the Apache Tomcat management interface.

Further Reading:

• Apache Tomcat Web Application Deployment

Accessing your Apache Tomcat server from the host

To access your web server from your host machine you can ask Docker to map a random port on your host to port 8080 exposed in the container.

console
docker run --name tomcat -P REGISTRY_NAME/bitnami/tomcat:latest

Run docker port to determine the random ports Docker assigned.

console
$ docker port tomcat
8080/tcp -> 0.0.0.0:32768

You can also manually specify the ports you want forwarded from your host to the container.

console
docker run -p 8080:8080 REGISTRY_NAME/bitnami/tomcat:latest

Access your web server in the browser by navigating to http://localhost:8080.

Configuration

Environment variables

Customizable environment variables

Read-only environment variables

Creating a custom user

By default, a management user named manager is created and is not assigned a password. Passing the TOMCAT_PASSWORD environment variable when running the image for the first time will set the password of this user to the value of TOMCAT_PASSWORD.

Additionally you can specify a user name for the management user using the TOMCAT_USERNAME environment variable. When not specified, the TOMCAT_PASSWORD configuration is applied on the default user (manager).

Specifying Environment variables using Docker Compose

This requires a minor change to the docker-compose.yml file present in this repository:

yaml
services:
  tomcat:
  ...
    environment:
      - TOMCAT_USERNAME=my_user
      - TOMCAT_PASSWORD=my_password
  ...

Specifying Environment variables on the Docker command line

console
docker run --name tomcat \
  -e TOMCAT_USERNAME=my_user \
  -e TOMCAT_PASSWORD=my_password \
  REGISTRY_NAME/bitnami/tomcat:latest

Configuration files

During the initialization of the container, the default Apache Tomcat configuration files are modified with the basic options defined through environment variables. If you want to add more specific configuration options, you can always mount your own configuration files under /opt/bitnami/tomcat/conf/ to override the existing ones. Please note that those files should be writable by the system user of the container.

console
docker run --name tomcat -v /path/to/config/server.xml:/opt/bitnami/tomcat/conf/server.xml REGISTRY_NAME/bitnami/tomcat:latest

or using Docker Compose:

yaml
services:
  tomcat:
  ...
    volumes:
      - /path/to/config/server.xml:/opt/bitnami/tomcat/conf/server.xml
  ...

Refer to the Apache Tomcat configuration manual for the complete list of configuration options.

FIPS configuration in Bitnami Secure Images

The Bitnami Apache Tomcat Docker image from the Bitnami Secure Images catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:

• OPENSSL_FIPS: whether OpenSSL runs in FIPS mode or not. yes (default), no.

Logging

The Bitnami Apache Tomcat Docker image sends the container logs to the stdout. To view the logs:

console
docker logs tomcat

or using Docker Compose:

console
docker-compose logs tomcat

You can configure the containers logging driver using the --log-driver option if you wish to consume the container logs differently. In the default configuration docker uses the json-file driver.

Maintenance

Upgrade this image

Bitnami provides up-to-date versions of Apache Tomcat, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.

Step 1: Get the updated image

console
docker pull REGISTRY_NAME/bitnami/tomcat:latest

or if you're using Docker Compose, update the value of the image property to REGISTRY_NAME/bitnami/tomcat:latest.

Step 2: Stop and backup the currently running container

Stop the currently running container using the command

console
docker stop tomcat

or using Docker Compose:

console
docker-compose stop tomcat

Next, take a snapshot of the persistent volume /path/to/tomcat-persistence using:

console
rsync -a /path/to/tomcat-persistence /path/to/tomcat-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)

Step 3: Remove the currently running container

console
docker rm -v tomcat

or using Docker Compose:

console
docker-compose rm -v tomcat

Step 4: Run the new image

Re-create your container from the new image.

console
docker run --name tomcat REGISTRY_NAME/bitnami/tomcat:latest

or using Docker Compose:

console
docker-compose up tomcat

Notable Changes

Debian: 9.0.26-r0, 8.5.46-r0, 8.0.53-r382, 7.0.96-r50. Oracle: 9.0.24-ol-7-r35, 8.5.45-ol-7-r34, 8.0.53-ol-7-r426, 7.0.96-ol-7-r61

• Decrease the size of the container. The configuration logic is now based on Bash scripts in the rootfs/ folder.

9.0.13-r27 , 8.5.35-r26, 8.0.53-r131 & 7.0.92-r20

• The Apache Tomcat container has been migrated to a non-root user approach. Previously the container ran as the root user and the Apache Tomcat daemon was started as the tomcat user. From now on, both the container and the Apache Tomcat daemon run as user 1001. As a consequence, the data directory must be writable by that user. You can revert this behavior by changing USER 1001 to USER root in the Dockerfile.

8.0.35-r3

• TOMCAT_USER parameter has been renamed to TOMCAT_USERNAME.

8.0.35-r0

• All volumes have been merged at /bitnami/tomcat. Now you only need to mount a single volume at /bitnami/tomcat for persistence.
• The logs are always sent to the stdout and are no longer collected in the volume.

Using docker-compose.yaml

Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated Bitnami Helm chart.

If you detect any issue in the docker-compose.yaml file, feel free to report it or contribute with a fix by following our Contributing Guidelines.

License

Copyright © 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

<[***]>

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.