migrate healthcheck enhancements to S3 image #12347
Merged
Conversation
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
alexrashed
added
the
semver: patch
S3 Image Test Results (AMD64 / ARM64) 2 files 2 suites 8m 50s ⏱️ Results for commit be3527e. |
bentsku
approved these changes
Mar 6, 2025
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.
Motivation
#12344 changed the health check in the
Dockerfileof the main image to be independent of the working directory (since some tools might be changing the workdir).Unfortunately during the review, I forgot about the S3 image, which is covered in this PR.
Changes
HEALTHCHECKdirective in theDockerfile.s3to be independent of the working directory.