Dockerfile: Fix legacy ENV key value format
#1047
Merged
+14
−14
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
Member
|
This needs a rebase after #1037 to make CI pass |
Replace legacy `ENV key value` syntax with `ENV key=value`. This fixes the build linter warning LegacyKeyValueFormat. Signed-off-by: Paweł Gronowski <[email protected]>
vvoland
force-pushed
the
fix-builder-lint
branch
from
7e58c7b to
d61915e
Compare
thaJeztah
approved these changes
Aug 16, 2024
Member
thaJeztah
left a comment
thaJeztah
left a comment
There was a problem hiding this comment.
LGTM
feel free to merge when it suits you best
1 task
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.
Replace legacy
ENV key valuesyntax withENV key=value.This fixes the build linter warning LegacyKeyValueFormat.
Signed-off-by: Paweł Gronowski [email protected]