Scripts to dockerize TinyProxy.
The base image is the fundamental part for tinyproxy docker image.
It is using the latest version of tinyproxy to install and doing automatically image cleanup, so that it only occupies like 400~500MB.
$ docker build -f base.dockerfile -t base .Assume your baseimage named "tinyproxy-base"(change it in tinyproxy-dox.dockerfile), use below command to build the final tinyproxy image.
$ docker build -f tinyproxy-dox.dockerfile -t tinyproxy .Q1. Why splitting as two dockerfiles?
A: Because it costs relatively long time to preparing the building environment and executing the build with recent release.
So splitting into two files will help you focus on your own business and logics in tinyproxy-dox.dockerfile and entrypoint.sh, they are more relative to businesses.
Q2. Why using a entrypoint shell?
A: Using entrypoing.sh helps you organize your building flow and extract the common parameters you might need to customize. It offers good comments and should be clear enough for later customization.
Q3. How to test tinyproxy?
A. Assuming you are in the running container of tinyproxy docker image, then by executing the following command you could check the response.
curl --proxy localhost:8888 --proxy-user username:password -k https://www.google.comBe noted that "Allow xxx.xxx.xxx.xxx" only works with "BasicAuth" in tinyproxy.conf, so setup in onetime might help to resolve the authorization issue.
Tinyproxy Homepage https://tinyproxy.github.io/
Tinyproxy Github Repo https://github.com/tinyproxy/tinyproxy
How to setup a simple proxy server with tinyproxy (Debian 10 Buster) https://nxnjz.net/2019/10/how-to-setup-a-simple-proxy-server-with-tinyproxy-debian-10-buster/