jacobalberty / squid-docker

This is a squid (http://www.squid-cache.org/) docker image

squid-docker

This is a squid (http://www.squid-cache.org/) docker image

Notes about development

This container is under heavy development at the moment. I do use it in production but at this point it is tailored to my own use. I am actively working to get it generalized enough to be useful for other people. This section contains notes about planned changes and how things work (Or don't work).

Configuration files

At this point configuration files just go under /conf. I intend to make this a little more nested to allow some of the other features to be implemented.

Dependencies

This image contains all of the default authentication handlers and options from the debian defaults for squid. But it does not include all of those authentication handlers dependencies. I have plans for a special conf file just for the image that will allow you to add dependencies that are specific to your setup without having to modify the image itself.

Usage

Simply put your squid configuration in /conf with squid.conf located there as well.

squid-docker's Issues

permission errors?

Here are the different errors I get when trying out this container

WARNING: Cannot write log file: /dev/stderr
/dev/stderr: Permission denied
messages will be sent to 'stderr'.

018/10/25 20:15:07| helperOpenServers: Starting 5/32 'security_file_certgen' processes
(security_file_certgen): Uninitialized SSL certificate database directory: /var/spool/squid/ssl_db. To initialize, run "security_file_certgen -c -s /var/spool/squid/ssl_db".
(security_file_certgen): Uninitialized SSL certificate database directory: /var/spool/squid/ssl_db. To initialize, run "security_file_certgen -c -s /var/spool/squid/ssl_db".
(security_file_certgen): Uninitialized SSL certificate database directory: /var/spool/squid/ssl_db. To initialize, run "security_file_certgen -c -s /var/spool/squid/ssl_db".

2018/10/25 20:15:07| FATAL: Cannot open '/dev/stdout' for writing.
The parent directory must be writeable by the
user 'proxy', which is the cache_effective_user
set in squid.conf.
2018/10/25 20:15:07| Squid Cache (Version 4.2): Terminated abnormally.

Since this is the container with the latest squid, I would really like to get it to work. I am assuming since you use this heavily, you probably somehow made it around these problems. Can you please help?

access_log configuation

Was curious if you could profile a sample squid.conf specifically around log file configuration. I need to perform request logging and have this in a squid.conf ported from a Debian 10 VM:
access_log daemon:/var/log/squid/access.log
Seems it may be the reason I get this error on startup:

logfileHandleWrite: daemon:/var/log/squid/access.log: error writing ((32) Broken pipe)