Skip to content

Docker executor no longer reuses predefined container names

What does this MR do?

This MR makes the docker execute generate a new random name each time it creates a "predefined" container.

Why was this MR needed?

Previously, the random container name was computed once and then reused during the execution of a job.
This causes conflicts when docker does not remove the previous container fast enough.

What's the best way to test this MR?

  1. Run a pipeline, check that the pipeline succeeds and that all containers are cleaned up.
  2. Run a pipeline during high IO load (see #21387). This test procedure is non-deterministic and flaky.

What are the relevant issue numbers?

#2408 (closed) #21387

Edited by i-do cpp

Merge request reports