0
0
Fork
You've already forked iperf3_docker
0
Iperf3 server in a docker image
squirl 22533c05a4
All checks were successful
build / build (push) Successful in 36s
updated ci and nginx
2025年12月16日 19:18:02 +01:00
.forgejo/workflows updated ci and nginx 2025年12月16日 19:18:02 +01:00
.gitignore Initial commit 2024年08月17日 00:30:16 +02:00
dockerfile updated ci and nginx 2025年12月16日 19:18:02 +01:00
readme.md specified the exact alpine version, extended the readme 2025年04月27日 22:27:27 +02:00
unlicence Initial commit 2024年08月17日 00:30:16 +02:00

Iperf3 docker image

An image for running an iperf3 server.

Running in docker

Docker compose in a production environment:

services:
 iperf3:
 image: codeberg.org/squirl/iperf3:latest
 restart: always
 ports:
 - "5201:5201"

Docker compose in a development environment (local build):

services:
 iperf3:
 build:
 context: .
 dockerfile: dockerfile
 restart: always
 ports:
 - "5201:5201"

CI

This repo comes with automatic builds on push, and makes a release on a tag push (automatic release triggers on tag v..). CI needs to have access to the repos api. Goto the applications settings and generate a token, with repo and package read and write access. Next, add the api key to actions of the repo as a secret, under the key REGISTRY_API_KEY. Don't forget to enable actions and the package repository for the repo. Also don't forget to link the package to the repo, as this is not done automatically.

Further env variables:

  • RUNNER_CERT_PATH: Path to the docker in docker certs (in my case: /certs/client)
  • RUNNER_DOCKER_HOST: Hostname for the docker in docker instance, as define when creating the runner (in my case: codeberg-docker)
  • RUNNER_IMAGE_NAME: Image name of the container (in this case: iperf3)
  • RUNNER_REPO_URL: URL of the forgejo container registry (in my case: codeberg.org)