added new postgres constructor to allow additional wait strategies #6309
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We ran into this issue with migrating off docker desktop and using rancher desktop, colima, and podman.
rancher-sandbox/rancher-desktop#2609
quarkusio/quarkus#25682
We found the fix would be to wait for ports to become available, however, that overrides the existing wait strategy. Ideally, a new constructor would be available that joins a custom wait strategy with the existing wait strategy.
The unit test demonstrates what basically works, adding an additional wait for exposed ports. I have verified adding that wait with the existing wait fixes this issue.
Also, as more devs migrate off docker desktop, this issue will likely impair devs so getting a convenient fix is prudent.