Comment on page
The base image for the bfren ecosystem, containing Alpine Linux and various helper executables.
x.x and x.x.x refer to the bfren image versions.
In addition, you can add
-betasuffixes to access development / test builds (see Docker Hub for further details).
If you need to build the image with a different timezone to the default ("Europe/London"), you can do so by setting the
TZARG, or by installing the
tzdatapackage. (Please note this is only possible if you are building the image yourself - otherwise you will need to use bf-tz.)
As well as the standard repositories, the edge repos are tagged with
@edgecomm. This means you can, for example, do
apk add curl@edgemainor
apk add php8@edgecommto add the edge versions of packages.
This image contains only one service:
cron, which is enabled by default. If you want to add scripts or executables to the cron you have two options.
The simplest way to add tasks to the cron in Alpine Linux is to place an executable file in one of the directories under
/etc/periodic/(remember to set the executable attribute in
$ ls /etc/periodic/
1min 15min daily hourly monthly weekly
If you want more control over your cron tasks you can create a normal crontab file:
$ head -n 1 /etc/crontabs/root
0 */8 * * * db-backup > /dev/null 2>&1
However, if you do this, remember you will be overriding the default file when your
/overlay/is copied over the image files, so you need to include the default directives if you don't want to break the cron further down the line.
All dynamic configuration files in the bfren ecosystem are built using esh, and the default location for those templates is