Skip to content

Commit

Permalink
feat: adds Node.js 22 support (#720)
Browse files Browse the repository at this point in the history
  • Loading branch information
timbru31 authored Oct 25, 2024
1 parent 570906c commit 3a03e53
Show file tree
Hide file tree
Showing 19 changed files with 322 additions and 33 deletions.
60 changes: 50 additions & 10 deletions .github/workflows/buildx.yml
Original file line number Diff line number Diff line change
Expand Up @@ -26,13 +26,13 @@ jobs:
platforms: linux/amd64,linux/arm64,linux/ppc64le,linux/s390x,linux/386,linux/arm/v7,linux/arm/v6

- path: 3.2/18
tags: "3.2 3.2-18 3.2-hydrogen"
tags: "3.2-18 3.2-hydrogen"
platforms: linux/amd64,linux/arm64,linux/arm/v7
- path: 3.2/18/slim
tags: "3.2-slim 3.2-slim-18 3.2-slim-hydrogen"
tags: "3.2-slim-18 3.2-slim-hydrogen"
platforms: linux/amd64,linux/arm64,linux/arm/v7
- path: 3.2/18/alpine
tags: "3.2-alpine 3.2-alpine-18 3.2-alpine-hydrogen"
tags: "3.2-alpine-18 3.2-alpine-hydrogen"
platforms: linux/amd64,linux/arm64,linux/ppc64le,linux/s390x,linux/386,linux/arm/v7,linux/arm/v6

- path: 3.3/18
Expand All @@ -56,23 +56,23 @@ jobs:
platforms: linux/amd64,linux/arm64,linux/ppc64le,linux/s390x,linux/386,linux/arm/v7,linux/arm/v6

- path: 3.1/20
tags: "3.1-20 3.1-iron"
tags: "3.1-20 3.1-iron 3.1"
platforms: linux/amd64,linux/arm64,linux/arm/v7
- path: 3.1/20/slim
tags: "3.1-slim-20 3.1-slim-iron"
tags: "3.1-slim-20 3.1-slim-iron 3.1-slim"
platforms: linux/amd64,linux/arm64,linux/arm/v7
- path: 3.1/20/alpine
tags: "3.1-alpine-20 3.1-alpine-iron"
tags: "3.1-alpine-20 3.1-alpine-iron 3.1-alpine"
platforms: linux/amd64,linux/arm64,linux/ppc64le,linux/s390x,linux/386,linux/arm/v7,linux/arm/v6

- path: 3.2/20
tags: "3.2 3.2-20 3.2-iron"
tags: "3.2-20 3.2-iron 3.2"
platforms: linux/amd64,linux/arm64,linux/arm/v7
- path: 3.2/20/slim
tags: "3.2-slim 3.2-slim-20 3.2-slim-iron"
tags: "3.2-slim-20 3.2-slim-iron 3.2-slim"
platforms: linux/amd64,linux/arm64,linux/arm/v7
- path: 3.2/20/alpine
tags: "3.2-alpine 3.2-alpine-20 3.2-alpine-iron"
tags: "3.2-alpine-20 3.2-alpine-iron 3.2-alpine"
platforms: linux/amd64,linux/arm64,linux/ppc64le,linux/s390x,linux/386,linux/arm/v7,linux/arm/v6

- path: 3.3/20
Expand All @@ -82,7 +82,7 @@ jobs:
tags: " 3.3-slim-20 3.3-slim-iron 3.3-slim 3-slim slim"
platforms: linux/amd64,linux/arm64,linux/arm/v7
- path: 3.3/20/alpine
tags: "3.3-alpine-20 3.3-alpine-iron 3.3-alpine 3-alpine alpine"
tags: "3.3-alpine-20 3.3-alpine-iron 3.3-alpine 3-alpine alpine"
platforms: linux/amd64,linux/arm64,linux/ppc64le,linux/s390x,linux/386,linux/arm/v7,linux/arm/v6

- path: 3.4/20
Expand All @@ -94,6 +94,46 @@ jobs:
- path: 3.4/20/alpine
tags: "3.4-alpine-20 3.4-alpine-iron 3.4-alpine"
platforms: linux/amd64,linux/arm64,linux/ppc64le,linux/s390x,linux/386,linux/arm/v7,linux/arm/v6

- path: 3.1/22
tags: "3.1-22 3.1-jod"
platforms: linux/amd64,linux/arm64,linux/arm/v7
- path: 3.1/22/slim
tags: "3.1-slim-22 3.1-slim-jod"
platforms: linux/amd64,linux/arm64,linux/arm/v7
- path: 3.1/22/alpine
tags: "3.1-alpine-22 3.1-alpine-jod"
platforms: linux/amd64,linux/arm64,linux/ppc64le,linux/s390x,linux/386,linux/arm/v7,linux/arm/v6

- path: 3.2/22
tags: "3.2-22 3.2-jod"
platforms: linux/amd64,linux/arm64,linux/arm/v7
- path: 3.2/22/slim
tags: "3.2-slim-22 3.2-slim-jod"
platforms: linux/amd64,linux/arm64,linux/arm/v7
- path: 3.2/22/alpine
tags: "3.2-alpine-22 3.2-alpine-jod"
platforms: linux/amd64,linux/arm64,linux/ppc64le,linux/s390x,linux/386,linux/arm/v7,linux/arm/v6

- path: 3.3/22
tags: "3.3-22 3.3-jod"
platforms: linux/amd64,linux/arm64,linux/arm/v7
- path: 3.3/22/slim
tags: "3.3-slim-22 3.3-slim-jod"
platforms: linux/amd64,linux/arm64,linux/arm/v7
- path: 3.3/22/alpine
tags: "3.3-alpine-22 3.3-alpine-jod"
platforms: linux/amd64,linux/arm64,linux/ppc64le,linux/s390x,linux/386,linux/arm/v7,linux/arm/v6

- path: 3.4/22
tags: "3.4-22 3.4-jod"
platforms: linux/amd64,linux/arm64,linux/arm/v7
- path: 3.4/22/slim
tags: "3.4-slim-22 3.4-slim-jod"
platforms: linux/amd64,linux/arm64,linux/arm/v7
- path: 3.4/22/alpine
tags: "3.4-alpine-22 3.4-alpine-jod"
platforms: linux/amd64,linux/arm64,linux/ppc64le,linux/s390x,linux/386,linux/arm/v7,linux/arm/v6
steps:
- name: Checkout
uses: actions/checkout@v4.2.2
Expand Down
28 changes: 28 additions & 0 deletions .github/workflows/dockerimage.yml
Original file line number Diff line number Diff line change
Expand Up @@ -70,6 +70,34 @@ jobs:
docker run -i $(docker build -q 3.4/20/slim) /bin/sh -c "ruby --version && node --version && npm --version"
echo "3.4 alpine with Node.js 20"
docker run -i $(docker build -q 3.4/20/alpine) /bin/sh -c "ruby --version && node --version && npm --version"
echo "3.1 with Node.js 22"
docker run -i $(docker build -q 3.1/22) /bin/sh -c "ruby --version && node --version && npm --version"
echo "3.1 slim with Node.js 22"
docker run -i $(docker build -q 3.1/22/slim) /bin/sh -c "ruby --version && node --version && npm --version"
echo "3.1 alpine with Node.js 22"
docker run -i $(docker build -q 3.1/22/alpine) /bin/sh -c "ruby --version && node --version && npm --version"
echo "3.2 with Node.js 22"
docker run -i $(docker build -q 3.2/22) /bin/sh -c "ruby --version && node --version && npm --version"
echo "3.2 slim with Node.js 22"
docker run -i $(docker build -q 3.2/22/slim) /bin/sh -c "ruby --version && node --version && npm --version"
echo "3.2 alpine with Node.js 22"
docker run -i $(docker build -q 3.2/22/alpine) /bin/sh -c "ruby --version && node --version && npm --version"
echo "3.3 with Node.js 22"
docker run -i $(docker build -q 3.3/22) /bin/sh -c "ruby --version && node --version && npm --version"
echo "3.3 slim with Node.js 22"
docker run -i $(docker build -q 3.3/22/slim) /bin/sh -c "ruby --version && node --version && npm --version"
echo "3.3 alpine with Node.js 22"
docker run -i $(docker build -q 3.3/22/alpine) /bin/sh -c "ruby --version && node --version && npm --version"
echo "3.4 with Node.js 22"
docker run -i $(docker build -q 3.4/22) /bin/sh -c "ruby --version && node --version && npm --version"
echo "3.4 slim with Node.js 22"
docker run -i $(docker build -q 3.4/22/slim) /bin/sh -c "ruby --version && node --version && npm --version"
echo "3.4 alpine with Node.js 22"
docker run -i $(docker build -q 3.4/22/alpine) /bin/sh -c "ruby --version && node --version && npm --version"
auto-merge:
runs-on: ubuntu-latest
needs: build
Expand Down
8 changes: 3 additions & 5 deletions 3.1/20/alpine/Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,8 @@ LABEL maintainer "Tim Brust <github@timbrust.de>"
ARG REFRESHED_AT
ENV REFRESHED_AT $REFRESHED_AT

Check warning on line 5 in 3.1/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/20/alpine, 3.1-alpine-20 3.1-alpine-iron 3.1-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.1/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/20/alpine, 3.1-alpine-20 3.1-alpine-iron 3.1-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.1/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/20/alpine, 3.1-alpine-20 3.1-alpine-iron 3.1-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.1/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/20/alpine, 3.1-alpine-20 3.1-alpine-iron 3.1-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.1/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/20/alpine, 3.1-alpine-20 3.1-alpine-iron 3.1-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.1/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/20/alpine, 3.1-alpine-20 3.1-alpine-iron 3.1-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.1/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/20/alpine, 3.1-alpine-20 3.1-alpine-iron 3.1-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.1/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/20/alpine, 3.1-alpine-20 3.1-alpine-iron 3.1-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.1/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/20/alpine, 3.1-alpine-20 3.1-alpine-iron 3.1-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.1/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/20/alpine, 3.1-alpine-20 3.1-alpine-iron 3.1-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.1/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/20/alpine, 3.1-alpine-20 3.1-alpine-iron 3.1-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.1/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/20/alpine, 3.1-alpine-20 3.1-alpine-iron 3.1-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.1/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/20/alpine, 3.1-alpine-20 3.1-alpine-iron 3.1-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.1/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/20/alpine, 3.1-alpine-20 3.1-alpine-iron 3.1-alpine, linux/amd64,linux/arm64,linux/pp...

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/

RUN echo @edge https://dl-cdn.alpinelinux.org/alpine/edge/community >> /etc/apk/repositories \
&& echo @edge https://dl-cdn.alpinelinux.org/alpine/edge/main >> /etc/apk/repositories \
&& apk -U upgrade \
RUN apk -U upgrade \
&& apk add --no-cache \
nodejs@edge \
npm@edge \
nodejs \
npm \
yarn
19 changes: 19 additions & 0 deletions 3.1/22/Dockerfile
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
FROM ruby:3.1
LABEL maintainer "Tim Brust <github@timbrust.de>"

Check warning on line 2 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

ARG REFRESHED_AT
ENV REFRESHED_AT $REFRESHED_AT

Check warning on line 5 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22, 3.1-22 3.1-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 NODE_MAJOR=22

SHELL ["/bin/bash", "-o", "pipefail", "-c"]

RUN printf 'Package: nodejs\nPin: origin deb.nodesource.com\nPin-Priority: 1001' > /etc/apt/preferences.d/nodesource \
&& mkdir -p /etc/apt/keyrings \
&& curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg \
&& echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_$NODE_MAJOR.x nodistro main" | tee /etc/apt/sources.list.d/nodesource.list \
&& apt-get update -qq && apt-get install -qq --no-install-recommends \
nodejs \
&& apt-get upgrade -qq \
&& apt-get clean \
&& rm -rf /var/lib/apt/lists/*\
&& npm install -g yarn@1
13 changes: 13 additions & 0 deletions 3.1/22/alpine/Dockerfile
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
FROM ruby:3.1-alpine
LABEL maintainer "Tim Brust <github@timbrust.de>"

Check warning on line 2 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

ARG REFRESHED_AT
ENV REFRESHED_AT $REFRESHED_AT

Check warning on line 5 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.1/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/alpine, 3.1-alpine-22 3.1-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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/

RUN echo @edge https://dl-cdn.alpinelinux.org/alpine/edge/community >> /etc/apk/repositories \
&& echo @edge https://dl-cdn.alpinelinux.org/alpine/edge/main >> /etc/apk/repositories \
&& apk -U upgrade \
&& apk add --no-cache \
nodejs-current@edge \
npm@edge \
yarn
25 changes: 25 additions & 0 deletions 3.1/22/slim/Dockerfile
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
FROM ruby:3.1-slim
LABEL maintainer "Tim Brust <github@timbrust.de>"

Check warning on line 2 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

ARG REFRESHED_AT
ENV REFRESHED_AT $REFRESHED_AT

Check warning on line 5 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.1/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/22/slim, 3.1-slim-22 3.1-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 NODE_MAJOR=22

# hadolint ignore=DL3009
RUN apt-get update -qq && apt-get install -qq --no-install-recommends \
curl \
gnupg2 \
libatomic1

SHELL ["/bin/bash", "-o", "pipefail", "-c"]

RUN printf 'Package: nodejs\nPin: origin deb.nodesource.com\nPin-Priority: 1001' > /etc/apt/preferences.d/nodesource \
&& mkdir -p /etc/apt/keyrings \
&& curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg \
&& echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_$NODE_MAJOR.x nodistro main" | tee /etc/apt/sources.list.d/nodesource.list \
&& apt-get update -qq && apt-get install -qq --no-install-recommends \
nodejs \
&& apt-get upgrade -qq \
&& apt-get clean \
&& rm -rf /var/lib/apt/lists/*\
&& npm install -g yarn@1
8 changes: 3 additions & 5 deletions 3.2/20/alpine/Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,8 @@ LABEL maintainer "Tim Brust <github@timbrust.de>"
ARG REFRESHED_AT
ENV REFRESHED_AT $REFRESHED_AT

Check warning on line 5 in 3.2/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/20/alpine, 3.2-alpine-20 3.2-alpine-iron 3.2-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.2/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/20/alpine, 3.2-alpine-20 3.2-alpine-iron 3.2-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.2/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/20/alpine, 3.2-alpine-20 3.2-alpine-iron 3.2-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.2/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/20/alpine, 3.2-alpine-20 3.2-alpine-iron 3.2-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.2/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/20/alpine, 3.2-alpine-20 3.2-alpine-iron 3.2-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.2/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/20/alpine, 3.2-alpine-20 3.2-alpine-iron 3.2-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.2/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/20/alpine, 3.2-alpine-20 3.2-alpine-iron 3.2-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.2/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/20/alpine, 3.2-alpine-20 3.2-alpine-iron 3.2-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.2/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/20/alpine, 3.2-alpine-20 3.2-alpine-iron 3.2-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.2/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/20/alpine, 3.2-alpine-20 3.2-alpine-iron 3.2-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.2/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/20/alpine, 3.2-alpine-20 3.2-alpine-iron 3.2-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.2/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/20/alpine, 3.2-alpine-20 3.2-alpine-iron 3.2-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.2/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/20/alpine, 3.2-alpine-20 3.2-alpine-iron 3.2-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.2/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/20/alpine, 3.2-alpine-20 3.2-alpine-iron 3.2-alpine, linux/amd64,linux/arm64,linux/pp...

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/

RUN echo @edge https://dl-cdn.alpinelinux.org/alpine/edge/community >> /etc/apk/repositories \
&& echo @edge https://dl-cdn.alpinelinux.org/alpine/edge/main >> /etc/apk/repositories \
&& apk -U upgrade \
RUN apk -U upgrade \
&& apk add --no-cache \
nodejs@edge \
npm@edge \
nodejs \
npm \
yarn
19 changes: 19 additions & 0 deletions 3.2/22/Dockerfile
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
FROM ruby:3.2
LABEL maintainer "Tim Brust <github@timbrust.de>"

Check warning on line 2 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

ARG REFRESHED_AT
ENV REFRESHED_AT $REFRESHED_AT

Check warning on line 5 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22, 3.2-22 3.2-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 NODE_MAJOR=22

SHELL ["/bin/bash", "-o", "pipefail", "-c"]

RUN printf 'Package: nodejs\nPin: origin deb.nodesource.com\nPin-Priority: 1001' > /etc/apt/preferences.d/nodesource \
&& mkdir -p /etc/apt/keyrings \
&& curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg \
&& echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_$NODE_MAJOR.x nodistro main" | tee /etc/apt/sources.list.d/nodesource.list \
&& apt-get update -qq && apt-get install -qq --no-install-recommends \
nodejs \
&& apt-get upgrade -qq \
&& apt-get clean \
&& rm -rf /var/lib/apt/lists/*\
&& npm install -g yarn@1
13 changes: 13 additions & 0 deletions 3.2/22/alpine/Dockerfile
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
FROM ruby:3.2-alpine
LABEL maintainer "Tim Brust <github@timbrust.de>"

Check warning on line 2 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

ARG REFRESHED_AT
ENV REFRESHED_AT $REFRESHED_AT

Check warning on line 5 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.2/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/alpine, 3.2-alpine-22 3.2-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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/

RUN echo @edge https://dl-cdn.alpinelinux.org/alpine/edge/community >> /etc/apk/repositories \
&& echo @edge https://dl-cdn.alpinelinux.org/alpine/edge/main >> /etc/apk/repositories \
&& apk -U upgrade \
&& apk add --no-cache \
nodejs-current@edge \
npm@edge \
yarn
25 changes: 25 additions & 0 deletions 3.2/22/slim/Dockerfile
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
FROM ruby:3.2-slim
LABEL maintainer "Tim Brust <github@timbrust.de>"

Check warning on line 2 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

ARG REFRESHED_AT
ENV REFRESHED_AT $REFRESHED_AT

Check warning on line 5 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.2/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.2/22/slim, 3.2-slim-22 3.2-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 NODE_MAJOR=22

# hadolint ignore=DL3009
RUN apt-get update -qq && apt-get install -qq --no-install-recommends \
curl \
gnupg2 \
libatomic1

SHELL ["/bin/bash", "-o", "pipefail", "-c"]

RUN printf 'Package: nodejs\nPin: origin deb.nodesource.com\nPin-Priority: 1001' > /etc/apt/preferences.d/nodesource \
&& mkdir -p /etc/apt/keyrings \
&& curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg \
&& echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_$NODE_MAJOR.x nodistro main" | tee /etc/apt/sources.list.d/nodesource.list \
&& apt-get update -qq && apt-get install -qq --no-install-recommends \
nodejs \
&& apt-get upgrade -qq \
&& apt-get clean \
&& rm -rf /var/lib/apt/lists/*\
&& npm install -g yarn@1
8 changes: 3 additions & 5 deletions 3.3/20/alpine/Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,8 @@ LABEL maintainer "Tim Brust <github@timbrust.de>"
ARG REFRESHED_AT
ENV REFRESHED_AT $REFRESHED_AT

Check warning on line 5 in 3.3/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/20/alpine, 3.3-alpine-20 3.3-alpine-iron 3.3-alpine 3-alpine alpine, linux/amd64,linu...

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 5 in 3.3/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/20/alpine, 3.3-alpine-20 3.3-alpine-iron 3.3-alpine 3-alpine alpine, linux/amd64,linu...

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 5 in 3.3/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/20/alpine, 3.3-alpine-20 3.3-alpine-iron 3.3-alpine 3-alpine alpine, linux/amd64,linu...

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 5 in 3.3/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/20/alpine, 3.3-alpine-20 3.3-alpine-iron 3.3-alpine 3-alpine alpine, linux/amd64,linu...

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 5 in 3.3/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/20/alpine, 3.3-alpine-20 3.3-alpine-iron 3.3-alpine 3-alpine alpine, linux/amd64,linu...

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 5 in 3.3/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/20/alpine, 3.3-alpine-20 3.3-alpine-iron 3.3-alpine 3-alpine alpine, linux/amd64,linu...

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 5 in 3.3/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/20/alpine, 3.3-alpine-20 3.3-alpine-iron 3.3-alpine 3-alpine alpine, linux/amd64,linu...

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 5 in 3.3/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/20/alpine, 3.3-alpine-20 3.3-alpine-iron 3.3-alpine 3-alpine alpine, linux/amd64,linu...

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 5 in 3.3/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/20/alpine, 3.3-alpine-20 3.3-alpine-iron 3.3-alpine 3-alpine alpine, linux/amd64,linu...

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 5 in 3.3/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/20/alpine, 3.3-alpine-20 3.3-alpine-iron 3.3-alpine 3-alpine alpine, linux/amd64,linu...

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 5 in 3.3/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/20/alpine, 3.3-alpine-20 3.3-alpine-iron 3.3-alpine 3-alpine alpine, linux/amd64,linu...

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 5 in 3.3/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/20/alpine, 3.3-alpine-20 3.3-alpine-iron 3.3-alpine 3-alpine alpine, linux/amd64,linu...

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 5 in 3.3/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/20/alpine, 3.3-alpine-20 3.3-alpine-iron 3.3-alpine 3-alpine alpine, linux/amd64,linu...

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/

RUN echo @edge https://dl-cdn.alpinelinux.org/alpine/edge/community >> /etc/apk/repositories \
&& echo @edge https://dl-cdn.alpinelinux.org/alpine/edge/main >> /etc/apk/repositories \
&& apk -U upgrade \
RUN apk -U upgrade \
&& apk add --no-cache \
nodejs@edge \
npm@edge \
nodejs \
npm \
yarn
19 changes: 19 additions & 0 deletions 3.3/22/Dockerfile
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
FROM ruby:3.3
LABEL maintainer "Tim Brust <github@timbrust.de>"

Check warning on line 2 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

ARG REFRESHED_AT
ENV REFRESHED_AT $REFRESHED_AT

Check warning on line 5 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22, 3.3-22 3.3-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 NODE_MAJOR=22

SHELL ["/bin/bash", "-o", "pipefail", "-c"]

RUN printf 'Package: nodejs\nPin: origin deb.nodesource.com\nPin-Priority: 1001' > /etc/apt/preferences.d/nodesource \
&& mkdir -p /etc/apt/keyrings \
&& curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg \
&& echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_$NODE_MAJOR.x nodistro main" | tee /etc/apt/sources.list.d/nodesource.list \
&& apt-get update -qq && apt-get install -qq --no-install-recommends \
nodejs \
&& apt-get upgrade -qq \
&& apt-get clean \
&& rm -rf /var/lib/apt/lists/*\
&& npm install -g yarn@1
13 changes: 13 additions & 0 deletions 3.3/22/alpine/Dockerfile
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
FROM ruby:3.3-alpine
LABEL maintainer "Tim Brust <github@timbrust.de>"

Check warning on line 2 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

Check warning on line 2 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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

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

ARG REFRESHED_AT
ENV REFRESHED_AT $REFRESHED_AT

Check warning on line 5 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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 5 in 3.3/22/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/alpine, 3.3-alpine-22 3.3-alpine-jod, linux/amd64,linux/arm64,linux/ppc64le,linux/...

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/

RUN echo @edge https://dl-cdn.alpinelinux.org/alpine/edge/community >> /etc/apk/repositories \
&& echo @edge https://dl-cdn.alpinelinux.org/alpine/edge/main >> /etc/apk/repositories \
&& apk -U upgrade \
&& apk add --no-cache \
nodejs-current@edge \
npm@edge \
yarn
25 changes: 25 additions & 0 deletions 3.3/22/slim/Dockerfile
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
FROM ruby:3.3-slim
LABEL maintainer "Tim Brust <github@timbrust.de>"

Check warning on line 2 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

ARG REFRESHED_AT
ENV REFRESHED_AT $REFRESHED_AT

Check warning on line 5 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.3/22/slim/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.3/22/slim, 3.3-slim-22 3.3-slim-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 NODE_MAJOR=22

# hadolint ignore=DL3009
RUN apt-get update -qq && apt-get install -qq --no-install-recommends \
curl \
gnupg2 \
libatomic1

SHELL ["/bin/bash", "-o", "pipefail", "-c"]

RUN printf 'Package: nodejs\nPin: origin deb.nodesource.com\nPin-Priority: 1001' > /etc/apt/preferences.d/nodesource \
&& mkdir -p /etc/apt/keyrings \
&& curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg \
&& echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_$NODE_MAJOR.x nodistro main" | tee /etc/apt/sources.list.d/nodesource.list \
&& apt-get update -qq && apt-get install -qq --no-install-recommends \
nodejs \
&& apt-get upgrade -qq \
&& apt-get clean \
&& rm -rf /var/lib/apt/lists/*\
&& npm install -g yarn@1
8 changes: 3 additions & 5 deletions 3.4/20/alpine/Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,8 @@ LABEL maintainer "Tim Brust <github@timbrust.de>"
ARG REFRESHED_AT
ENV REFRESHED_AT $REFRESHED_AT

Check warning on line 5 in 3.4/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/20/alpine, 3.4-alpine-20 3.4-alpine-iron 3.4-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.4/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/20/alpine, 3.4-alpine-20 3.4-alpine-iron 3.4-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.4/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/20/alpine, 3.4-alpine-20 3.4-alpine-iron 3.4-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.4/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/20/alpine, 3.4-alpine-20 3.4-alpine-iron 3.4-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.4/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/20/alpine, 3.4-alpine-20 3.4-alpine-iron 3.4-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.4/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/20/alpine, 3.4-alpine-20 3.4-alpine-iron 3.4-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.4/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/20/alpine, 3.4-alpine-20 3.4-alpine-iron 3.4-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.4/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/20/alpine, 3.4-alpine-20 3.4-alpine-iron 3.4-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.4/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/20/alpine, 3.4-alpine-20 3.4-alpine-iron 3.4-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.4/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/20/alpine, 3.4-alpine-20 3.4-alpine-iron 3.4-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.4/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/20/alpine, 3.4-alpine-20 3.4-alpine-iron 3.4-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.4/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/20/alpine, 3.4-alpine-20 3.4-alpine-iron 3.4-alpine, linux/amd64,linux/arm64,linux/pp...

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 5 in 3.4/20/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/20/alpine, 3.4-alpine-20 3.4-alpine-iron 3.4-alpine, linux/amd64,linux/arm64,linux/pp...

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/

RUN echo @edge https://dl-cdn.alpinelinux.org/alpine/edge/community >> /etc/apk/repositories \
&& echo @edge https://dl-cdn.alpinelinux.org/alpine/edge/main >> /etc/apk/repositories \
&& apk -U upgrade \
RUN apk -U upgrade \
&& apk add --no-cache \
nodejs@edge \
npm@edge \
nodejs \
npm \
yarn
19 changes: 19 additions & 0 deletions 3.4/22/Dockerfile
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
FROM ruby:3.4-rc
LABEL maintainer "Tim Brust <github@timbrust.de>"

Check warning on line 2 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

Check warning on line 2 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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

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

ARG REFRESHED_AT
ENV REFRESHED_AT $REFRESHED_AT

Check warning on line 5 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 5 in 3.4/22/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.4/22, 3.4-22 3.4-jod, linux/amd64,linux/arm64,linux/arm/v7)

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 NODE_MAJOR=22

SHELL ["/bin/bash", "-o", "pipefail", "-c"]

RUN printf 'Package: nodejs\nPin: origin deb.nodesource.com\nPin-Priority: 1001' > /etc/apt/preferences.d/nodesource \
&& mkdir -p /etc/apt/keyrings \
&& curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg \
&& echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_$NODE_MAJOR.x nodistro main" | tee /etc/apt/sources.list.d/nodesource.list \
&& apt-get update -qq && apt-get install -qq --no-install-recommends \
nodejs \
&& apt-get upgrade -qq \
&& apt-get clean \
&& rm -rf /var/lib/apt/lists/*\
&& npm install -g yarn@1
Loading

0 comments on commit 3a03e53

Please sign in to comment.