armhf/httpd repository overview

⁠DEPRECATED

The armhf⁠ organization is deprecated in favor of the more-specific arm32v7⁠ and arm32v6⁠ organizations, as per https://github.com/docker-library/official-images#architectures-other-than-amd64⁠. Please adjust your usages accordingly.

⁠Supported tags and respective Dockerfile links

** THESE IMAGES ARE VERY EXPERIMENTAL; THEY ARE PROVIDED ON A BEST-EFFORT BASIS WHILE docker-library/official-images#2289⁠ IS STILL IN-PROGRESS (which is the first step towards proper multiarch images) **

** PLEASE DO NOT USE THEM FOR IMPORTANT THINGS **

This image is built from the source of the official image of the same name (httpd)⁠. Please see that image's description for links to the relevant Dockerfiles.

If you are curious about specifically how this image differs, see the Jenkins Groovy DSL scripts in the tianon/jenkins-groovy GitHub repository⁠, which are responsible for creating the Jenkins jobs which build them.

⁠Quick reference

• Where to get help:
  the Docker Community Forums⁠, the Docker Community Slack⁠, or Stack Overflow⁠

• Where to file issues:
  https://github.com/docker-library/httpd/issues⁠

• Maintained by:
  the Docker Community⁠

• Published image artifact details:
  repo-info repo's repos/httpd/ directory⁠ (history⁠)
  (image metadata, transfer size, etc)

• Image updates:
  official-images PRs with label library/httpd⁠
  official-images repo's library/httpd file⁠ (history⁠)

• Source of this description:
  docs repo's httpd/ directory⁠ (history⁠)

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

⁠Create a 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

⁠Without a Dockerfile

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

⁠Configuration

To customize the configuration of the httpd server, just COPY your custom configuration in as /usr/local/apache2/conf/httpd.conf.

FROM httpd:2.4
COPY ./my-httpd.conf /usr/local/apache2/conf/httpd.conf

⁠SSL/HTTPS

If you want to run your web traffic over SSL, the simplest setup is to COPY or mount (-v) your server.crt and server.key into /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.

⁠License

View license information⁠ for the software contained in this image.