lanycrost/alpine repository overview

⁠Improved version of Alpine

⁠Introduction

Dockerfile to build an alpine⁠ container image.

• Currently tracking 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8 and edge
• s6 overlay⁠ enabled for PID 1 Init capabilities
• zabbix-agent⁠ based on 3.4.x compiled for individual container monitoring.
• Cron installed along with other tools (bash, curl, less, vim) for easier management.
• Ability to update User ID and Group ID Permissions for Development Purposes dyanmically.

⁠Table of Contents

• Introduction⁠
• Prerequisites⁠
• Installation⁠
• Quick Start⁠
• Configuration⁠
  • Data Volumes⁠
  • Environment Variables⁠
  • Networking⁠
• Maintenance⁠
  • Shell Access⁠
  • References⁠

⁠Prerequisites

No prequisites required

⁠Installation

Automated builds of the image are available on Docker Hub⁠ and is the recommended method of installation.

docker pull lanycrost/alpine:(imagetag)

The following image tags are available:

• 3.1 - Alpine 3.1
• 3.2 - Alpine 3.2
• 3.3 - Alpine 3.3
• 3.4 - Alpine 3.4
• 3.5 - Alpine 3.5
• 3.6 - Alpine 3.6
• 3.7 - Alpine 3.7
• 3.8 - Alpine 3.8
• edge - Alpine edge
• latest - Alpine 3.8

⁠Quick Start

Utilize this image as a base for further builds. By default it does not start the S6 Overlay system, but Bash. Please visit the s6 overlay repository⁠ for instructions on how to enable the S6 Init system when using this base or look at some of my other images which use this as a base.

⁠Configuration

⁠Data-Volumes

The following directories are used for configuration and can be mapped for persistent storage.

⁠Environment Variables

Below is the complete list of available options that can be used to customize your installation.

See The Official Zabbix Agent Documentation⁠ for information about the following Zabbix values

If you enable DEBUG_PERMISSIONS=TRUE all the users and groups have been modified in accordance with Environmental Variables will be displayed in output. e.g. If you add USER_NGINX=1000 it will reset the containers nginx user id from 82 to 1000 - Hint, also change the Group ID to your local development users UID & GID and avoid Docker permission issues when developing.

⁠Networking

The following ports are exposed.

⁠Debug Mode

When using this as a base image, create statements in your startup scripts to check for existence of DEBUG_MODE=TRUE and set various parameters in your applications to output more detail, enable debugging modes, and so on. In this base image it does the following:

• Sets zabbix-agent to output logs in verbosity

⁠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. alpine) bash

⁠Authors

• Khachatur Ashotyan⁠

⁠References

• https://www.alpinelinux.org⁠
• https://github.com/just-containers/s6-overlay⁠
• https://www.zabbix.com⁠