Enabling Docker for Pipelines wrongfully reserves 1 GB of memory

Issue #14666 closed
Jeroen De Raedt
staff created an issue

When Docker is enabled for a Pipelines build, it wrongfully results in 1GB of memory reservation (out of the total 4 GB of memory allocated to each build).

Having Docker enabled should not result in any memory reservation.

Comments (6)

  1. Raul Gomis staff


    We have just deployed a fix for this issue. Now, the memory allocation should be correct when docker is enabled.

    Please, let me know if you have any more questions or observe other weird behavior.


  2. Log in to comment