rusxakep/alpine repository overview

⁠github.com/rusxakep/docker-alpine

⁠About

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.

⁠Maintainer

• Dave Conroy⁠
• [Mikhail Baykov] (https://github.com/rusxakep⁠)

⁠Table of Contents

• About⁠
• Maintainer⁠
• Table of Contents⁠
• Prerequisites and Assumptions⁠
• Installation⁠
  • Build from Source⁠
  • Prebuilt Images⁠
    • Multi Archictecture⁠
• Configuration⁠
  • Quick Start⁠
  • Persistent Storage⁠
  • Environment Variables⁠
    • Container Options⁠
    • SMTP Options⁠
    • Zabbix Options⁠
    • Permissions⁠
  • Networking⁠
• Maintenance⁠
  • Shell Access⁠
• Support⁠
  • Usage⁠
  • Bugfixes⁠
  • Feature Requests⁠
  • Updates⁠
• License⁠
• References⁠

⁠Prerequisites and Assumptions

No prerequisites required

⁠Installation

⁠Build from Source

Clone this repository and build the image with docker build <arguments> (imagename) .

⁠Prebuilt Images

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

docker pull rusxakep/alpine:(imagetag)

The following image tags are available along with their tagged release based on what's written in the Changelog⁠:

⁠Multi Archictecture

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)

⁠Configuration

⁠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.

⁠Persistent Storage

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.

⁠Container Options

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.

⁠SMTP Options

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

⁠Zabbix Options

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.

⁠Permissions

⁠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.

bash docker exec -it (whatever your container name is) bash

⁠Support

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.

⁠Usage

• 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.

⁠Bugfixes

• Please, submit a Bug Report⁠ if something isn't working as expected. I'll do my best to issue a fix in short order.

⁠Feature Requests

• 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.

⁠Updates

• 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.

⁠License

MIT. See LICENSE⁠ for more details.

⁠References

• https://www.alpinelinux.org⁠