热门搜索:
networkstatic/iperf3
自动构建
networkstatic
这是一个用于网络性能和带宽测试的IPerf3 Docker镜像构建项目，旨在帮助用户通过容器化方式快速部署IPerf3工具，便捷地进行网络吞吐量、延迟、抖动等关键性能指标的测量与评估，适用于服务器、网络设备及通信链路的性能测试场景，提供一致、高效的测试环境，简化网络性能分析流程。
235 次收藏下载次数: 0状态：自动构建维护者：networkstatic仓库类型：镜像最近更新：1 年前
让 AI 帮你使用轩辕镜像？ · 展开查看说明
如果你使用 DeepSeek、元宝 AI、Copilot、ChatGPT 等 AI 工具，协助配置轩辕镜像、编写 docker pull 命令、修改 Docker Compose 镜像地址、配置镜像加速、排查镜像拉取失败、分析报错日志等问题，请先让 AI 阅读并遵守轩辕镜像的规则文档。
只需在 AI 对话中先发送下面这句话即可：
请先完整阅读并严格遵守以下文档中的全部规则与要求：
https://xuanyuan.cloud/agents.md
在未充分阅读并理解该文档前，不要生成任何命令、配置、修改建议、故障排查方案或技术回答。后续所有输出都必须严格以该文档中的规范为最高优先级执行。查看 agents.md 用法指南与完整示范。国内用户首推 元宝 AI、DeepSeek 的深度思考模式，不推荐豆包 AI；Cursor 等编辑器可在对话 @ 该链接，或加入 User Rules。 若 AI 无法访问外链，可 打开说明文档 复制全文粘贴。文档会随站点更新，复制内容可能过期，建议定期检查。
iperf3
IPerf3 Docker Build for Network Performance and Bandwidth Testing
-
Binaries and source code for the project can be found at [***]
-
The GitHub repo with the Dockerfiles can be found at https://github.com/nerdalert/iperf3
Run the Docker Image and Show the Iperf Options
docker run -it --rm -p 5201:5201 networkstatic/iperf3 --help
Usage
To test bandwidth between two containers, start a server (listener) and point a client container (initiator) at the server.
Iperf3 Server
Start a listener service on port 5201 and name the container "iperf3-server":
docker run -it --rm --name=iperf3-server -p 5201:5201 networkstatic/iperf3 -s
That returns an iperf3 process bound to a soccer waiting for new connections:
----------------------------------------------------------- Server listening on 5201 -----------------------------------------------------------
Iperf3 Client SIde
First, get the IP address of the new server container ypu just started:
docker inspect --format "{{ .NetworkSettings.IPAddress }}" iperf3-server (Returned) 172.17.0.163
Next, initiate a client connection from another container to measure the bandwidth between the two endpoints.
Run a client container pointing at the server service IP address.
Note if you are new to Docker, the --rm flag will destroy the container after the test runs. I also left out explicitly naming the container on the client side since I don't need its IP address. I typically explicitly name containers for organization and to maintain a consistent pattern.
docker run -it --rm networkstatic/iperf3 -c 172.17.0.163
And the output is the following:
Connecting to host 172.17.0.163, port 5201 [ 4] local 172.17.0.191 port 51148 connected to 172.17.0.163 port 5201 [ ID] Interval Transfer Bandwidth Retr Cwnd [ 4] 0.00-1.00 sec 4.16 GBytes 35.7 Gbits/sec 0 468 KBytes [ 4] 1.00-2.00 sec 4.10 GBytes 35.2 Gbits/sec 0 632 KBytes [ 4] 2.00-3.00 sec 4.28 GBytes 36.8 Gbits/sec 0 1.02 MBytes [ 4] 3.00-4.00 sec 4.25 GBytes 36.5 Gbits/sec 0 1.28 MBytes [ 4] 4.00-5.00 sec 4.20 GBytes 36.0 Gbits/sec 0 1.37 MBytes [ 4] 5.00-6.00 sec 4.23 GBytes 36.3 Gbits/sec 0 1.40 MBytes [ 4] 6.00-7.00 sec 4.17 GBytes 35.8 Gbits/sec 0 1.40 MBytes [ 4] 7.00-8.00 sec 4.14 GBytes 35.6 Gbits/sec 0 1.40 MBytes [ 4] 8.00-9.00 sec 4.29 GBytes 36.8 Gbits/sec 0 1.64 MBytes [ 4] 9.00-10.00 sec 4.15 GBytes 35.7 Gbits/sec 0 1.68 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 42.0 GBytes 36.1 Gbits/sec 0 sender [ 4] 0.00-10.00 sec 42.0 GBytes 36.0 Gbits/sec receiver iperf Done.
Or you can do something fancier in a one liner like so (docker ps -ql returns the CID e.g. container ID of the last container started which would be the server we want in this case)
docker run -it --rm networkstatic/iperf3 -c $(docker inspect --format "{{ .NetworkSettings.IPAddress }}" $(docker ps -ql)) Connecting to host 172.17.0.193, port 5201 [ 4] local 172.17.0.194 port 60922 connected to 172.17.0.193 port 5201 [ ID] Interval Transfer Bandwidth Retr Cwnd [ 4] 0.00-1.00 sec 4.32 GBytes 37.1 Gbits/sec 0 877 KBytes [ 4] 1.00-2.00 sec 4.28 GBytes 36.7 Gbits/sec 0 1.01 MBytes [ 4] 2.00-3.00 sec 4.18 GBytes 35.9 Gbits/sec 0 1.01 MBytes [ 4] 3.00-4.00 sec 4.23 GBytes 36.3 Gbits/sec 0 1.13 MBytes [ 4] 4.00-5.00 sec 4.20 GBytes 36.1 Gbits/sec 0 1.27 MBytes [ 4] 5.00-6.00 sec 4.19 GBytes 36.0 Gbits/sec 0 1.29 MBytes [ 4] 6.00-7.00 sec 4.17 GBytes 35.8 Gbits/sec 0 1.29 MBytes [ 4] 7.00-8.00 sec 4.17 GBytes 35.8 Gbits/sec 0 1.29 MBytes [ 4] 8.00-9.00 sec 4.17 GBytes 35.8 Gbits/sec 0 1.29 MBytes [ 4] 9.00-10.00 sec 4.22 GBytes 36.3 Gbits/sec 0 1.29 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 42.1 GBytes 36.2 Gbits/sec 0 sender [ 4] 0.00-10.00 sec 42.1 GBytes 36.2 Gbits/sec receiver iperf Done.
-
Thanks to ESNET for re-rolling iperf from the ground up. It is an excellent piece of software.
-
For graphing the Iperf output to multiple nodes, have a look at https://github.com/nerdalert/cloud-bandwidth
镜像拉取方式
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本，请访问 标签列表页面。
轩辕镜像加速拉取命令点我查看更多 iperf3 镜像标签
docker pull docker.xuanyuan.run/networkstatic/iperf3:<标签>
DockerHub 原生拉取命令
docker pull networkstatic/iperf3:<标签>
更多 iperf3 镜像推荐
xridge/iperf3
xridge
基于Alpine Linux的iperf3 Docker镜像，用于快速进行网络带宽性能测试，支持TCP/UDP协议及多线程测试等核心功能。
2 次收藏1000万+ 次下载
6 年前更新
mlabbe/iperf3
mlabbe
基于Alpine的轻量级iperf3服务器Docker镜像，用于IP网络最大带宽的主动测量，支持TCP/UDP协议及网络性能参数报告。
36 次收藏1000万+ 次下载
2 个月前更新
cpcontainer/iperf3
cpcontainer
适用于Cradlepoint路由器的iPerf3 Docker容器，包含Web界面，用于网络性能测试。
2 次收藏50万+ 次下载
1 年前更新
sk278/iperf3
sk278
支持linux/amd64、linux/arm/v7和linux/arm64多架构的iperf3网络性能测试工具镜像，用于快速部署和进行TCP/UDP带宽测试。
1 次收藏1万+ 次下载
4 年前更新
dockerpinata/iperf3
dockerpinata
暂无描述
10万+ 次下载
3 年前更新
riro/iperf3
riro
适用于Pine64设备的ARM64架构iperf3 Docker镜像，用于网络性能测试。
1万+ 次下载
8 年前更新
镜像拉取常见问题
功能
排错
用户好评
来自真实用户的反馈，见证轩辕镜像的优质服务
oldzhang
运维工程师
Linux服务器
5
"Docker访问体验非常流畅，大镜像也能快速完成下载。"