linuxserver/smokeping
Simply pulling
lscr.io/linuxserver/smokeping:latest
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 | Available | Tag |
---|---|---|
x86-64 | ✅ | amd64-<version tag> |
arm64 | ✅ | arm64v8-<version tag> |
armhf | ❌ | |
- Once running the URL will be
http://<host-ip>/smokeping/smokeping.cgi
. For example a full URL might look likehttps://smokeping.yourdomain.com/smokeping/smokeping.cgi
. - Basics are, edit the
Targets
file to ping the hosts you're interested in to match the format found there. - Wait 10 minutes.
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
---
version: "2.1"
services:
smokeping:
image: lscr.io/linuxserver/smokeping:latest
container_name: smokeping
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
volumes:
- /path/to/smokeping/config:/config
- /path/to/smokeping/data:/data
ports:
- 80:80
restart: unless-stopped
docker run -d \
--name=smokeping \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Etc/UTC \
-p 80:80 \
-v /path/to/smokeping/config:/config \
-v /path/to/smokeping/data:/data \
--restart unless-stopped \
lscr.io/linuxserver/smokeping:latest
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.Parameter | Function |
---|---|
80 | Allows HTTP access to the internal webserver. |
Env | Function |
---|---|
PUID=1000 | for UserID - see below for explanation |
PGID=1000 | for GroupID - see below for explanation |
TZ=Etc/UTC |
Volume | Function |
---|---|
/config | Configure the Targets file here |
/data | Storage location for db and application data (graphs etc) |
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)