[](https://microbadger.com/images/linuxserver/smokeping "Get your own version badge on microbadger.com")
[](https://microbadger.com/images/linuxserver/smokeping "Get your own version badge on microbadger.com")
[Smokeping](https://oss.oetiker.ch/smokeping/) keeps track of your network latency. For a full example of what this application is capable of visit [UCDavis](http://smokeping.ucdavis.edu/cgi-bin/smokeping.fcgi).
## Supported Architectures
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).
Here are some example snippets to help you get started creating a container from this image.
### docker
```
docker create \
--name=smokeping \
-e PUID=1001 \
-e PGID=1001 \
-e TZ=Europe/London \
-p 80:80 \
-v </path/to/smokeping/config>:/config \
-v </path/to/smokeping/data>:/data \
--restart unless-stopped \
linuxserver/smokeping
```
### docker-compose
Compatible with docker-compose v2 schemas.
```yaml
---
version: "2"
services:
smokeping:
image: linuxserver/smokeping
container_name: smokeping
environment:
- PUID=1001
- PGID=1001
- TZ=Europe/London
volumes:
-</path/to/smokeping/config>:/config
-</path/to/smokeping/data>:/data
ports:
- 80:80
mem_limit: 4096m
restart: unless-stopped
```
## Parameters
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.
### Ports (`-p`)
| Parameter | Function |
| :----: | --- |
| `80` | Allows HTTP access to the internal webserver. |
### Environment Variables (`-e`)
| Env | Function |
| :----: | --- |
| `PUID=1001` | for UserID - see below for explanation |
| `PGID=1001` | for GroupID - see below for explanation |
| `TZ=Europe/London` | Specify a timezone to use EG Europe/London |
### Volume Mappings (`-v`)
| Volume | Function |
| :----: | --- |
| `/config` | Configure the `Targets` file here |
| `/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=1001` and `PGID=1001`, to find yours use `id user` as below:
