The LinuxServer.io team brings you another container release featuring:
- regular and timely application updates
- easy user mappings (PGID, PUID)
- custom base image with s6 overlay
- weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
- regular security updates
Find us at:
- Blog - all the things you can do with our containers including How-To guides, opinions and much more!
- Discord - realtime support / chat with the community and the team.
- Discourse - post on our community forum.
- Fleet - an online web interface which displays all of our maintained images.
- GitHub - view the source for all of our repositories.
- Open Collective - please consider helping us by either donating or contributing to our budget
Healthchecks is a watchdog for your cron jobs. It's a web server that listens for pings from your cron jobs, plus a web interface.
Our images support multiple architectures such as x86-64
, arm64
and armhf
. We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling linuxserver/healthchecks
should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
Architecture | Tag |
---|---|
x86-64 | amd64-latest |
arm64 | arm64v8-latest |
armhf | arm32v7-latest |
Here are some example snippets to help you get started creating a container.
docker create \
--name=healthchecks \
-e PUID=1000 \
-e PGID=1000 \
-e SITE_ROOT=<SITE_ROOT> \
-e SITE_NAME=<SITE_NAME> \
-e DEFAULT_FROM_EMAIL=<DEFAULT_FROM_EMAIL> \
-e EMAIL_HOST=<EMAIL_HOST> \
-e EMAIL_PORT=<EMAIL_PORT> \
-e EMAIL_HOST_USER=<EMAIL_HOST_USER> \
-e EMAIL_HOST_PASSWORD=<EMAIL_HOST_PASSWORD> \
-e EMAIL_USE_TLS=<True or False> \
-e ALLOWED_HOSTS=<ALLOWED_HOSTS> \
-e SUPERUSER_EMAIL=<SUPERUSER_EMAIL> \
-e SUPERUSER_PASSWORD=<SUPERUSER_PASSWORD> \
-p 8000:8000 \
-v <path to data on host>:/config \
--restart unless-stopped \
linuxserver/healthchecks
Compatible with docker-compose v2 schemas.
---
version: "2.1"
services:
healthchecks:
image: linuxserver/healthchecks
container_name: healthchecks
environment:
- PUID=1000
- PGID=1000
- SITE_ROOT=<SITE_ROOT>
- SITE_NAME=<SITE_NAME>
- DEFAULT_FROM_EMAIL=<DEFAULT_FROM_EMAIL>
- EMAIL_HOST=<EMAIL_HOST>
- EMAIL_PORT=<EMAIL_PORT>
- EMAIL_HOST_USER=<EMAIL_HOST_USER>
- EMAIL_HOST_PASSWORD=<EMAIL_HOST_PASSWORD>
- EMAIL_USE_TLS=<True or False>
- ALLOWED_HOSTS=<ALLOWED_HOSTS>
- SUPERUSER_EMAIL=<SUPERUSER_EMAIL>
- SUPERUSER_PASSWORD=<SUPERUSER_PASSWORD>
volumes:
- <path to data on host>:/config
ports:
- 8000:8000
restart: unless-stopped
Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal>
respectively. For example, -p 8080:80
would expose port 80
from inside the container to be accessible from the host's IP on port 8080
outside the container.
Parameter | Function |
---|---|
-p 8000 |
will map the container's port 8000 to port 8000 on the host |
-e PUID=1000 |
for UserID - see below for explanation |
-e PGID=1000 |
for GroupID - see below for explanation |
-e SITE_ROOT=<SITE_ROOT> |
The site's top-level URL (e.g., https://healthchecks.example.com) |
-e SITE_NAME=<SITE_NAME> |
The site's name (e.g., "Example Corp HealthChecks") |
-e DEFAULT_FROM_EMAIL=<DEFAULT_FROM_EMAIL> |
From email for alerts |
-e EMAIL_HOST=<EMAIL_HOST> |
SMTP host |
-e EMAIL_PORT=<EMAIL_PORT> |
SMTP port |
-e EMAIL_HOST_USER=<EMAIL_HOST_USER> |
SMTP user |
-e EMAIL_HOST_PASSWORD=<EMAIL_HOST_PASSWORD> |
SMTP password |
-e EMAIL_USE_TLS=<True or False> |
Use TLS for SMTP (True or False ) |
-e ALLOWED_HOSTS=<ALLOWED_HOSTS> |
array of valid hostnames for the server ["test.com","test2.com"] or "*" |
-e SUPERUSER_EMAIL=<SUPERUSER_EMAIL> |
Superuser email |
-e SUPERUSER_PASSWORD=<SUPERUSER_PASSWORD> |
Superuser password |
-v /config |
database and healthchecks config directory volume mapping |
You can set any environment variable from a file by using a special prepend FILE__
.
As an example:
-e FILE__PASSWORD=/run/secrets/mysecretpassword
Will set the environment variable PASSWORD
based on the contents of the /run/secrets/mysecretpassword
file.
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022
setting.
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.
When using volumes (-v
flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID
and group PGID
.
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance PUID=1000
and PGID=1000
, to find yours use id user
as below:
$ id username
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
ย
Access the WebUI at :8000. For more information, check out Healthchecks.
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) can be accessed via the dynamic badge above.
- Shell access whilst the container is running:
docker exec -it healthchecks /bin/bash
- To monitor the logs of the container in realtime:
docker logs -f healthchecks
- container version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' healthchecks
- image version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/healthchecks
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.
Below are the instructions for updating containers:
- Update the image:
docker pull linuxserver/healthchecks
- Stop the running container:
docker stop healthchecks
- Delete the container:
docker rm healthchecks
- Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your
/config
folder and settings will be preserved) - Start the new container:
docker start healthchecks
- You can also remove the old dangling images:
docker image prune
- Update all images:
docker-compose pull
- or update a single image:
docker-compose pull healthchecks
- or update a single image:
- Let compose update all containers as necessary:
docker-compose up -d
- or update a single container:
docker-compose up -d healthchecks
- or update a single container:
- You can also remove the old dangling images:
docker image prune
- Pull the latest image at its tag and replace it with the same env variables in one run:
docker run --rm \ -v /var/run/docker.sock:/var/run/docker.sock \ containrrr/watchtower \ --run-once healthchecks
Note: We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.
- You can also remove the old dangling images:
docker image prune
If you want to make local modifications to these images for development purposes or just to customize the logic:
git clone https://github.com/linuxserver/docker-healthchecks.git
cd docker-healthchecks
docker build \
--no-cache \
--pull \
-t linuxserver/healthchecks:latest .
The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static
docker run --rm --privileged multiarch/qemu-user-static:register --reset
Once registered you can define the dockerfile to use with -f Dockerfile.aarch64
.
- 19.12.19: - Rebasing to alpine 3.11.
- 31.10.19: - Add postgres client and fix config for CSRF.
- 23.10.19: - Allow to create superuser
- 28.06.19: - Rebasing to alpine 3.10.
- 12.04.19: - Rebase to Alpine 3.9.
- 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
- 14.02.19: - Adding mysql libs needed for using a database.
- 11.10.18: - adding pipeline logic and multi arching release
- 15.11.17: -
git pull
is now in Dockerfile so each tagged container contains the same code version - 17.10.17: - Fixed
local_settings.py
output - 27.09.17: - Initial Release.