Docker image for Diladele Web Safety ICAP Filter

Today we are announcing a Docker image for Diladele Web Safety ICAP Filter. It enables easy deployment of network filtering solutions using Docker technology.

This experimental version contains the following features:

  • Squid is compiled with SSL Bump support including the patch that fixes Chrome NET::ERR_CERT_INVALID error
  • Apache, Web Safety and Squid are deployed in the same container
  • Supervisor is used for coordination of all processes

In order to use Web Safety, please use the following instructions:

  1. Install Docker for your platform, for instructions please see
  2. Type command: docker search diladele. You should see the following image diladele/qlproxy:4.3.0.rc
  3. Start a container with the following command: docker run --name qlproxy -ti -p 8000:80 -p 3128:3128 diladele/qlproxy:4.3.0.rc. This commands will download the image and create a container with the name qlproxy and open port 8000 for Diladele Web Safety Administration Console and port 3128 for Squid.

Now you can connect with your browser to the box ip address or domain name on port 8000 and manage your deployment. For filtering, the clients should connect to port 3128.

To get the status of the container please use docker ps, for stopping of container – docker stop (container id). To remove the container – docker rm (container id).

Please be aware, this is an experimental image and was tested only on Ubuntu. The development of the project is done in

All feedback is greatly appreciated!

Diladele Dev Team

About sichent

This entry was posted in docker and tagged , , , . Bookmark the permalink.

2 Responses to Docker image for Diladele Web Safety ICAP Filter

  1. Cameron says:

    currently using at home. Works a treat running from a synology NAS with docker.

    Just checking if its possible to get reports emailed to you for various things? can’t seem to find the setting anywhere on the web console.

    Thanks for a great product.

    • sichent says:

      Hello Cameron, for now we do not have this functionality; but this is in plans for 4.4 or most probably for 4.5 (early summer 2016).

Comments are closed.