Repository navigation
Replies: 1 comment
|
Thanks for the question, and sorry it went unanswered for so long.
I've added this to my fork: each host now has optional build limits (CPU cores and memory) in Settings → Docker Hosts → (host) → Build limits. Your Measured on the published image: a build step running two CPU-bound processes took ~3.5 s unlimited and ~13.5 s capped at 0.5 core: four times less CPU, four times the time, so the build never used more than half a core. Trade-offs while limits are set: the limited builder has its own cache (the first build after enabling them starts cold), and the image is loaded into Docker at the end of each build, which adds a few seconds. Behind LinuxServer's socket-proxy it also needs Test image: Feedback welcome!
|

Uh oh!
There was an error while loading. Please reload this page.
Is it possible to set custom arguments to dockman that will be used whenever a image is built? I need to set
--cpu-period=100000
--cpu-quota=100000
so my CPU doesn't get hogged to a 100% while the build is running because it causes issues but I dont see a option to do so
All reactions