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:
- Discord - realtime support / chat with the community and the team.
- IRC - on freenode at
#linuxserver.io. Our primary support channel is Discord. - Blog - all the things you can do with our containers including How-To guides, opinions and much more!
Smokeping keeps track of your network latency. For a full example of what this application is capable of visit UCDavis.
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/smokeping 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=smokeping \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Europe/London \
-p 80:80 \
-v </path/to/smokeping/config>:/config \
-v </path/to/smokeping/data>:/data \
--restart unless-stopped \
linuxserver/smokeping
Compatible with docker-compose v2 schemas.
---
version: "2"
services:
smokeping:
image: linuxserver/smokeping
container_name: smokeping
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/London
volumes:
- </path/to/smokeping/config>:/config
- </path/to/smokeping/data>:/data
ports:
- 80:80
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 80 |
Allows HTTP access to the internal webserver. |
-e PUID=1000 |
for UserID - see below for explanation |
-e PGID=1000 |
for GroupID - see below for explanation |
-e TZ=Europe/London |
Specify a timezone to use EG Europe/London |
-v /config |
Configure the Targets file here |
-v /data |
Storage location for db and application data (graphs etc) |
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)
- Once running the URL will be
http://<host-ip>/. - Basics are, edit the
Targetsfile to ping the hosts you're interested in to match the format found there. - Wait 10 minutes.
- Shell access whilst the container is running:
docker exec -it smokeping /bin/bash - To monitor the logs of the container in realtime:
docker logs -f smokeping - container version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' smokeping
- image version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/smokeping
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/smokeping - Stop the running container:
docker stop smokeping - Delete the container:
docker rm smokeping - Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your
/configfolder and settings will be preserved) - Start the new container:
docker start smokeping - 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 shot:
docker run --rm \ -v /var/run/docker.sock:/var/run/docker.sock taisun/updater \ --oneshot smokeping - 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 smokeping
- 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 smokeping
- or update a single container:
- You can also remove the old dangling images:
docker image prune
- 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
- 22.02.19: - Rebasing to alpine 3.9.
- 14.11.18: - Allow access without /smokeping in URL.
- 28.04.18: - Rebase to alpine 3.8.
- 09.04.18: - Add bc package.
- 08.04.18: - Add tccping script and tcptraceroute package (thanks rcarmo).
- 13.12.17: - Expose httpd_conf to /config.
- 13.12.17: - Rebase to alpine 3.7.
- 24.07.17: - Add :unraid tag for hosts without ipv6.
- 12.07.17: - Add inspect commands to README, move to jenkins build and push.
- 28.05.17: - Rebase to alpine 3.6.
- 07.05.17: - Expose smokeping.conf in /config/site-confs to allow user customisations
- 12.04.17: - Fix cropper.js path, thanks nibbledeez.
- 09.02.17: - Rebase to alpine 3.5.
- 17.10.16: - Add ttf-dejavu package as per LT forum.
- 10.09.16: - Add layer badges to README.
- 05.09.16: - Add curl package.
- 28.08.16: - Add badges to README.
- 25.07.16: - Rebase to alpine linux.
- 23.07.16: - Fix apt script confusion.
- 29.06.15: - This is the first release, it is mostly stable, but may contain minor defects. (thus a beta tag)