Hey folks, I’m enabling Gradle’s configuration cache in CI and running into a Docker auth issue with Testcontainers. The first run after turning it on is fine, then about an hour later a fresh run starts failing to pull from our private registry with 401. If I switch the configuration cache off, the same workflow passes. I’m not reading credentials during configuration, so I’m puzzled about what state could be getting reused. Could the configuration cache cause tests to see stale Docker auth across runs? Is it more practical to mark tests as not compatible with the configuration cache because the registry token is short-lived? If anyone has dealt with configuration cache oddities like this, I’d appreciate pointers.

You say you do not read the token at configuration time, how do you read it?

It's a couple layers of abstraction away from my code 😅 Testcontainers uses the Docker API, so I assume there's somewhere sort of logic in there to grab the auth in there

Can you knit an MCVE? Without knowing your situation it is pretty hard to give substantial advice.