Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[27.x backport] rpm, deb: fix Dockerfile linting issues #1065

Merged
merged 2 commits into from
Sep 4, 2024

Conversation

thaJeztah
Copy link
Member

commit d61915e addressed these warnings
for the deb-based Dockerfiles, but didn't update the rpm ones;

     - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 13)
     - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 15)
     - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 16)

Signed-off-by: Sebastiaan van Stijn <[email protected]>
(cherry picked from commit 3a7bbe7)
Signed-off-by: Sebastiaan van Stijn <[email protected]>
The `GO_IMAGE` build-arg doesn't have a default;

     - InvalidDefaultArgInFrom: Default value for ARG ${GO_IMAGE} results in empty or invalid base image name (line 8)

This is not a real issue when building using the Makefiles (which is how
these Dockerfiles are expected to be used) but we can probably set a
default.

This patch sets the default to `golang:latest` to pick the latest version,
which should be fine for this (until we get a linter recommending not
to use `:latest`).

Signed-off-by: Sebastiaan van Stijn <[email protected]>
(cherry picked from commit 9c73210)
Signed-off-by: Sebastiaan van Stijn <[email protected]>
@thaJeztah thaJeztah self-assigned this Sep 4, 2024
@thaJeztah thaJeztah requested a review from vvoland September 4, 2024 11:52
@vvoland vvoland merged commit e1be6f6 into docker:27.x Sep 4, 2024
7 checks passed
@thaJeztah thaJeztah deleted the 27.x_backport_fix_dockerfile_linting branch September 4, 2024 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants