Skip to content

Docker Build

Docker Build #272

Triggered via schedule March 15, 2026 05:10
Status Failure
Total duration 37s
Artifacts

docker-build.yml

on: schedule
docker-ccip-plugins  /  init
7s
docker-ccip-plugins / init
docker-ccip  /  init
7s
docker-ccip / init
docker-core-plugins-testing  /  init
8s
docker-core-plugins-testing / init
docker-core-plugins  /  init
7s
docker-core-plugins / init
docker-core  /  init
7s
docker-core / init
docker-ccip-plugins  /  set-build-matrix
3s
docker-ccip-plugins / set-build-matrix
docker-ccip  /  set-build-matrix
2s
docker-ccip / set-build-matrix
docker-core-plugins-testing  /  set-build-matrix
4s
docker-core-plugins-testing / set-build-matrix
docker-core-plugins  /  set-build-matrix
2s
docker-core-plugins / set-build-matrix
docker-core  /  set-build-matrix
2s
docker-core / set-build-matrix
Matrix: docker-ccip-plugins / build-publish
Matrix: docker-ccip / build-publish
Matrix: docker-core-plugins-testing / build-publish
Matrix: docker-core-plugins / build-publish
Matrix: docker-core / build-publish
docker-ccip-plugins  /  docker-manifest
0s
docker-ccip-plugins / docker-manifest
docker-ccip  /  docker-manifest
docker-ccip / docker-manifest
docker-core-plugins-testing  /  docker-manifest
0s
docker-core-plugins-testing / docker-manifest
docker-core-plugins  /  docker-manifest
docker-core-plugins / docker-manifest
docker-core  /  docker-manifest
docker-core / docker-manifest
deploy-nightly-ccip
deploy-nightly-ccip
call-cre-workflow-don-benchmark  /  workflow-don-benchmark
call-cre-workflow-don-benchmark / workflow-don-benchmark
call-cre-local-env-tests  /  changes
call-cre-local-env-tests / changes
deploy-nightly-core
0s
deploy-nightly-core
call-cre-local-env-tests  /  test-cli
call-cre-local-env-tests / test-cli
call-cre-local-env-tests  /  Notify about local env startup failure
call-cre-local-env-tests / Notify about local env startup failure
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 15 warnings
docker-core-plugins / build-publish-arm64
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
docker-core / build-publish-amd64
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
docker-core-plugins-testing / build-publish-arm64
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
docker-core-plugins-testing / build-publish-amd64
The strategy configuration was canceled because "docker-core-plugins-testing.build-publish.ubuntu-24_04-arm_arm64" failed
docker-core-plugins-testing / build-publish-amd64
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
docker-core / build-publish-arm64
The strategy configuration was canceled because "docker-core.build-publish.ubuntu-24_04_amd64" failed
docker-core / build-publish-arm64
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
docker-ccip / build-publish-arm64
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
docker-ccip / build-publish-amd64
The strategy configuration was canceled because "docker-ccip.build-publish.ubuntu-24_04-arm_arm64" failed
docker-ccip / build-publish-amd64
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
docker-ccip-plugins / build-publish-arm64
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
docker-core-plugins / build-publish-amd64
The strategy configuration was canceled because "docker-core-plugins.build-publish.ubuntu-24_04-arm_arm64" failed
docker-core-plugins / build-publish-amd64
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
docker-ccip-plugins / build-publish-amd64
The strategy configuration was canceled because "docker-ccip-plugins.build-publish.ubuntu-24_04-arm_arm64" failed
docker-ccip-plugins / build-publish-amd64
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
docker-core / init
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 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/
docker-ccip-plugins / init
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 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/
docker-ccip / init
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 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/
docker-core-plugins / init
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 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/
docker-core-plugins-testing / init
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 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/
docker-core-plugins / build-publish-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@ececac1a45f3b08a01d2dd070d28d111c5fe6722. 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/
docker-core / build-publish-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@ececac1a45f3b08a01d2dd070d28d111c5fe6722. 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/
docker-core-plugins-testing / build-publish-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@ececac1a45f3b08a01d2dd070d28d111c5fe6722. 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/
docker-core-plugins-testing / build-publish-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@ececac1a45f3b08a01d2dd070d28d111c5fe6722. 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/
docker-core / build-publish-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@ececac1a45f3b08a01d2dd070d28d111c5fe6722. 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/
docker-ccip / build-publish-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@ececac1a45f3b08a01d2dd070d28d111c5fe6722. 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/
docker-ccip / build-publish-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@ececac1a45f3b08a01d2dd070d28d111c5fe6722. 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/
docker-ccip-plugins / build-publish-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@ececac1a45f3b08a01d2dd070d28d111c5fe6722. 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/
docker-core-plugins / build-publish-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@ececac1a45f3b08a01d2dd070d28d111c5fe6722. 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/
docker-ccip-plugins / build-publish-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@ececac1a45f3b08a01d2dd070d28d111c5fe6722. 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/