Skip to content

Always prefer creating new containers when running with Docker Executor

Kamil Trzciński requested to merge docker-prefer-to-always-create-containers into master

What does this MR do?

We seem to be colliding with some external services that can remove stopped containers without us watching. This makes us see some strange error messages when it happens. When possible try to create and number a new container instead of using existing one. In order to not break the compatibility do not do that for after_script as otherwise we might loose image context. Ideal solution would be to commit and spun a new one, but let's skip that for now.

Does this MR meet the acceptance criteria?

  • Documentation created/updated
  • Tests
    • Added for this feature/bug
    • All builds are passing
  • Branch has no merge conflicts with master (if you do - rebase it please)

What are the relevant issue numbers?

Closes #2347 (closed)

Edited by Alessio Caiazza (OOO until 2024-08-26)

Merge request reports