Dockerfile to build an alpine linux container image.
- Currently tracking 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.10, 3.11, 3.12, 3.13 and edge.
- s6 overlay enabled for PID 1 init capabilities.
- zabbix-agent for individual container monitoring.
- Cron installed along with other tools (bash, curl, less, logrotate, nano, vim) for easier management.
- MSMTP enabled to send mail from container to external SMTP server.
- Ability to update User ID and Group ID permissions for development purposes dynamically.
- About
- Maintainer
- Table of Contents
- Prerequisites and Assumptions
- Installation
- Configuration
- Maintenance
- Support
- License
- References
No prerequisites required
Clone this repository and build the image with docker build <arguments> (imagename) .
Builds of the image are available on Docker Hub and is the recommended method of installation.
docker pull tiredofit/alpine:(imagetag)The following image tags are available along with their tagged release based on what's written in the Changelog:
| Alpine version | Tag |
|---|---|
edge |
:edge |
3.13 |
:3.13 |
3.12 |
:3.12 |
3.11 |
:3.11 |
3.10 |
:3.10 |
3.9 |
:3.9 |
3.8 |
:3.8 |
3.7 |
:3.7 |
3.6 |
:3.6 |
3.5 |
:3.5 |
Images are built primarily for amd64 architecture, and may also include builds for arm/v6, arm/v7, arm64 and others. These variants are all unsupported. Consider sponsoring my work so that I can work with various hardware. To see if this image supports multiple architecures, type docker manifest (image):(tag)
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.
The following directories are used for configuration and can be mapped for persistent storage.
| Directory | Description |
|---|---|
/etc/zabbix/zabbix_agentd.conf.d/ |
Zabbix Agent configuration directory |
/assets/cron-custom |
Drop custom crontabs here |
Below is the complete list of available options that can be used to customize your installation.
| Parameter | Description | Default |
|---|---|---|
COLORIZE_OUTPUT |
Enable/Disable colorized console output | TRUE |
CONTAINER_LOG_LEVEL |
Control level of output of container INFO, WARN, NOTICE, DEBUG |
Default NOTICE |
DEBUG_MODE |
Enable debug mode | FALSE |
ENABLE_CRON |
Enable Cron | TRUE |
ENABLE_LOGROTATE |
Enable Logrotate (if Cron enabled) | TRUE |
ENABLE_SMTP |
Enable SMTP services | TRUE |
ENABLE_ZABBIX |
Enable Zabbix Agent | TRUE |
SKIP_SANITY_CHECK |
Disable container startup routine check | FALSE |
TIMEZONE |
Set Timezone | Etc/GMT |
If you wish to have this sends mail, set ENABLE_SMTP=TRUE and configure the following environment variables.
See the MSMTP Configuration Options for further information on options to configure MSMTP.
| Parameter | Description | Default |
|---|---|---|
SMTP_AUTO_FROM |
Add setting to support sending through Gmail SMTP | TRUE |
SMTP_HOST |
Hostname of SMTP Server | postfix-relay |
SMTP_PORT |
Port of SMTP Server | 25 |
SMTP_DOMAIN |
HELO Domain | docker |
SMTP_MAILDOMAIN |
Mail Domain From | local |
SMTP_AUTHENTICATION |
SMTP Authentication | none |
SMTP_USER |
Enable SMTP services | user |
SMTP_PASS |
Enable Zabbix Agent | password |
SMTP_TLS |
Use TLS | off |
SMTP_STARTTLS |
Start TLS from within session | off |
SMTP_TLSCERTCHECK |
Check remote certificate | off |
See The Official Zabbix Agent Documentation for information about the following Zabbix values.
| Parameter | Description | Default |
|---|---|---|
ZABBIX_LOGFILE |
Logfile location | /var/log/zabbix/zabbix_agentd.log |
ZABBIX_LOGFILESIZE |
Logfile size | 1 |
ZABBIX_DEBUGLEVEL |
Debug level | 1 |
ZABBIX_REMOTECOMMANDS_ALLOW |
Enable remote commands | * |
ZABBIX_REMOTECOMMANDS_DENY |
Deny remote commands | |
ZABBIX_REMOTECOMMANDS_LOG |
Enable remote commands Log (0/1) |
1 |
ZABBIX_SERVER |
Allow connections from Zabbix server IP | 0.0.0.0/0 |
ZABBIX_LISTEN_PORT |
Zabbix Agent listening port | 10050 |
ZABBIX_LISTEN_IP |
Zabbix Agent listening IP | 0.0.0.0 |
ZABBIX_START_AGENTS |
How many Zabbix Agents to start | 3 |
ZABBIX_SERVER_ACTIVE |
Server for active checks | zabbix-proxy |
ZABBIX_HOSTNAME |
Container hostname to report to server | docker |
ZABBIX_REFRESH_ACTIVE_CHECKS |
Seconds to refresh Active Checks | 120 |
ZABBIX_BUFFER_SEND |
Buffer Send | 5 |
ZABBIX_BUFFER_SIZE |
Buffer Size | 100 |
ZABBIX_MAXLINES_SECOND |
Max Lines Per Second | 20 |
ZABBIX_ALLOW_ROOT |
Allow running as root | 1 |
ZABBIX_USER |
Zabbix user to start as | zabbix |
If you enable DEBUG_PERMISSIONS=TRUE all the users and groups have been modified in accordance with
environment 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.
| Parameter | Description |
|---|---|
USER_<USERNAME> |
The user's UID in /etc/passwd will be modified with new UID |
GROUP_<GROUPNAME> |
The group's GID in /etc/group and /etc/passwd will be modified with new GID |
GROUP_ADD_<USERNAME> |
The username will be added in /etc/group after the group name defined |
The following ports are exposed.
| Port | Description |
|---|---|
10050 |
Zabbix Agent |
#@ 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
For debugging and maintenance purposes you may want access the containers shell.
bash docker exec -it (whatever your container name is) bash
These images were built to serve a specific need in a production environment and gradually have had more functionality added based on requests from the community.
- The Discussions board is a great place for working with the community on tips and tricks of using this image.
- Consider sponsoring me personalized support.
- Please, submit a Bug Report if something isn't working as expected. I'll do my best to issue a fix in short order.
- Feel free to submit a feature request, however there is no guarantee that it will be added, or at what timeline.
- Consider sponsoring me regarding development of features.
- Best effort to track upstream changes, More priority if I am actively using the image in a production environment.
- Consider sponsoring me for up to date releases.
MIT. See LICENSE for more details.