NickBorgers

Thank you for flagging, not sure what happened there. Should be fixed now, though I'm not sure how that update propagates. Lol at the hogz of terror

@TimTheSettler this is now published as an unraid app; creating this forum post was part of the criteria.

When I started up my new server machine and installed unraid as the OS I wanted to run some stress tests to validate the thermal performance of the machine and how much noise it would make. I found this thread with a technique: https://forums.unraid.net/topic/119655-updated-unraid-stress-and-temperature-testing-with-docker-cpu-temps-system-stablity/ However the docker image it relied on is no longer usable, so I built a new one. This thread is for support for the container image.

I have started using unraid as a converged data storage and workload environment. The simplicity it provides comes at a cost, which is that I feel the command line interface on the base OS is not well suited to diagnosing problems. An example is that tcpdump is not available, which makes it very difficult for me to diagnose problems. I got around this by creating a container image which slept forever, giving me something to exec into and take actions including running tcpdump. This is a thread for support for the container. https://github.com/NickBorgers/util/tree/main/unraid-util

You can run this again, I took what progrium did and duplicated it. Both just wrap the existing tool stress. https://github.com/NickBorgers/util/releases/tag/v1.3.0 https://hub.docker.com/r/nickborgers/stress docker run --rm --network=none --user=99:100 -it nickborgers/stress --cpu 2 --io 1 --vm 2 --vm-bytes 128M --timeout 10s