Skip to content

SCHEDULE - Automatic builds #33

SCHEDULE - Automatic builds

SCHEDULE - Automatic builds #33

Triggered via schedule March 13, 2026 23:26
Status Success
Total duration 2h 32m 56s
Artifacts 24

build_schedule.yml

on: schedule
prepare  /  prepare
24s
prepare / prepare
Matrix: build / build
cleanup  /  remove_artifacts
3s
cleanup / remove_artifacts
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 47 warnings
build / build (alpine, 3.19, false, false, linux/amd64,linux/arm64, faflopza)
buildx failed with: ERROR: failed to build: failed to solve: process "/dev/.buildkit_qemu_emulator /bin/bash -c echo \"\" && source /container/base/functions/container/build && case \"$(container_info distro)\" in alpine ) if [ \"$(grep -o '^PRETTY_NAME=.*' /etc/os-release | cut -d = -f2)\" = '\"Alpine Linux edge\"' ] ; then apk add merge-usr ; merge-usr ; fi ; case \"$(container_info variant)\" in 3.[5-9] | 3.1[1-6] ) alpine_ssl=libressl ; ;; 3.1[7-9] | 3.2[0-9] ) alpine_ssl=openssl ; ;; esac ; case \"$(container_info variant)\" in 3.[5-8] ) zstd_pacakge=\"\" ; ;; *) zstd_package=\"zstd\" ; ;; esac ; IMAGE_BASE_BUILD_DEPS_ALPINE=\" gettext musl-dev \" ; IMAGE_BASE_RUN_DEPS_ALPINE=\" acl ${alpine_ssl} bash ${busybox_extras} ca-certificates curl git grep libgcc $(apk search libssl1* -q) nano sudo tzdata xz ${zstd_package} \" ; ;; debian ) IMAGE_BASE_BUILD_DEPS_DEBIAN=\" \" ; IMAGE_BASE_RUN_DEPS_DEBIAN=\" acl apt-transport-https apt-utils aptitude busybox-static ca-certificates curl dirmngr gettext git gnupg nano procps sudo tar tzdata zstd \" ; ;; esac ; package update && package upgrade && package install IMAGE_BASE_BUILD_DEPS IMAGE_BASE_RUN_DEPS && mkdir -p /etc/bash/ /run/secrets /usr/local/bin /usr/local/sbin && if [ -e \"/usr/bin/envsubst\" ] ; then mv /usr/bin/envsubst /usr/local/bin/envsubst ; fi && container_build_log base && rm -rf /etc/timezone && ln -snf /usr/share/zoneinfo/${TIMEZONE} /etc/localtime && echo \"${TIMEZONE}\" > /etc/timezone && case \"$(container_info distro)\" in \"debian\" ) dpkg-reconfigure -f noninteractive tzdata ; rm -rf
build / build (alpine, 3.22, false, false, linux/amd64,linux/arm64, faflopza)
buildx failed with: ERROR: failed to build: failed to solve: process "/dev/.buildkit_qemu_emulator /bin/bash -c echo \"\" && source /container/base/functions/container/build && case \"$(container_info distro)\" in alpine ) if [ \"$(grep -o '^PRETTY_NAME=.*' /etc/os-release | cut -d = -f2)\" = '\"Alpine Linux edge\"' ] ; then apk add merge-usr ; merge-usr ; fi ; case \"$(container_info variant)\" in 3.[5-9] | 3.1[1-6] ) alpine_ssl=libressl ; ;; 3.1[7-9] | 3.2[0-9] ) alpine_ssl=openssl ; ;; esac ; case \"$(container_info variant)\" in 3.[5-8] ) zstd_pacakge=\"\" ; ;; *) zstd_package=\"zstd\" ; ;; esac ; IMAGE_BASE_BUILD_DEPS_ALPINE=\" gettext musl-dev \" ; IMAGE_BASE_RUN_DEPS_ALPINE=\" acl ${alpine_ssl} bash ${busybox_extras} ca-certificates curl git grep libgcc $(apk search libssl1* -q) nano sudo tzdata xz ${zstd_package} \" ; ;; debian ) IMAGE_BASE_BUILD_DEPS_DEBIAN=\" \" ; IMAGE_BASE_RUN_DEPS_DEBIAN=\" acl apt-transport-https apt-utils aptitude busybox-static ca-certificates curl dirmngr gettext git gnupg nano procps sudo tar tzdata zstd \" ; ;; esac ; package update && package upgrade && package install IMAGE_BASE_BUILD_DEPS IMAGE_BASE_RUN_DEPS && mkdir -p /etc/bash/ /run/secrets /usr/local/bin /usr/local/sbin && if [ -e \"/usr/bin/envsubst\" ] ; then mv /usr/bin/envsubst /usr/local/bin/envsubst ; fi && container_build_log base && rm -rf /etc/timezone && ln -snf /usr/share/zoneinfo/${TIMEZONE} /etc/localtime && echo \"${TIMEZONE}\" > /etc/timezone && case \"$(container_info distro)\" in \"debian\" ) dpkg-reconfigure -f noninteractive tzdata ; rm -rf
prepare / prepare
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build / build (alpine, 3.12, false, false, linux/amd64,linux/arm64, core)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (alpine, 3.16, false, false, linux/amd64,linux/arm64, core)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (alpine, 3.22, false, false, linux/amd64,linux/arm64, core)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (alpine, 3.19, false, false, linux/amd64,linux/arm64, core)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (alpine, 3.23, true, true, linux/amd64,linux/arm64, core)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (alpine, 3.15, false, false, linux/amd64,linux/arm64, core)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (debian, bookworm, false, false, linux/amd64,linux/arm64, core)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (debian, trixie, false, true, linux/amd64,linux/arm64, core)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (alpine, 3.12, false, false, linux/amd64,linux/arm64, faflopza)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (alpine, 3.12, false, false, linux/amd64,linux/arm64, faflopzaze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (alpine, 3.19, false, false, linux/amd64,linux/arm64, faflopza)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build / build (alpine, 3.22, false, false, linux/amd64,linux/arm64, faflopza)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build / build (alpine, 3.15, false, false, linux/amd64,linux/arm64, faflopza)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (alpine, 3.15, false, false, linux/amd64,linux/arm64, faflopzaze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (alpine, 3.16, false, false, linux/amd64,linux/arm64, faflopza)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (alpine, 3.16, false, false, linux/amd64,linux/arm64, faflopzaze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (debian, bookworm, false, false, linux/amd64,linux/arm64, faflopza)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (debian, bookworm, false, false, linux/amd64,linux/arm64, faflopzaze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (debian, trixie, false, true, linux/amd64,linux/arm64, faflopza)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (alpine, 3.23, true, true, linux/amd64,linux/arm64, faflopza)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (alpine, 3.22, false, false, linux/amd64,linux/arm64, faflopzaze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (alpine, 3.19, false, false, linux/amd64,linux/arm64, faflopzaze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (alpine, 3.23, true, true, linux/amd64,linux/arm64, faflopzaze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
build / build (debian, trixie, false, true, linux/amd64,linux/arm64, faflopzaze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Default value for global ARG results in an empty or invalid base image name: Containerfile#L9
InvalidDefaultArgInFrom: Default value for ARG docker.io/${DISTRO}:${DISTRO_VARIANT} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/

Artifacts

Produced during runtime
Name Size Digest
nfrastack~container-base~9PEJKH.dockerbuild
92.4 KB
sha256:d8a8f502d1923481f4befe7bbe0510adf78e6f67d9ea581b14dbd9f43e446900
nfrastack~container-base~D2BO1H.dockerbuild
765 KB
sha256:fff869232d6e5156b4d75c9140733ba9e5e7c391de9946604ffd038d74eda278
nfrastack~container-base~H5QGD3.dockerbuild
283 KB
sha256:4a0f1f26e5280334000f5a4045faa8b1de630f60570bb8854473ed76ae12a376
nfrastack~container-base~I2K19D.dockerbuild
748 KB
sha256:8aa2d02993d32d7b73cc93d704c71405062dea829b6f06af4b3632309790305f
nfrastack~container-base~IWJS6D.dockerbuild
253 KB
sha256:5db82218a24bc07ceeb85f529ad47d9fef58ded26dfaa450f5157e7229f50bd4
nfrastack~container-base~JFN6MC.dockerbuild
516 KB
sha256:6fd7abb871f8cf6e3a1c7d0ea757f26ef87d4731d2199c24519a921974db620e
nfrastack~container-base~KULCYZ.dockerbuild
726 KB
sha256:549dd86b0bf1c3275751363252747a67aa1791891d9b7775f21541720846a94e
nfrastack~container-base~KZKGF5.dockerbuild
128 KB
sha256:303dd5bff67d814e575198f69f290dee5936173c212a6b124802c618087ccc91
nfrastack~container-base~M51J39.dockerbuild
253 KB
sha256:e643bfa7ed50d413634a4b2383cd5cf3c5cf7669e8f46deac6dc2f49a673a376
nfrastack~container-base~NJV9UX.dockerbuild
282 KB
sha256:2b76ed1c1a9177baacb71e4cd9133e6b46a785f50da795f7fc5453972b7f7519
nfrastack~container-base~O08Z72.dockerbuild
350 KB
sha256:f3a5dd635e189a7af356171677ea2ee85db28ae92cab9adf5072d6de9537a5c8
nfrastack~container-base~P45GDA.dockerbuild
765 KB
sha256:251120ee75feab92697f3cf21878368a0d8aed68b4b10dbd29d25f6e275c3a00
nfrastack~container-base~PVPO07.dockerbuild
800 KB
sha256:2cf564b2f71930b79219b6b68e5ea267855945a7e9db2d03e0f7c9cb3246f67d
nfrastack~container-base~Q4F01M.dockerbuild
96.7 KB
sha256:f75d62b5f0980e7054e1c146e8166ae1227cd75caab41af5757ca860f4782759
nfrastack~container-base~Q7CPOA.dockerbuild
91 KB
sha256:d2d839e1aa4483a4b9586b8edb9ebab2b3b84e086d8535bb8afde989890b8fdd
nfrastack~container-base~R9MYQ4.dockerbuild
141 KB
sha256:14b7be8c37a278d7165908c9adca287b319c86e8e441936790ac8338a96630c3
nfrastack~container-base~U3H9AH.dockerbuild
260 KB
sha256:855fe04be3cd283f7901b63cca7925b5eff03d01ecf78cf26a846707b9a0335e
nfrastack~container-base~U3XDFD.dockerbuild
528 KB
sha256:46ab5b808b5df45f33be5f7de76c9494185184a229a541b72bfcbd3cb22d95fa
nfrastack~container-base~U4SWE6.dockerbuild
265 KB
sha256:d55bbad34464114e3e96294563024113992187c3c736e258c53b75ad2a420c05
nfrastack~container-base~UBCT34.dockerbuild
478 KB
sha256:e47b97700c262694654a6e093d4ea0dd477dd964268982c0bf8f1fcbffd11d68
nfrastack~container-base~VTG7Y7.dockerbuild
544 KB
sha256:d60e4c05b156bc5581c724e9a51469cd85353aaa18d7c1fd4d2e39dd480e1855
nfrastack~container-base~WLDOFP.dockerbuild
515 KB
sha256:081c62a25e5aaae26b41350b377e1eace591744d5d0480ec364812fbad4f1bfc
nfrastack~container-base~YHC24M.dockerbuild
377 KB
sha256:60da0dac5f6fb88b779fef6bd3519d220b50288f7021a8961589cdad16602dd1
nfrastack~container-base~ZZZR6S.dockerbuild
945 KB
sha256:fa50f9db5c6763d81e58ee6c0399de6edcd6f9fbf0de9be19417a8a4f4d57157