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 httpd?
The Apache HTTP Server, colloquially called Apache, is a Web server application notable for playing a key role in the initial growth of the World Wide Web. Originally based on the NCSA HTTPd server, development of Apache began in early 1995 after work on the NCSA code stalled. Apache quickly overtook NCSA HTTPd as the dominant HTTP server, and has remained the most popular HTTP server in use since April 1996.
How to use this image.
This image only contains Apache httpd with the defaults from upstream. There is no PHP installed, but it should not be hard to extend. On the other hand, if you just want PHP with Apache httpd see the PHP image and look at the
-apache tags. If you want to run a simple HTML server, add a simple Dockerfile to your project where
public-html/ is the directory containing all your HTML.
Dockerfile in your project
FROM httpd:2.4 COPY ./public-html/ /usr/local/apache2/htdocs/
Then, run the commands to build and run the Docker image:
$ docker build -t my-apache2 . $ docker run -dit --name my-running-app my-apache2
If you don’t want to include a
Dockerfile in your project, it is sufficient to do the following:
$ docker run -dit --name my-apache-app -v "$PWD":/usr/local/apache2/htdocs/ httpd:2.4
To customize the configuration of the httpd server, just
COPY your custom configuration in as
FROM httpd:2.4 COPY ./my-httpd.conf /usr/local/apache2/conf/httpd.conf
If you want to run your web traffic over SSL, the simplest setup is to
COPY or mount (
/usr/local/apache2/conf/ and then customize the
/usr/local/apache2/conf/httpd.conf by removing the comment from the line with
#Include conf/extra/httpd-ssl.conf. This config file will use the certificate files previously added and tell the daemon to also listen on port 443. Be sure to also add something like
-p 443:443 to your
docker run to forward the https port.
The previous steps should work well for development, but we recommend customizing your conf files for production, see httpd.apache.org for more information about SSL setup.
httpd 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.