Get rid of Docker warnings#31
Merged
Merged
Conversation
dv4harr10
approved these changes
Sep 3, 2024
3 tasks
mcdonnnj
approved these changes
Oct 9, 2025
This gets rid of a warning from docker-compose.
This gets rid of a warning from Docker.
8df9437 to
830fd13
Compare
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.
🗣 Description
This pull request gets rid of one warning from
docker composeand two warnings fromdocker build.💭 Motivation and context
docker-composewarning is due to the fact that theversionkey has been deprecated in Docker composition files.dockerwarnings are both due to the fact that inDockerfilethe wordASshould be uppercase inFROM...AS...lines.Code without warnings is cleaner code.
🧪 Testing
All automated tests pass.
✅ Pre-approval checklist