Do not require comma delimiters for exec form #117
Merged
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.
In order to better facilitate parsing of the output from the
docker history
command, it's necessary to loosen the requirements of parsing exec form instructions such asCMD
.As an example, a Dockerfile containing the instruction
CMD ["echo", "Hello"]
will be represented asCMD ["echo" "Hello"]
in the output of thedocker history
command (notice the lack of a comma). So it's not truly a valid JSON array syntax.This updates the parsing logic to allow the comma to be optional in this case.