docker-documentation/images/docker-healthchecks.md

160 wiersze
6.4 KiB
Markdown
Czysty Zwykły widok Historia

2019-09-29 12:37:54 +00:00
# [linuxserver/healthchecks](https://github.com/linuxserver/docker-healthchecks)
2019-02-10 13:38:37 +00:00
2019-09-29 12:37:54 +00:00
[![GitHub Release](https://img.shields.io/github/release/linuxserver/docker-healthchecks.svg?style=flat-square&color=E68523)](https://github.com/linuxserver/docker-healthchecks/releases)
[![MicroBadger Layers](https://img.shields.io/microbadger/layers/linuxserver/healthchecks.svg?style=flat-square&color=E68523)](https://microbadger.com/images/linuxserver/healthchecks "Get your own version badge on microbadger.com")
[![MicroBadger Size](https://img.shields.io/microbadger/image-size/linuxserver/healthchecks.svg?style=flat-square&color=E68523)](https://microbadger.com/images/linuxserver/healthchecks "Get your own version badge on microbadger.com")
[![Docker Pulls](https://img.shields.io/docker/pulls/linuxserver/healthchecks.svg?style=flat-square&color=E68523)](https://hub.docker.com/r/linuxserver/healthchecks)
[![Docker Stars](https://img.shields.io/docker/stars/linuxserver/healthchecks.svg?style=flat-square&color=E68523)](https://hub.docker.com/r/linuxserver/healthchecks)
[![Build Status](https://ci.linuxserver.io/view/all/job/Docker-Pipeline-Builders/job/docker-healthchecks/job/master/badge/icon?style=flat-square)](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-healthchecks/job/master/)
[![](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/healthchecks/latest/badge.svg)](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/healthchecks/latest/index.html)
2019-02-10 13:38:37 +00:00
[Healthchecks](https://github.com/healthchecks/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.
2019-09-29 12:37:54 +00:00
2019-02-10 13:38:37 +00:00
## Supported Architectures
2019-09-01 12:38:04 +00:00
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](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
2019-02-10 13:38:37 +00:00
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 |
2019-09-29 12:37:54 +00:00
| :----: | --- |
2019-02-10 13:38:37 +00:00
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
2019-03-24 19:41:19 +00:00
| armhf | arm32v7-latest |
2019-02-10 13:38:37 +00:00
2019-09-29 12:37:54 +00:00
2019-02-10 13:38:37 +00:00
## Usage
Here are some example snippets to help you get started creating a container from this image.
### docker
2019-09-29 12:37:54 +00:00
```
2019-02-10 13:38:37 +00:00
docker create \
--name=healthchecks \
2019-03-03 13:37:46 +00:00
-e PUID=1000 \
-e PGID=1000 \
2019-02-10 13:38:37 +00:00
-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=<EMAIL_USE_TLS> \
-e ALLOWED_HOSTS=<ALLOWED_HOSTS> \
-p 8000:8000 \
-v <path to data>:/config \
--restart unless-stopped \
linuxserver/healthchecks
```
2019-09-29 12:37:54 +00:00
2019-02-10 13:38:37 +00:00
### docker-compose
Compatible with docker-compose v2 schemas.
```yaml
---
version: "2"
services:
healthchecks:
image: linuxserver/healthchecks
container_name: healthchecks
environment:
2019-03-03 13:37:46 +00:00
- PUID=1000
- PGID=1000
2019-02-10 13:38:37 +00:00
- 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=<EMAIL_USE_TLS>
- ALLOWED_HOSTS=<ALLOWED_HOSTS>
volumes:
- <path to data>:/config
ports:
- 8000:8000
restart: unless-stopped
```
## Parameters
2019-09-29 12:37:54 +00:00
Docker 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.
2019-02-10 13:38:37 +00:00
2019-09-29 12:37:54 +00:00
### Ports (`-p`)
2019-02-10 13:38:37 +00:00
| Parameter | Function |
2019-09-29 12:37:54 +00:00
| :----: | --- |
2019-02-10 13:38:37 +00:00
| `8000` | will map the container's port 8000 to port 8000 on the host |
2019-09-29 12:37:54 +00:00
### Environment Variables (`-e`)
2019-02-10 13:38:37 +00:00
| Env | Function |
2019-09-29 12:37:54 +00:00
| :----: | --- |
2019-03-03 13:37:46 +00:00
| `PUID=1000` | for UserID - see below for explanation |
| `PGID=1000` | for GroupID - see below for explanation |
2019-09-29 12:37:54 +00:00
| `SITE_ROOT=<SITE_ROOT>` | The site's domain (i.e., example.com) |
2019-02-10 13:38:37 +00:00
| `SITE_NAME=<SITE_NAME>` | The site's name |
| `DEFAULT_FROM_EMAIL=<DEFAULT_FROM_EMAIL>` | From email for alerts |
| `EMAIL_HOST=<EMAIL_HOST>` | SMTP host |
| `EMAIL_PORT=<EMAIL_PORT>` | SMTP port |
| `EMAIL_HOST_USER=<EMAIL_HOST_USER>` | SMTP user |
| `EMAIL_HOST_PASSWORD=<EMAIL_HOST_PASSWORD>` | SMTP password |
| `EMAIL_USE_TLS=<EMAIL_USE_TLS>` | Use TLS for SMTP |
2019-09-29 12:37:54 +00:00
| `ALLOWED_HOSTS=<ALLOWED_HOSTS>` | array of valid hostnames for the server ["test.com","test2.com"] |
2019-02-10 13:38:37 +00:00
2019-09-29 12:37:54 +00:00
### Volume Mappings (`-v`)
2019-02-10 13:38:37 +00:00
| Volume | Function |
2019-09-29 12:37:54 +00:00
| :----: | --- |
2019-02-10 13:38:37 +00:00
| `/config` | database and healthchecks config |
2019-09-29 12:37:54 +00:00
2019-02-10 13:38:37 +00:00
## User / Group Identifiers
2019-09-29 12:37:54 +00:00
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`.
2019-02-10 13:38:37 +00:00
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
2019-03-03 13:37:46 +00:00
In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
2019-02-10 13:38:37 +00:00
2019-09-29 12:37:54 +00:00
```
2019-02-10 13:38:37 +00:00
$ id username
2019-03-03 13:37:46 +00:00
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
2019-02-10 13:38:37 +00:00
```
## Application Setup
2019-09-29 12:37:54 +00:00
Access the WebUI at <your-ip>:8000. For more information, check out [Healthchecks](https://github.com/healthchecks/healthchecks).
2019-02-10 13:38:37 +00:00
## Support Info
2019-09-01 12:38:04 +00:00
* Shell access whilst the container is running:
2019-02-10 13:38:37 +00:00
* `docker exec -it healthchecks /bin/bash`
2019-09-01 12:38:04 +00:00
* To monitor the logs of the container in realtime:
2019-02-10 13:38:37 +00:00
* `docker logs -f healthchecks`
2019-09-01 12:38:04 +00:00
* Container version number
2019-02-10 13:38:37 +00:00
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' healthchecks`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/healthchecks`
## Versions
2019-04-13 06:29:34 +00:00
* **12.04.19:** - Rebase to Alpine 3.9.
2019-03-24 19:41:19 +00:00
* **23.03.19:** - Switching to new Base images, shift to arm32v7 tag.
2019-03-01 00:24:49 +00:00
* **14.02.19:** - Adding mysql libs needed for using a database.
2019-02-10 13:38:37 +00:00
* **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.