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

Jump to bottom

fix #297 show curl errors #300

Merged
merged 1 commit into from
Aug 27, 2024
Merged

fix #297 show curl errors #300

Show file tree
Hide file tree
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
4 changes: 2 additions & 2 deletions eclipse-temurin/Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,13 +10,13 @@

# Env variables
ARG SCALA_VERSION
ENV SCALA_VERSION ${SCALA_VERSION:-2.13.10}

Check warning on line 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-21.0.2_13)

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 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-22_36)

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 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-17.0.10_7)

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 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-21.0.2_13)

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 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-17.0.10_7)

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 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-21.0.2_13)

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 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-17.0.10_7)

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 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-22_36)

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 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-22_36)

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 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-21.0.2_13)

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 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-22_36)

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 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-17.0.10_7)

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/
ARG SBT_VERSION
ENV SBT_VERSION ${SBT_VERSION:-1.6.2}

Check warning on line 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-21.0.2_13)

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 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-22_36)

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 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-17.0.10_7)

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 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-21.0.2_13)

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 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-17.0.10_7)

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 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-21.0.2_13)

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 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-17.0.10_7)

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 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-22_36)

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 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-22_36)

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 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-21.0.2_13)

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 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-22_36)

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 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-17.0.10_7)

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/
ARG USER_ID
ENV USER_ID ${USER_ID:-1001}

Check warning on line 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-21.0.2_13)

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 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-22_36)

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 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-17.0.10_7)

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 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-21.0.2_13)

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 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-17.0.10_7)

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 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-21.0.2_13)

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 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-17.0.10_7)

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 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-22_36)

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 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-22_36)

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 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-21.0.2_13)

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 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-22_36)

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 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-17.0.10_7)

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/
ARG GROUP_ID
ENV GROUP_ID ${GROUP_ID:-1001}

Check warning on line 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-21.0.2_13)

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 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-22_36)

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 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-17.0.10_7)

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 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-21.0.2_13)

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 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-17.0.10_7)

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 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-21.0.2_13)

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 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-17.0.10_7)

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 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-22_36)

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 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-22_36)

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 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-21.0.2_13)

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 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-22_36)

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 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-17.0.10_7)

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/

# Install dependencies
# curl for downloading sbt and scala
Expand All @@ -28,7 +28,7 @@

# Install sbt
RUN \
curl -fsL "https://github.com/sbt/sbt/releases/download/v$SBT_VERSION/sbt-$SBT_VERSION.tgz" | tar xfz - -C /usr/share && \
curl -fsL --show-error "https://github.com/sbt/sbt/releases/download/v$SBT_VERSION/sbt-$SBT_VERSION.tgz" | tar xfz - -C /usr/share && \
chown -R root:root /usr/share/sbt && \
chmod -R 755 /usr/share/sbt && \
ln -s /usr/share/sbt/bin/sbt /usr/local/bin/sbt
Expand All @@ -39,7 +39,7 @@
"3"*) URL=https://github.com/lampepfl/dotty/releases/download/$SCALA_VERSION/scala3-$SCALA_VERSION.tar.gz SCALA_DIR=/usr/share/scala3-$SCALA_VERSION ;; \
*) URL=https://downloads.typesafe.com/scala/$SCALA_VERSION/scala-$SCALA_VERSION.tgz SCALA_DIR=/usr/share/scala-$SCALA_VERSION ;; \
esac && \
curl -fsL $URL | tar xfz - -C /usr/share && \
curl -fsL --show-error $URL | tar xfz - -C /usr/share && \
mv $SCALA_DIR /usr/share/scala && \
chown -R root:root /usr/share/scala && \
chmod -R 755 /usr/share/scala && \
Expand Down Expand Up @@ -88,2 +88,2 @@

CMD sbt
4 changes: 2 additions & 2 deletions eclipse-temurin/alpine.Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Use a multi-stage build to reduce the size of the final image
ARG BASE_IMAGE_TAG
FROM eclipse-temurin:${BASE_IMAGE_TAG:-21.0.2_13-jdk-alpine} as builder

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-alpine-22_36)

The 'as' keyword should match the case of the 'from' keyword 

FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-alpine-17.0.10_7)

The 'as' keyword should match the case of the 'from' keyword 

FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-alpine-21.0.2_13)

The 'as' keyword should match the case of the 'from' keyword 

FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-alpine-17.0.10_7)

The 'as' keyword should match the case of the 'from' keyword 

FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-alpine-22_36)

The 'as' keyword should match the case of the 'from' keyword 

FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-alpine-21.0.2_13)

The 'as' keyword should match the case of the 'from' keyword 

FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-alpine-17.0.10_7)

The 'as' keyword should match the case of the 'from' keyword 

FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-alpine-21.0.2_13)

The 'as' keyword should match the case of the 'from' keyword 

FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-alpine-22_36)

The 'as' keyword should match the case of the 'from' keyword 

FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-alpine-21.0.2_13)

The 'as' keyword should match the case of the 'from' keyword 

FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-alpine-22_36)

The 'as' keyword should match the case of the 'from' keyword 

FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-alpine-17.0.10_7)

The 'as' keyword should match the case of the 'from' keyword 

FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

ARG SCALA_VERSION=3.4.0
ARG SBT_VERSION=1.9.9
Expand All @@ -18,7 +18,7 @@
"3"*) URL=https://github.com/lampepfl/dotty/releases/download/$SCALA_VERSION/scala3-$SCALA_VERSION.tar.gz SCALA_DIR=scala3-$SCALA_VERSION ;; \
*) URL=https://downloads.typesafe.com/scala/$SCALA_VERSION/scala-$SCALA_VERSION.tgz SCALA_DIR=scala-$SCALA_VERSION ;; \
esac && \
curl -fsL $URL | tar xfz - -C /usr/share && \
curl -fsL --show-error $URL | tar xfz - -C /usr/share && \
mv /usr/share/$SCALA_DIR $SCALA_HOME && \
ln -s "$SCALA_HOME/bin/"* "/usr/bin/" && \
update-ca-certificates && \
Expand All @@ -31,7 +31,7 @@

# Install sbt
RUN \
curl -fsL https://github.com/sbt/sbt/releases/download/v$SBT_VERSION/sbt-$SBT_VERSION.tgz | tar xfz - -C /usr/local && \
curl -fsL --show-error https://github.com/sbt/sbt/releases/download/v$SBT_VERSION/sbt-$SBT_VERSION.tgz | tar xfz - -C /usr/local && \
$(mv /usr/local/sbt-launcher-packaging-$SBT_VERSION /usr/local/sbt || true) && \
ln -s /usr/local/sbt/bin/* /usr/local/bin/ && \
sbt -Dsbt.rootdir=true -batch sbtVersion && \
Expand Down Expand Up @@ -88,4 +88,4 @@
## -w /home/sbtuser
WORKDIR /root

CMD sbt

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-alpine-22_36)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-alpine-17.0.10_7)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-alpine-21.0.2_13)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-alpine-17.0.10_7)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-alpine-22_36)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-alpine-21.0.2_13)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-alpine-17.0.10_7)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-alpine-21.0.2_13)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-alpine-22_36)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-alpine-21.0.2_13)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-alpine-22_36)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-alpine-17.0.10_7)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
4 changes: 2 additions & 2 deletions graalvm-ce/Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,18 +10,18 @@

# Env variables
ARG SCALA_VERSION
ENV SCALA_VERSION ${SCALA_VERSION:-2.13.10}

Check warning on line 13 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-ce-22.3.3-b1-java17)

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 13 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-ce-22.3.3-b1-java17)

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 13 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-ce-22.3.3-b1-java17)

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/
ARG SBT_VERSION
ENV SBT_VERSION ${SBT_VERSION:-1.6.2}

Check warning on line 15 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-ce-22.3.3-b1-java17)

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 15 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-ce-22.3.3-b1-java17)

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 15 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-ce-22.3.3-b1-java17)

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 JAVA_OPTS -XX:+UseG1GC

Check warning on line 16 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-ce-22.3.3-b1-java17)

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 16 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-ce-22.3.3-b1-java17)

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 16 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-ce-22.3.3-b1-java17)

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/
ARG USER_ID
ENV USER_ID ${USER_ID:-1001}

Check warning on line 18 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-ce-22.3.3-b1-java17)

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 18 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-ce-22.3.3-b1-java17)

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 18 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-ce-22.3.3-b1-java17)

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/
ARG GROUP_ID
ENV GROUP_ID ${GROUP_ID:-1001}

Check warning on line 20 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-ce-22.3.3-b1-java17)

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 20 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-ce-22.3.3-b1-java17)

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 20 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-ce-22.3.3-b1-java17)

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/

# Install sbt
RUN \
curl -fsL "https://github.com/sbt/sbt/releases/download/v$SBT_VERSION/sbt-$SBT_VERSION.tgz" | tar xfz - -C /usr/share && \
curl -fsL --show-error "https://github.com/sbt/sbt/releases/download/v$SBT_VERSION/sbt-$SBT_VERSION.tgz" | tar xfz - -C /usr/share && \
chown -R root:root /usr/share/sbt && \
chmod -R 755 /usr/share/sbt && \
ln -s /usr/share/sbt/bin/sbt /usr/local/bin/sbt
Expand All @@ -33,7 +33,7 @@
"3"*) URL=https://github.com/lampepfl/dotty/releases/download/$SCALA_VERSION/scala3-$SCALA_VERSION.tar.gz SCALA_DIR=/usr/share/scala3-$SCALA_VERSION ;; \
*) URL=https://downloads.typesafe.com/scala/$SCALA_VERSION/scala-$SCALA_VERSION.tgz SCALA_DIR=/usr/share/scala-$SCALA_VERSION ;; \
esac && \
curl -fsL $URL | tar xfz - -C /usr/share && \
curl -fsL --show-error $URL | tar xfz - -C /usr/share && \
mv $SCALA_DIR /usr/share/scala && \
chown -R root:root /usr/share/scala && \
chmod -R 755 /usr/share/scala && \
Expand Down Expand Up @@ -77,4 +77,4 @@
## -w /home/sbtuser
WORKDIR /root

CMD sbt

Check warning on line 80 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-ce-22.3.3-b1-java17)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 80 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-ce-22.3.3-b1-java17)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 80 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-ce-22.3.3-b1-java17)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
4 changes: 2 additions & 2 deletions graalvm-community/Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,18 +10,18 @@

# Env variables
ARG SCALA_VERSION
ENV SCALA_VERSION ${SCALA_VERSION:-2.13.12}

Check warning on line 13 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-22.0.1)

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 13 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-21.0.2)

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 13 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-22.0.1)

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 13 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-21.0.2)

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 13 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-21.0.2)

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 13 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-22.0.1)

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/
ARG SBT_VERSION
ENV SBT_VERSION ${SBT_VERSION:-1.9.7}

Check warning on line 15 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-22.0.1)

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 15 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-21.0.2)

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 15 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-22.0.1)

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 15 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-21.0.2)

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 15 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-21.0.2)

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 15 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-22.0.1)

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 JAVA_OPTS -XX:+UseG1GC

Check warning on line 16 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-22.0.1)

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 16 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-21.0.2)

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 16 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-22.0.1)

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 16 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-21.0.2)

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 16 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-21.0.2)

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 16 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-22.0.1)

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/
ARG USER_ID
ENV USER_ID ${USER_ID:-1001}

Check warning on line 18 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-22.0.1)

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 18 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-21.0.2)

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 18 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-22.0.1)

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 18 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-21.0.2)

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 18 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-21.0.2)

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 18 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-22.0.1)

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/
ARG GROUP_ID
ENV GROUP_ID ${GROUP_ID:-1001}

Check warning on line 20 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-22.0.1)

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 20 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-21.0.2)

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 20 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-22.0.1)

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 20 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-21.0.2)

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 20 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-21.0.2)

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 20 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-22.0.1)

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/

# Install sbt
RUN \
curl -fsL "https://github.com/sbt/sbt/releases/download/v$SBT_VERSION/sbt-$SBT_VERSION.tgz" | tar xfz - -C /usr/share && \
curl -fsL --show-error "https://github.com/sbt/sbt/releases/download/v$SBT_VERSION/sbt-$SBT_VERSION.tgz" | tar xfz - -C /usr/share && \
chown -R root:root /usr/share/sbt && \
chmod -R 755 /usr/share/sbt && \
ln -s /usr/share/sbt/bin/sbt /usr/local/bin/sbt
Expand All @@ -33,7 +33,7 @@
"3"*) URL=https://github.com/lampepfl/dotty/releases/download/$SCALA_VERSION/scala3-$SCALA_VERSION.tar.gz SCALA_DIR=/usr/share/scala3-$SCALA_VERSION ;; \
*) URL=https://downloads.typesafe.com/scala/$SCALA_VERSION/scala-$SCALA_VERSION.tgz SCALA_DIR=/usr/share/scala-$SCALA_VERSION ;; \
esac && \
curl -fsL $URL | tar xfz - -C /usr/share && \
curl -fsL --show-error $URL | tar xfz - -C /usr/share && \
mv $SCALA_DIR /usr/share/scala && \
chown -R root:root /usr/share/scala && \
chmod -R 755 /usr/share/scala && \
Expand Down Expand Up @@ -77,4 +77,4 @@
## -w /home/sbtuser
WORKDIR /root

CMD sbt

Check warning on line 80 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-22.0.1)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 80 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-21.0.2)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 80 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-22.0.1)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 80 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-21.0.2)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 80 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-21.0.2)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 80 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-22.0.1)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals 

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/