$ docker build -t httpd-playground .
$ docker run --name httpd-instance -dit -p 8080:80 httpd-playground
$ docker run --name httpd-instance --rm -p 8080:80 httpd-playground

** docker run: -d : To start a container in detached mode

** docker run: -i : Keep STDIN open even if not attached

** docker run: _-t : Allocate a pseudo-tty

** docker run: --rm : By default a container’s file system persists even after the container exits. This makes debugging a lot easier (since you can inspect the final state) and you retain all your data by default. But if you are running short-term foreground processes, these container file systems can really pile up. If instead you’d like Docker to automatically clean up the container and remove the file system when the container exits, you can add the --rm flag

vi /etc/hosts

...
127.0.0.1       localhost 
127.0.0.1       www.site1.domain.co.uk site1.domain.co.uk 
127.0.0.1       www.site2.domain.co.uk site2.domain.co.uk 
127.0.0.1       www.site3.domain.co.uk site3.domain.co.uk
127.0.0.1       www.site4.domain.co.uk site4.domain.co.uk
...

The following URLs should be valid:

• http://www.site1.domain.co.uk:8080
• http://www.site2.domain.co.uk:8080 (Basic Auth Applied)
• http://www.site3.domain.co.uk:8080 (Basic Auth Applied)
• http://www.site4.domain.co.uk:8080 (Basic Auth Applied)
• http://www.site5.domain.co.uk:8080
• http://www.site6.domain.co.uk:8080

$ docker exec -it httpd-instance /bin/bash

Apache home: /usr/local/apache2

ServerName localhost:80

Include conf/extra/httpd-vhosts.conf

Extra loaded modules:

DB

LoadModule authn_dbd_module modules/mod_authn_dbd.so
LoadModule dbd_module modules/mod_dbd.so

Proxy

LoadModule proxy_module modules/mod_proxy.
LoadModule proxy_http_module modules/mod_proxy_http.so

Listen -> https://httpd.apache.org/docs/current/bind.html

Password file creation:

$ htpasswd -c conf/auth/passwords user2

Add a user password:

$ htpasswd conf/auth/passwords user3

$ docker rmi $(docker images -f "dangling=true" -q)