Fix lint warnings in simple test Dockerfile #1494
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR fixes two lint warnings in
tests/dockerfile/simple/Dockerfile:JSONArgsRecommended: The Dockerfile used shell form
CMD "/bin/sh"which triggers a warning.
Updated to JSON exec form:
CMD ["/bin/sh"]LegacyKeyValueFormat: The Dockerfile used
ENV HOME /tmpwhich triggers a lint warning.
Updated to recommended format:
ENV HOME=/tmpThese are small cleanups in the test Dockerfile and do not change runtime
behavior of repo2docker. They simply align with Docker best practices and
resolve the linter warnings.
Fixes #1477
Fixes #1478