ci: Set up Docker Buildx #44
LazuliKaoAnnotations
7 errors and 4 warnings
|
Release Windows Docker image (2022, servercore)
ERROR: no matching manifest for windows(10.0.20348)/amd64 in the manifest list entries
|
|
Release Windows Docker image (2022, nanoserver)
The strategy configuration was canceled because "release_docker_windows._2022_servercore" failed
|
|
Release Windows Docker image (2022, nanoserver)
ERROR: no matching manifest for windows(10.0.20348)/amd64 in the manifest list entries
|
|
Release Windows Docker image (2025, nanoserver)
The strategy configuration was canceled because "release_docker_windows._2022_servercore" failed
|
|
Release Windows Docker image (2025, nanoserver)
ERROR: no matching manifest for windows(10.0.26100)/amd64 in the manifest list entries
|
|
Release Windows Docker image (2025, servercore)
The strategy configuration was canceled because "release_docker_windows._2022_servercore" failed
|
|
Release Windows Docker image (2025, servercore)
ERROR: no matching manifest for windows(10.0.26100)/amd64 in the manifest list entries
|
|
Release Windows Docker image (2022, servercore)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
Release Windows Docker image (2022, nanoserver)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
Release Windows Docker image (2025, nanoserver)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
Release Windows Docker image (2025, servercore)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|