The Apache HTTP Server Project is an effort to develop and maintain an open-source HTTP server for modern operating systems including UNIX and Windows NT. The goal of this project is to provide a secure, efficient and extensible server that provides HTTP services in sync with the current HTTP standards.

http://httpd.apache.org/

docker run --name apache bitnami/apache

apache:
  image: bitnami/apache

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

docker pull bitnami/apache: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.

docker pull bitnami/apache:[TAG]

If you wish, you can also build the image yourself.

git clone https://github.com/bitnami/bitnami-docker-apache.git
cd bitnami-docker-apache
docker build -t bitnami/apache .

This Apache image exposes a volume at /app. Content mounted here is served by the default catch-all virtual host. Mounting an empty directory here will copy the default content to your volume.

docker run --name apache -v /path/to/app:/app bitnami/apache

or using Docker Compose:

apache:
  image: bitnami/apache
  volumes:
    - /path/to/app:/app

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

docker run --name apache -P bitnami/apache

Run docker port to determine the random ports Docker assigned.

$ docker port apache
443/tcp -> 0.0.0.0:32768
80/tcp -> 0.0.0.0:32769

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

docker run -p 8080:80 -p 8443:443 bitnami/apache

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

The default httpd.conf includes virtual hosts placed in /bitnami/apache/conf/vhosts/*.conf. You can mount a directory at /bitnami/apache/conf/vhosts from your host containing your custom virtual hosts.

docker run -v /path/to/apache/vhosts:/bitnami/apache/conf/vhosts bitnami/apache

or using Docker Compose:

apache:
  image: bitnami/apache
  volumes:
    - /path/to/apache/vhosts:/bitnami/apache/conf/vhosts

This container looks for configuration in /bitnami/apache/conf. You can mount a directory there with your own configuration, or the default configuration will be copied to your directory if it is empty.

Run the Apache image, mounting a directory from your host.

docker run --name apache -v /path/to/apache/conf:/bitnami/apache/conf bitnami/apache

or using Docker Compose:

apache:
  image: bitnami/apache
  volumes:
    - /path/to/apache/conf:/bitnami/apache/conf

Edit the configuration on your host using your favorite editor.

vi /path/to/apache/conf/httpd.conf

After changing the configuration, restart your Apache container for changes to take effect.

docker restart apache

or using Docker Compose:

docker-compose restart apache

Note!

You can also reload the Apache configuration by sending the HUP signal to the container using the docker kill command.

docker kill -s HUP apache

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. Bitnami provides example virtual hosts for all of our runtime containers in /bitnami/apache/conf/vhosts/.

Further Reading:

• mod_proxy documentation

The Bitnami Apache Docker Image supports two different logging modes: logging to stdout, and logging to a file.

The default behavior is to log to stdout, as Docker expects. These will be collected by Docker, converted to JSON and stored in the host, to be accessible via the docker logs command.

docker logs apache

or using Docker Compose:

docker-compose logs apache

This method of logging has the downside of not being easy to manage. Without an easy way to rotate logs, they could grow exponentially and take up large amounts of disk space on your host.

To log to file, run the Apache image, mounting a directory from your host at /bitnami/apache/logs. This will instruct the container to send logs to your directory.

docker run --name apache -v /path/to/apache/logs:/bitnami/apache/logs bitnami/apache

or using Docker Compose:

apache:
  image: bitnami/apache
  volumes:
    - /path/to/apache/logs:/bitnami/apache/logs

To perform operations (e.g. logrotate) on the logs, mount the same directory in a container designed to operate on log files, such as logstash.

To backup your configuration and logs, follow these simple steps:

docker stop apache

or using Docker Compose:

docker-compose stop apache

We need to mount two volumes in a container we will use to create the backup: a directory on your host to store the backup in, and the volumes from the container we just stopped so we can access the data.

docker run --rm -v /path/to/backups:/backups --volumes-from apache busybox \
  cp -a /bitnami/apache /backups/latest

or using Docker Compose:

docker run --rm -v /path/to/backups:/backups --volumes-from `docker-compose ps -q apache` busybox \
  cp -a /bitnami/apache /backups/latest

Note! If you only need to backup configuration, you can change the first argument to cp to /bitnami/apache/conf.

Restoring a backup is as simple as mounting the backup as volumes in the container.

docker run -v /path/to/backups/latest/conf:/bitnami/apache/conf \
  -v /path/to/backups/latest/logs:/bitnami/apache/logs \
  bitnami/apache

or using Docker Compose:

apache:
  image: bitnami/apache
  volumes:
    - /path/to/backups/latest/conf:/bitnami/apache/conf
    - /path/to/backups/latest/logs:/bitnami/apache/logs

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

docker pull bitnami/apache:latest

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

Before continuing, you should backup your container's configuration and logs.

Follow the steps on creating a backup.

docker rm -v apache

or using Docker Compose:

docker-compose rm -v apache

Re-create your container from the new image, restoring your backup if necessary.

docker run --name apache bitnami/apache:latest

or using Docker Compose:

docker-compose start apache

This image is tested for expected runtime behavior, using the Bats testing framework. You can run the tests on your machine using the bats command.

bats test.sh

• /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.

We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.

If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:

• Host OS and version
• Docker version (docker version)
• Output of docker info
• Version of this container (echo $BITNAMI_APP_VERSION inside the container)
• The command you used to run the container, and any relevant output you saw (masking any sensitive information)

Copyright 2015 Bitnami

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

http://www.apache.org/licenses/LICENSE-2.0

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.