Container #2160
container.yml
on: schedule
Matrix: Build and push containers image to GitHub Packages
Annotations
3 errors and 6 warnings
|
Build and push containers image to GitHub Packages (Dockerfile-Fedora-latest, fedora:latest)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c dnf -y install --setopt=install_weak_deps=False asciidoc bash-completion biosdevname bluez btrfs-progs busybox bzip2 cifs-utils cryptsetup dash dbus-daemon device-mapper-multipath dhcp-client dhcp-server dmraid e2fsprogs f2fs-tools fcoe-utils fuse3 gcc git iproute iputils iscsi-initiator-utils kbd kernel kmod-devel libkcapi-hmaccalc libselinux-utils lvm2 lzop make mdadm memstrack mksh nbd ndctl NetworkManager nfs-utils ntfs-3g ntfsprogs nvme-cli parted pcsc-lite pigz qemu-system-x86-core rng-tools rpm-build sbsigntools scsi-target-utils ShellCheck shfmt squashfs-tools strace sudo systemd-boot-unsigned systemd-networkd systemd-resolved tar tcpdump tpm2-tools wget which xz && dnf -y remove dracut --noautoremove && dnf -y update && dnf clean all" did not complete successfully: exit code: 1
|
|
Build and push containers image to GitHub Packages (Dockerfile-Debian, debian:latest)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c apt-get update -y -qq && apt-get upgrade -y -qq && apt-get install -y -qq --no-install-recommends dracut && DEBIAN_FRONTEND=noninteractive apt-get install -y -qq --no-install-recommends -o Dpkg::Use-Pty=0 asciidoc astyle btrfs-progs busybox-static bzip2 ca-certificates console-setup cpio cryptsetup curl dash debhelper debhelper-compat dmraid docbook docbook-xml docbook-xsl fdisk g++ gawk git iputils-arping iputils-ping isc-dhcp-client isc-dhcp-server kmod less libdmraid-dev libkmod-dev linux-image-generic lvm2 make mdadm multipath-tools nbd-client nbd-server network-manager nfs-kernel-server ntfs-3g open-iscsi ovmf parted pigz pkg-config procps qemu-system-x86 quilt shellcheck squashfs-tools strace sudo systemd-boot-efi tcpdump tgt thin-provisioning-tools vim wget && apt-get clean && dpkg -P --force-depends dracut dracut-core initramfs-tools-core" did not complete successfully: exit code: 100
|
|
Build and push containers image to GitHub Packages (Dockerfile-Gentoo, gentoo:latest)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c echo 'sys-apps/systemd-utils boot' > /etc/portage/package.use/systemd-utils && emerge -qv sys-apps/systemd-utils" did not complete successfully: exit code: 1
|
|
Build and push containers image to GitHub Packages (Dockerfile-Fedora-latest, fedora:latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2, docker/setup-buildx-action@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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 and push containers image to GitHub Packages (Dockerfile-Debian, debian:latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2, docker/setup-buildx-action@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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 and push containers image to GitHub Packages (Dockerfile-Gentoo, gentoo:latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2, docker/setup-buildx-action@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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 and push containers image to GitHub Packages (Dockerfile-Arch, arch:latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2, docker/setup-buildx-action@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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 and push containers image to GitHub Packages (Dockerfile-Ubuntu, ubuntu:latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2, docker/setup-buildx-action@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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 and push containers image to GitHub Packages (Dockerfile-OpenSuse-latest, opensuse:latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2, docker/setup-buildx-action@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|