introduce --parallel to limit concurrent engine calls#10030
Conversation
37b5d4b to
cdabc00
Compare
glours
left a comment
glours
left a comment
There was a problem hiding this comment.
I think tests are failing due to the wrong default value of the maxConcurrency attribute.
Docs should also be updated 😉
51b5ee7 to
9bc188b
Compare
|
Oh nice! This is something that people have asked for for a while, albeit mostly regarding build operations. |
|
Build max-parallelism can be controlled, but this takes place on the builder side: https://github.com/docker/buildx/blob/master/docs/guides/resource-limiting.md#max-parallelism |
9bc188b to
3078aee
Compare
3078aee to
5bde50d
Compare
Codecov ReportBase: 77.02% // Head: 77.02% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## v2 #10030 +/- ##
=======================================
Coverage 77.02% 77.02%
=======================================
Files 2 2
Lines 235 235
=======================================
Hits 181 181
Misses 48 48
Partials 6 6 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Signed-off-by: Nicolas De Loof <[email protected]>
5bde50d to
a0acc20
Compare
4 participants
What I did
Introduce
--parallel=<int>for user to limit the concurrency during image pullscould be later applied to other operations, typically
buildwith adequate buildx|kit support for thisRelated issue
(not mandatory) A picture of a cute animal, if possible in relation to what you did
