Speed up integration test class containers boot time

[sming]

Devise a way to avoid the 2-3 minute spin-up time for integration test class containers boot time

Use Case: ITs take too long to start

• I am a Heroic developer
• Who wants to iterate on his/her changes as fast as possible
• So that I can be maximally efficient and not have to context-switch whilst waiting

Design & Implementation Notes

• currently we use GenericContainer and ElasticsearchContainer

• these are containers that are started and stopped on every code-debug iteration

• they take 2-3 minutes to start. This is a problem as it slows the developer down a lot.

• some kind of daemon (like the one that Gradle starts for quicker compilation) would be ideal

[sming]

from slack convo :

if its a simple matter of “it takes a while” thats another thing. you can cache containers/builds and not rebuild/re-pull each time of course. starting a container should be pretty quick if its ready.

@sjoeboo - so despite running any given IT multiple times in a row (once per debugging session), I still had to wait 2-3 mins each time. Is there some config I can add to docker on my macbook to stop it from tearing down and un-caching those images? If so, how and where? Cheers.
or perhaps it's some "cache_images=true" directive?