Explain that Docker Desktop is required to run S3ObjectFetchingTest#137
Merged
Explain that Docker Desktop is required to run S3ObjectFetchingTest#137
S3ObjectFetchingTest#137Conversation
3da6705 to
c13f712
Compare
c13f712 to
c02d85c
Compare
S3ObjectFetchingTest
emdash-ie
approved these changes
Feb 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
S3ObjectFetchingTestuses S3Mock/testcontainers/Docker, and requires Docker Engine to be running on the machine.Without Docker Desktop, alternatives like Colima can be explored, but see:
testcontainers-javacurrently doesn't support different Docker contextsThis PR adds a message explaining the problem when Docker Engine isn't available - the default error in this situation wasn't fully explanatory, and didn't explain that Guardian devs will probably want to use & start Docker Desktop: