kopia lustrzana https://github.com/linuxserver/docker-documentation
Bot Updating Templated Files
LinuxServer-CI
rodzic
041e2e331f
commit
14f157c90f
|
|
@ -1,30 +1,37 @@
|
|||
# linuxserver/smokeping
|
||||
# [linuxserver/smokeping](https://github.com/linuxserver/docker-smokeping)
|
||||
|
||||
[](https://discord.gg/YWrKVTn) [](https://microbadger.com/images/linuxserver/smokeping) [](https://microbadger.com/images/linuxserver/smokeping)   [](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-smokeping/job/master/) [](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/smokeping/latest/index.html)
|
||||
[](https://discord.gg/YWrKVTn)
|
||||
[](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")
|
||||
|
||||
|
||||
[](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-smokeping/job/master/)
|
||||
[](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/smokeping/latest/index.html)
|
||||
|
||||
[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) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
|
||||
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/).
|
||||
|
||||
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 | arm32v6-latest |
|
||||
|
||||
|
||||
## Usage
|
||||
|
||||
Here are some example snippets to help you get started creating a container from this image.
|
||||
|
||||
### docker
|
||||
|
||||
```text
|
||||
```
|
||||
docker create \
|
||||
--name=smokeping \
|
||||
-e PUID=1000 \
|
||||
|
|
@ -37,6 +44,7 @@ docker create \
|
|||
linuxserver/smokeping
|
||||
```
|
||||
|
||||
|
||||
### docker-compose
|
||||
|
||||
Compatible with docker-compose v2 schemas.
|
||||
|
|
@ -62,47 +70,52 @@ services:
|
|||
|
||||
## 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.
|
||||
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`\)
|
||||
### Ports (`-p`)
|
||||
|
||||
| Parameter | Function |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| `80` | Allows HTTP access to the internal webserver. |
|
||||
|
||||
### Environment Variables \(`-e`\)
|
||||
|
||||
### Environment Variables (`-e`)
|
||||
|
||||
| Env | Function |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| `PUID=1000` | for UserID - see below for explanation |
|
||||
| `PGID=1000` | for GroupID - see below for explanation |
|
||||
| `TZ=Europe/London` | Specify a timezone to use EG Europe/London |
|
||||
|
||||
### Volume Mappings \(`-v`\)
|
||||
### Volume Mappings (`-v`)
|
||||
|
||||
| Volume | Function |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| `/config` | Configure the `Targets` file here |
|
||||
| `/data` | Storage location for db and application data \(graphs etc\) |
|
||||
| `/data` | Storage location for db and application data (graphs etc) |
|
||||
|
||||
|
||||
|
||||
## User / Group Identifiers
|
||||
|
||||
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`.
|
||||
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:
|
||||
|
||||
```text
|
||||
```
|
||||
$ id username
|
||||
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
|
||||
```
|
||||
|
||||
## Application Setup
|
||||
|
||||
* Once running the URL will be `http://<host-ip>/`.
|
||||
* Basics are, edit the `Targets` file to ping the hosts you're interested in to match the format found there.
|
||||
* Wait 10 minutes.
|
||||
- Once running the URL will be `http://<host-ip>/`.
|
||||
- Basics are, edit the `Targets` file to ping the hosts you're interested in to match the format found there.
|
||||
- Wait 10 minutes.
|
||||
|
||||
|
||||
|
||||
## Support Info
|
||||
|
||||
|
|
@ -121,8 +134,8 @@ In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as bel
|
|||
* **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.
|
||||
* **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.
|
||||
|
|
@ -136,5 +149,4 @@ In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as bel
|
|||
* **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\)
|
||||
|
||||
* **29.06.15:** - This is the first release, it is mostly stable, but may contain minor defects. (thus a beta tag)
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue