linter: lint rule for using the legacy key/value format with whitespace #4923
Conversation
This file contains 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
jsternberg
force-pushed
the
lint-legacy-key-value-env
branch
4 times, most recently
from
18a8384
to
6be16d1
Compare
daghack
approved these changes
May 15, 2024
thaJeztah
reviewed
May 16, 2024
Comment on lines
+634
to
+636
| FROM scratch | ||
| ENV key value | ||
| LABEL key value |
There was a problem hiding this comment.
I know there were some concerns about warning about these being potentially too strict.
Wondering if we should have a "more permissive" and "more strict" rule. The most problematic ones are when multiple whitespaces are present;
ARG key one two
ENV key one twoThose look very much alike, but ARG means 3 args are defined, but the ENV one defines a single key env with value one two
thaJeztah
approved these changes
May 16, 2024
tonistiigi
reviewed
May 29, 2024
| @@ -105,4 +105,11 @@ var ( | |||
| return fmt.Sprintf("Multiple %s instructions should not be used in the same stage because only the last one will be used", instructionName) | |||
| }, | |||
| } | |||
| RuleLegacyKeyValueFormat = LinterRule[func(cmdName string) string]{ | |||
There was a problem hiding this comment.
We should provide some hint that key=value should be used instead in the message. Most users will not know what is "legacy format"
There was a problem hiding this comment.
Changed this message to read differently so now it explicitly mentions the solution in the detailed description.
jsternberg
force-pushed
the
lint-legacy-key-value-env
branch
from
6be16d1
to
d312e96
Compare
The `ENV` and `LABEL` commands both support using either a whitespace delimited token or one delimited with the equals token. The equals token is preferred because it is more explicit and less ambiguous than using whitespace. The linter rule emits a warning when it sees the whitespace separator used. To facilitate this, the parser was modified to include the separator as a node in the tree. The associated parsing code has also been changed for 3 arguments instead of only 2 per key/value pair. Signed-off-by: Jonathan A. Sternberg <jonathan.sternberg@docker.com>
jsternberg
force-pushed
the
lint-legacy-key-value-env
branch
from
d312e96
to
6cfa459
Compare
tonistiigi
approved these changes
May 30, 2024
techknowlogick
pushed a commit
to go-gitea/gitea
that referenced
this pull request
Jun 21, 2024
See https://docs.docker.com/reference/build-checks/legacy-key-value-format/. Fixes these warnings seen during the docker build: ``` 4 warnings found (use --debug to expand): - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 5) - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 9) - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 75) - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 76) ``` Introduced in: moby/buildkit#4923
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this pull request
Jun 21, 2024
See https://docs.docker.com/reference/build-checks/legacy-key-value-format/. Fixes these warnings seen during the docker build: ``` 4 warnings found (use --debug to expand): - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 5) - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 9) - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 75) - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 76) ``` Introduced in: moby/buildkit#4923
techknowlogick
pushed a commit
to go-gitea/gitea
that referenced
this pull request
Jun 24, 2024
Backport #31450 by @silverwind See https://docs.docker.com/reference/build-checks/legacy-key-value-format/. Fixes these warnings seen during the docker build: ``` 4 warnings found (use --debug to expand): - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 5) - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 9) - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 75) - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 76) ``` Introduced in: moby/buildkit#4923 Co-authored-by: silverwind <me@silverwind.io>
DennisRasey
pushed a commit
to DennisRasey/forgejo
that referenced
this pull request
Jun 25, 2024
See https://docs.docker.com/reference/build-checks/legacy-key-value-format/. Fixes these warnings seen during the docker build: ``` 4 warnings found (use --debug to expand): - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 5) - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 9) - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 75) - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 76) ``` Introduced in: moby/buildkit#4923 (cherry picked from commit 996037fb6a61b1a7f9a0a837fd87bbeab9cad154) Conflicts: Dockerfile.rootless trivial context conflict
luzfcb
added a commit
to cookiecutter/cookiecutter-django
that referenced
this pull request
Jul 18, 2024
The old syntax for ENV and LABEL is marked as deprecated in docker buildx v0.14.0 https://docs.docker.com/reference/build-checks/legacy-key-value-format/ moby/buildkit#4923
Merged
2 tasks
luzfcb
added a commit
to cookiecutter/cookiecutter-django
that referenced
this pull request
Jul 18, 2024
The old syntax for ENV and LABEL is marked as deprecated in docker buildx v0.14.0 https://docs.docker.com/reference/build-checks/legacy-key-value-format/ moby/buildkit#4923
luzfcb
added a commit
to cookiecutter/cookiecutter-django
that referenced
this pull request
Jul 19, 2024
The old syntax for ENV and LABEL is marked as deprecated in docker buildx v0.14.0 https://docs.docker.com/reference/build-checks/legacy-key-value-format/ moby/buildkit#4923
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
ENVandLABELcommands both support using either a whitespace delimited token or one delimited with the equals token. The equals token is preferred because it is more explicit and less ambiguous than using whitespace. The linter rule emits a warning when it sees the whitespace separator used.To facilitate this, the parser was modified to include the separator as a node in the tree. The associated parsing code has also been changed for 3 arguments instead of only 2 per key/value pair.