public_git/bitnami-containers
1
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-10-17 16:01:06 +02:00
Code Issues Projects Releases Wiki Activity

[bitnami/apache] Release 2.4.66-debian-12-r7 (#91528)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-03-12 11:11:18 +01:00
committed by GitHub
parent 0415a97844
commit 5b7f1e9f2a
2 changed files with 33 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/apache/2.4/debian-12/Dockerfile
+3 -3
View File
@@ -7,7 +7,7 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith"
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-02-27T00:21:44Z" \
org.opencontainers.image.created="2026-03-12T09:38:10Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/apache/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/apache" \
@@ -28,7 +28,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
COMPONENTS=( \
"render-template-1.0.9-162-linux-${OS_ARCH}-debian-12" \
"render-template-1.0.9-163-linux-${OS_ARCH}-debian-12" \
"apache-2.4.66-1-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
@@ -52,7 +52,7 @@ ENV APACHE_HTTPS_PORT_NUMBER="" \
APACHE_HTTP_PORT_NUMBER="" \
APP_VERSION="2.4.66" \
BITNAMI_APP_NAME="apache" \
IMAGE_REVISION="6" \
IMAGE_REVISION="7" \
PATH="/opt/bitnami/common/bin:/opt/bitnami/apache/bin:$PATH"
EXPOSE 8080 8443
bitnami/apache/README.md
+30 -30
View File
@@ -5,7 +5,7 @@
[Overview of Apache](https://httpd.apache.org/)
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.
## <a id="tl-dr"></a> TL;DR
## TL;DR
```console
docker run --name apache bitnami/apache:latest
@@ -13,7 +13,7 @@ docker run --name apache bitnami/apache:latest
You can find the available configuration options in the [Environment Variables](#environment-variables) section.
## <a id="why-use-bitnami-secure-images"></a> Why use Bitnami Secure Images?
## Why use Bitnami Secure Images?
Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images?
@@ -30,19 +30,19 @@ Each image comes with valuable security metadata. You can view the metadata in [
If you are looking for our previous generation of images based on Debian Linux, please see the [Bitnami Legacy registry](https://hub.docker.com/u/bitnamilegacy).
## <a id="how-to-deploy-in-kubernetes"></a> How to deploy Apache in Kubernetes?
## How to deploy Apache 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 Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/apache).
## <a id="why-non-root"></a> Why use a non-root container?
## 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](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-work-with-non-root-containers-index.html).
## <a id="supported-tags"></a> Supported tags and respective `Dockerfile` links
## 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](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html).
## <a id="get-this-image"></a> Get this image
## Get this image
The recommended way to get the Bitnami Apache Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/apache).
@@ -64,11 +64,11 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .
```
## <a id="using-`docker-compose.yaml`"></a> Using `docker-compose.yaml`
## 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](https://github.com/bitnami/charts/tree/main/bitnami/apache).
## <a id="hosting-a-static-website"></a> Hosting a static website
## Hosting a static website
The `/app` path is configured as the Apache [DocumentRoot](https://httpd.apache.org/docs/2.4/urlmapping.html#documentroot). Content mounted here is served by the default catch-all virtual host.
@@ -93,7 +93,7 @@ services:
> **NOTE** As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
## <a id="accessing-your-server-from-the-host"></a> Accessing your server from the host
## Accessing your 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 ports `8080` and `8443` exposed in the container.
@@ -117,11 +117,11 @@ docker run -p 8080:8080 -p 8443:8443 bitnami/apache:latest
Access your web server in the browser by navigating to `http://localhost:8080/`.
## <a id="configuration"></a> Configuration
## Configuration
The following section describes the supported environment variables
### <a id="environment-variables"></a> Environment variables
### Environment variables
The following tables list the main variables you can set.
@@ -180,7 +180,7 @@ docker run -d --name apache -p 80:8081 -p 443:443 \
bitnami/apache:latest
```
### <a id="adding-custom-virtual-hosts"></a> Adding custom virtual hosts
### Adding custom virtual hosts
The default `httpd.conf` includes virtual hosts placed in `/opt/bitnami/apache/conf/vhosts/`. You can mount a `my_vhost.conf` file containing your custom virtual hosts at the `/vhosts` folder.
@@ -223,7 +223,7 @@ services:
- /path/to/my_vhost.conf:/vhosts/my_vhost.conf:ro
```
### <a id="using-custom-ssl-certificates"></a> Using custom SSL certificates
### Using custom SSL certificates
*NOTE:* The steps below assume that you are using a custom domain name and that you have already configured the custom domain name to point to your server.
@@ -264,7 +264,7 @@ services:
- /path/to/apache-certs:/certs
```
### <a id="full-configuration"></a> Full configuration
### Full configuration
The image looks for configurations in `/opt/bitnami/apache/conf`. You can overwrite the `httpd.conf` file using your own custom configuration file.
@@ -289,13 +289,13 @@ services:
- /path/to/httpd.conf:/opt/bitnami/apache/conf/httpd.conf
```
### <a id="fips-configuration"></a> FIPS configuration in Bitnami Secure Images
### FIPS configuration in Bitnami Secure Images
The Bitnami Apache Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) 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`.
## <a id="reverse-proxy-to-other-containers"></a> Reverse proxy to other containers
## Reverse proxy to other containers
Apache can be used to reverse proxy to other containers using Docker's linking system. This is particularly useful if you want to serve dynamic content through an Apache frontend.
@@ -303,7 +303,7 @@ Apache can be used to reverse proxy to other containers using Docker's linking s
- [mod_proxy documentation](http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#forwardreverse)
## <a id="logging"></a> Logging
## Logging
The Bitnami Apache Docker image sends the container logs to the `stdout`. To view the logs:
@@ -319,11 +319,11 @@ docker-compose logs apache
You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
## <a id="customize-this-image"></a> Customize this image
## Customize this image
The Bitnami Apache Docker image is designed to be extended so it can be used as the base image for your custom web applications.
### <a id="extend-this-image"></a> Extend this image
### Extend this image
Before extending this image, please note there are certain configuration settings you can modify using the original image:
@@ -336,7 +336,7 @@ If your desired customizations cannot be covered using the methods mentioned abo
```Dockerfile
FROM bitnami/apache
### <a id="put-your-customizations-below"></a> Put your customizations below
### Put your customizations below
...
```
@@ -350,22 +350,22 @@ Here is an example of extending the image with the following modifications:
```Dockerfile
FROM bitnami/apache
### <a id="change-user-to-perform-privileged-actions"></a> Change user to perform privileged actions
### Change user to perform privileged actions
USER 0
### <a id="install-'vim'"></a> Install 'vim'
### Install 'vim'
RUN install_packages vim
### <a id="revert-to-the-original-non-root-user"></a> Revert to the original non-root user
### Revert to the original non-root user
USER 1001
### <a id="enable-mod_ratelimit-module"></a> Enable mod_ratelimit module
### Enable mod_ratelimit module
RUN sed -i -r 's/#LoadModule ratelimit_module/LoadModule ratelimit_module/' /opt/bitnami/apache/conf/httpd.conf
### <a id="modify-the-ports-used-by-by-default"></a> Modify the ports used by Apache by default
## <a id="it-is-also-possible-to-change-these-environment-variables-at-runtime"></a> It is also possible to change these environment variables at runtime
### Modify the ports used by Apache by default
## It is also possible to change these environment variables at runtime
ENV APACHE_HTTP_PORT_NUMBER=8181
EXPOSE 8181 8443
### <a id="modify-the-default-container-user"></a> Modify the default container user
### Modify the default container user
USER 1002
```
@@ -403,11 +403,11 @@ volumes:
driver: local
```
## <a id="useful-links"></a> Useful Links
## Useful Links
- [Create An AMP Development Environment With Bitnami Containers](https://docs.bitnami.com/containers/how-to/create-amp-environment-containers/)
## <a id="notable-changes"></a> Notable Changes
## Notable Changes
### 2.4.64-debian-12-r2
@@ -461,7 +461,7 @@ volumes:
- The `/app` directory is no longer exported as a volume. This caused problems when building on top of the image, since changes in the volume are not persisted between Dockerfile `RUN` instructions. To keep the previous behavior (so that you can mount the volume in another container), create the container with the `-v /app` option.
## <a id="license"></a> License
## License
Copyright &copy; 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.