feat: add patch for _tkinter compilation with gcc 14+ and update Dock… #44
scc-twAnnotations
20 errors and 64 warnings
|
build (x86_64, 2.7)
Process completed with exit code 1.
|
|
build (x86_64, 3.14t)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c set -eux && ./build_python.sh && ./install_pip.sh" did not complete successfully: exit code: 2
|
|
build (x86_64, 3.13)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c set -eux && ./build_python.sh && ./install_pip.sh" did not complete successfully: exit code: 2
|
|
build (x86_64, 3.13t)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c set -eux && ./build_python.sh && ./install_pip.sh" did not complete successfully: exit code: 2
|
|
build (x86, 2.7)
Process completed with exit code 1.
|
|
build (x86_64, 3.15t)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c set -eux && ./build_python.sh && ./install_pip.sh" did not complete successfully: exit code: 2
|
|
build (x86_64, 3.15)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c set -eux && ./build_python.sh && ./install_pip.sh" did not complete successfully: exit code: 2
|
|
build (x86_64, 3.10)
Process completed with exit code 1.
|
|
build (x86_64, 3.11)
Process completed with exit code 1.
|
|
build (x86, 3.13)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c set -eux && ./build_python.sh && ./install_pip.sh" did not complete successfully: exit code: 2
|
|
build (x86, 3.15t)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c set -eux && ./build_python.sh && ./install_pip.sh" did not complete successfully: exit code: 2
|
|
build (x86_64, 3.14)
Process completed with exit code 1.
|
|
build (x86_64, 3.12)
Process completed with exit code 1.
|
|
build (x86, 3.13t)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c set -eux && ./build_python.sh && ./install_pip.sh" did not complete successfully: exit code: 2
|
|
build (x86, 3.10)
Process completed with exit code 1.
|
|
build (x86, 3.11)
Process completed with exit code 1.
|
|
build (x86, 3.12)
Process completed with exit code 1.
|
|
build (x86, 3.14t)
Process completed with exit code 1.
|
|
build (x86, 3.14)
Process completed with exit code 1.
|
|
build (x86, 3.15)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c set -eux && ./build_python.sh && ./install_pip.sh" did not complete successfully: exit code: 2
|
|
build (x86_64, 2.7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
FROM --platform flag should not use a constant value:
2.7/x86_64/Dockerfile#L199
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
2.7/x86_64/Dockerfile#L164
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
2.7/x86_64/Dockerfile#L43
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
2.7/x86_64/Dockerfile#L1
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
build (x86_64, 3.14t)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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 (x86_64, 3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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 (x86_64, 3.13t)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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 (x86, 2.7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
FROM --platform flag should not use a constant value:
2.7/x86/Dockerfile#L199
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
2.7/x86/Dockerfile#L164
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
2.7/x86/Dockerfile#L43
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
2.7/x86/Dockerfile#L1
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
build (x86_64, 3.15t)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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 (x86_64, 3.15)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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 (x86_64, 3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
FROM --platform flag should not use a constant value:
3.10/x86_64/Dockerfile#L31
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.10/x86_64/Dockerfile#L1
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.10/x86_64/Dockerfile#L206
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.10/x86_64/Dockerfile#L169
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
build (x86_64, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
FROM --platform flag should not use a constant value:
3.11/x86_64/Dockerfile#L206
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.11/x86_64/Dockerfile#L169
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.11/x86_64/Dockerfile#L31
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.11/x86_64/Dockerfile#L1
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
build (x86, 3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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 (x86, 3.15t)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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 (x86_64, 3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
FROM --platform flag should not use a constant value:
3.14/x86_64/Dockerfile#L31
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.14/x86_64/Dockerfile#L1
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.14/x86_64/Dockerfile#L213
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.14/x86_64/Dockerfile#L176
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
build (x86_64, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
FROM --platform flag should not use a constant value:
3.12/x86_64/Dockerfile#L169
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.12/x86_64/Dockerfile#L31
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.12/x86_64/Dockerfile#L1
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.12/x86_64/Dockerfile#L206
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
build (x86, 3.13t)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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 (x86, 3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
FROM --platform flag should not use a constant value:
3.10/x86/Dockerfile#L206
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.10/x86/Dockerfile#L169
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.10/x86/Dockerfile#L31
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.10/x86/Dockerfile#L1
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
build (x86, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
FROM --platform flag should not use a constant value:
3.11/x86/Dockerfile#L206
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.11/x86/Dockerfile#L169
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.11/x86/Dockerfile#L31
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.11/x86/Dockerfile#L1
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
build (x86, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
FROM --platform flag should not use a constant value:
3.12/x86/Dockerfile#L169
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.12/x86/Dockerfile#L31
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.12/x86/Dockerfile#L1
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.12/x86/Dockerfile#L206
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
build (x86, 3.14t)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
FROM --platform flag should not use a constant value:
3.14t/x86/Dockerfile#L214
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.14t/x86/Dockerfile#L177
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.14t/x86/Dockerfile#L31
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.14t/x86/Dockerfile#L1
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
build (x86, 3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
FROM --platform flag should not use a constant value:
3.14/x86/Dockerfile#L213
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.14/x86/Dockerfile#L176
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.14/x86/Dockerfile#L31
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
FROM --platform flag should not use a constant value:
3.14/x86/Dockerfile#L1
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/386"
More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
|
|
build (x86, 3.15)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
scc-tw~standalone-python~0EHJOC.dockerbuild
|
1.88 MB |
sha256:58dd16e3c9c8d92cf3779959aff24390aa4332b6fecccc50a5f7fedea42fe241
|
|
|
scc-tw~standalone-python~16T4NI.dockerbuild
|
1010 KB |
sha256:50f3c4a4fd10eb6860c1cb7f8ef6c22c111487aae63bc402f164792c2412ede5
|
|
|
scc-tw~standalone-python~16VU05.dockerbuild
|
1.93 MB |
sha256:989e503817d9c9c49d4e0f77cea68d453fbacdf8a3535762a3efee6547900eae
|
|
|
scc-tw~standalone-python~2QN2S4.dockerbuild
|
256 KB |
sha256:b181d2f2ecaf272c57da754361f328d9c08823cbd6a6a6973cc0e5de1c2ce817
|
|
|
scc-tw~standalone-python~3PO11P.dockerbuild
|
1.03 MB |
sha256:58e7fb43472996be25b8bceb86010877180a5b2b10b1b7dc959daa3fcc79c0ca
|
|
|
scc-tw~standalone-python~4KSLEI.dockerbuild
|
1.89 MB |
sha256:c6131954c7bf11354a025a1de68534fe58f4a8f0063af06ffbe0dac1c696190b
|
|
|
scc-tw~standalone-python~8EN4AE.dockerbuild
|
894 KB |
sha256:f5da0f4e285c76455d2c34630755f91bce05e9a69115bd163140643cf9a9566a
|
|
|
scc-tw~standalone-python~B58HMD.dockerbuild
|
1.92 MB |
sha256:008b0897900f7ef27cb75688a16551bbe671d6d51278c113414c92bcf1865cda
|
|
|
scc-tw~standalone-python~D9BIHH.dockerbuild
|
1.08 MB |
sha256:a19967eb112f8cc9e6a7412678c15503d5671d0ab734e1baa9658452088ce29b
|
|
|
scc-tw~standalone-python~F69RTF.dockerbuild
|
1.02 MB |
sha256:00e4a280af0a3f43f3d338e00dc5637e496eea85130cda89774f4c47b1bbaa0a
|
|
|
scc-tw~standalone-python~HITR1W.dockerbuild
|
1.05 MB |
sha256:4c7e1fac4aa52db99fdf981dfbe585cbc554b0805f64112056cdda62cd41efbe
|
|
|
scc-tw~standalone-python~JAXKVP.dockerbuild
|
1.08 MB |
sha256:e6ac18479da5f18a10c6e5a6e21b643088c7a47871266eb72418d8e65bd9fb6a
|
|
|
scc-tw~standalone-python~JZE2ND.dockerbuild
|
1.88 MB |
sha256:d171aba790ce0b7dd9d65ef4fb27f8148ab216f817827712c86ea2ac695c1247
|
|
|
scc-tw~standalone-python~M5KVMY.dockerbuild
|
914 KB |
sha256:118c81dc1e93bb4d152a19168bcfbeeb7740899f7b256f5071e030d029b13c4b
|
|
|
scc-tw~standalone-python~OTXN1G.dockerbuild
|
888 KB |
sha256:bb872bfc2f0ca2f59d56d2c26a50c3420313b921da739c4476346f7183ed7a48
|
|
|
scc-tw~standalone-python~R6GSUZ.dockerbuild
|
1.05 MB |
sha256:8ff9083ba912bf27b7da317ebded835b23416df78ab34a628b9ad1f3e7ac2835
|
|
|
scc-tw~standalone-python~RROHJW.dockerbuild
|
1000 KB |
sha256:e7178612a3bc63b36adcb1933bf293d57a58d81bd6c2fa134d35a9e0a8fa2761
|
|
|
scc-tw~standalone-python~S6O0BP.dockerbuild
|
1000 KB |
sha256:7165c7cd710ff08114addfde0bade4a699d90845821dc68c8e2712b16a5fd9bd
|
|
|
scc-tw~standalone-python~U8109W.dockerbuild
|
1000 KB |
sha256:7fa3e264d1b6259528c9664dbcd020d97ce26efcd6e39a726e314cc0f2d6ca2d
|
|
|
scc-tw~standalone-python~YH9W3C.dockerbuild
|
1.03 MB |
sha256:5b130f604b1afba19b08468f737afcf23b96d0a4d83091c6412d5efe8e537940
|
|