[Feature]: Container startup attempt backoff strategy

Module

None

Problem

I have a JUnit test extension that starts up a container. If multiple tests are executing in parallel in isolated JVMs, they contend for the container name and port bindings. One can work around this by giving it effectively infinite startup attempts and a reasonable startup timeout, but this generates excessive test logs from constant startup attempts.

Solution

Introduce a startup attempt backoff strategy option when constructing a container. Being able to exponentially backoff to a reasonable interval between startup attempts would help in reducing logs.

Benefit

This would benefit any situation where there is contention for exclusive resources between container instances, or any other situation where container startups are very flaky for an extended period, but eventual success is likely.

Alternatives

At the moment I'm using Awaitility to check for container name contention before attempting startup.

Would you like to help contributing this feature?

Yes

L’issue non identifica file, test o un punto di ingresso, quindi per prima cosa traccia il tentativo di avvio del container e la gestione dei retry utilizzati durante la costruzione di un container. Definisci il comportamento di backoff configurabile, inclusi i ritardi esponenziali e la sua interazione con i tentativi di avvio e i timeout; il lavoro è completato quando i conflitti possono essere ritentati con meno logs e l’avvio successivo rimane possibile.