feat: build containers for iperf with github actions#1763
feat: build containers for iperf with github actions#1763kashalls wants to merge 3 commits intoesnet:masterfrom
Conversation
|
My intention for this feature was to setup some kind of "official" implementation of an iperf container. A Dockerfile as added to If you go to docker hub, there are almost 1,400 different containers that have been pushed once and never again. There is no telling what those containers actually run unless you look into it. What individual is going to look through 1,400 containers. Publishing this container, automatically, will allow users who only want to run trusted containers an option instead of having to build, maintain and deploy forks. |
|
I do something similar here but I use Alpine Linux and target more architectures + windows x86_64 builds. https://github.com/userdocs/iperf3-static docker run -it ghcr.io/userdocs/iperf3-static:latest iperf3 --version |
|
Hey, just curious why this PR got closed instead of merged? |
It went roughly a year with no comments from maintainers, or anyone else for that matter. I can reopen it if someone wants it as a feature still. |
|
Yeah, it'd be wonderful to have an official Docker image, instead of thousands of sketchy images. I finally found a way to install it as a service on macOS though, detailed in #1958 |

PLEASE NOTE the following text from the iperf3 license. Submitting a
pull request to the iperf3 repository constitutes "[making]
Enhancements available...publicly":
The complete iperf3 license is available in the
LICENSEfile in thetop directory of the iperf3 source tree.
Version of iperf3 (or development branch, such as
masteror3.1-STABLE) to which this pull request applies: masterIssues fixed (if any): (See brief description)
Brief description of code changes (suitable for use as a commit message):
Adds automation to expand on pre-existing Dockerfile. It builds and deploys the container to ghcr.io/esnet/iperf.