Sign inSign up

tonyskidmore/docker-tinyproxy

By tonyskidmore

Updated over 6 years ago

Image
0

141

tonyskidmore/docker-tinyproxy repository overview

Repositories

Why use this container?

Simply put, this container has been written with simplicity and security in mind.

Surprisingly, many community containers run unnecessarily with root privileges by default and don't provide help for dropping unneeded CAPabilities either. On top of that, overly complex shell scripts, monolithic designs and unofficial base images make it harder to verify the source among other issues.

To remedy the situation, these images have been written with security, simplicity and overall quality in mind.

RequirementStatusDetails
Don't run as rootNever run as root unless necessary.
Official base image
Drop extra CAPabilitiesSee docker-compose.yml
No default passwordsNo static default passwords. That would make the container insecure by default.
Support secrets-filesSupport providing e.g. passwords via files instead of environment variables.
Handle signals properly
Simple DockerfileNo overextending the container's responsibilities. And keep everything in the Dockerfile if reasonable.
Versioned tagsOffer versioned tags for stability.

Supported tags

See the Tags tab on Docker Hub for specifics. Basically you have:

  • The default latest tag that always has the latest changes.
  • Minor versioned tags (follow Semantic Versioning), e.g. 1.1 which would follow branch 1.1.x on GitHub.

Configuration

See Dockerfile and docker-compose.yml (https://github.com/kalaksi/docker-tinyproxy) for usable environment variables. Variables that are left empty will use default values.
If you need more customization, mount your own tinyproxy.conf to /etc/tinyproxy/tinyproxy.conf, otherwise, the default tinyproxy configuration file will be used and customized according to the environment variables.

Considerations for the native configuration file

This section doesn't apply to the current version (but is relevant for the future release)!
Note that you can't use /dev/stdout directly as the logfile: https://github.com/tinyproxy/tinyproxy/issues/43.
The proper way to get Tinyproxy to log to stdout is to disable LogFile and Syslog on the configuration so make sure that's how your file is set up.

Development

Contributing

See the repository on https://github.com/kalaksi/docker-tinyproxy. All kinds of contributions are welcome!

License

View license information for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

Tag summary

Content type

Image

Digest

Size

2.7 MB

Last updated

over 6 years ago

docker pull tonyskidmore/docker-tinyproxy