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.

Sign up for GitHub

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

Bump almalinux/9-base from 9.4-20240923 to 9.5-20241118 #236

Merged
merged 1 commit into from
Nov 21, 2024
Merged

Bump almalinux/9-base from 9.4-20240923 to 9.5-20241118 #236

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Dockerfile.almalinux
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
FROM almalinux/9-base:9.4-20240923
FROM almalinux/9-base:9.5-20241118

LABEL org.opencontainers.image.title="haxorof/ansible-core" \
org.opencontainers.image.description="Ansible Core + additions" \
Expand All @@ -7,8 +7,8 @@
ARG docker_version
ARG gosu_version

ENV LANG C.UTF-8

Check warning on line 10 in Dockerfile.almalinux

View workflow job for this annotation

GitHub Actions / build_push (almalinux, v2.15)

Legacy key/value format with whitespace separator should not be used 

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in Dockerfile.almalinux

View workflow job for this annotation

GitHub Actions / build_push (almalinux, v2.16)

Legacy key/value format with whitespace separator should not be used 

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in Dockerfile.almalinux

View workflow job for this annotation

GitHub Actions / build_push (almalinux, v2.17)

Legacy key/value format with whitespace separator should not be used 

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
ENV LC_ALL C.UTF-8

Check warning on line 11 in Dockerfile.almalinux

View workflow job for this annotation

GitHub Actions / build_push (almalinux, v2.15)

Legacy key/value format with whitespace separator should not be used 

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 11 in Dockerfile.almalinux

View workflow job for this annotation

GitHub Actions / build_push (almalinux, v2.16)

Legacy key/value format with whitespace separator should not be used 

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 11 in Dockerfile.almalinux

View workflow job for this annotation

GitHub Actions / build_push (almalinux, v2.17)

Legacy key/value format with whitespace separator should not be used 

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
ENV VIRTUAL_ENV=/.env
ENV PATH=$VIRTUAL_ENV/bin:$PATH

Expand Down
Loading