github.com/tiredofit/docker-unbound

About

Dockerfile to build an Unbound DNS Cache container image for quicker DNS lookups, mostly useful for mail servers, and other services that repeatedly rely on name resolution.

• This Container uses a customized Alpine Linux base which includes s6 overlay enabled for PID 1 Init capabilities, zabbix-agent for individual container monitoring, Cron also installed along with other tools (bash,curl, less, logrotate, nano) for easier management. It also supports sending to external SMTP servers..

Changelog

Maintainer

• Dave Conroy

Table of Contents

• Introduction
• Authors
• Table of Contents
• Prerequisites
• Installation
  • Quick Start
• Configuration
  • Data-Volumes
  • Environment Variables
  • Networking
• Maintenance
  • Shell Access
• References

Prerequisites and Assumptions

None.

Installation

Automated builds of the image are available on Docker Hub

docker pull hub.docker.com/tiredofit/unbound:(imagetag)

Builds of the image are also available on the Github Container Registry

docker pull ghcr.io/tiredofit/docker-tiredofit:(imagetag)

The following image tags are available:

• latest - Most recent release of Unbound w/ Alpine Linux

Quick Start

• The quickest way to get started is using docker-compose. See the examples folder for a working docker-compose.yml that can be modified for development or production use.

• Set various environment variables to understand the capabilities of this image.

• Map persistent storage for access to configuration and data files for backup.

Configuration

Persistent Storage

No files are required for persistent storage.

Environment Variables

Along with the Environment Variables from the Base image, below is the complete list of available options that can be used to customize your installation.

Networking

Maintenance

Shell Access

For debugging and maintenance purposes you may want access the containers shell.

docker exec -it (whatever your container name is e.g. unbound) bash

References

• https://unbound.net