Skip to content

Updated latest version of container resolver to fix the vulnerability(AST-123397) #728

Updated latest version of container resolver to fix the vulnerability(AST-123397)

Updated latest version of container resolver to fix the vulnerability(AST-123397) #728

Triggered via pull request March 25, 2026 09:14
Status Failure
Total duration 2h 22m 55s
Artifacts

ci-tests.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 23 warnings
govulncheck
wrappers.ContainerResolverImpl.Resolve calls containerResolver.ContainersResolver.Resolve, which eventually calls binary.NewELFPackageCataloger
govulncheck
wrappers.ContainerResolverImpl.Resolve calls containerResolver.ContainersResolver.Resolve, which eventually calls binary.NewClassifierCataloger
govulncheck
wrappers.ContainerResolverImpl.Resolve calls containerResolver.ContainersResolver.Resolve, which eventually calls binary.DefaultClassifierCatalogerConfig
govulncheck
wrappers.init calls containerResolver.init, which eventually calls artifact.init
govulncheck
wrappers.ContainerResolverImpl.Resolve calls containerResolver.ContainersResolver.Resolve, which eventually calls artifact.IDByHash
govulncheck
kerberos.ValidateKerberosSetup calls config.Load, which eventually calls arch.newScanner
govulncheck
wrappers.init calls containerResolver.init, which eventually calls arch.init
govulncheck
wrappers.ContainerResolverImpl.Resolve calls containerResolver.ContainersResolver.Resolve, which eventually calls arch.NewDBCataloger
govulncheck
wrappers.init calls containerResolver.init, which eventually calls alpine.init
govulncheck
wrappers.ContainerResolverImpl.Resolve calls containerResolver.ContainersResolver.Resolve, which eventually calls alpine.NewDBCataloger
integration-tests
Process completed with exit code ***.
govulncheck
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-go@v4.0.0. 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/
govulncheck
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>09KfDaQAAAADM31+FA4USRqQMHnex0MlkQ0hJMzBFREdFMDExMgBFZGdl
govulncheck
Failed to restore: Cache service responded with 400
scan Docker Image with Trivy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@722adc63f1aa60a57ec37892e133b1d319cae598, docker/login-action@49ed152c8eca782a232dede0303416e8f356c37b, docker/setup-buildx-action@cf09c5c41b299b55c366aff30022701412eb6ab0. 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/
scan Docker Image with Trivy
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
scan Docker Image with Trivy
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
scan Docker Image with Trivy
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
scan Docker Image with Trivy
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
scan Docker Image with Trivy
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
scan Docker Image with Trivy
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
scan Docker Image with Trivy
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
scan Docker Image with Trivy
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
scan Docker Image with Trivy
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@1e31de5234b9f8995739874a8ce0492dc87873e2, actions/setup-go@4d34df0c2316fe8122ab82dc22947d607c0c91f9. 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/
lint
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0gKjDaQAAAABVRXuJf4w8R7csZ9BO+jZ+Q0hJMzBFREdFMDExMgBFZGdl
lint
Unexpected input(s) 'skip-pkg-cache', valid inputs are ['version', 'version-file', 'install-mode', 'install-only', 'working-directory', 'github-token', 'verify', 'only-new-issues', 'args', 'skip-cache', 'skip-save-cache', 'cache-invalidation-interval', 'problem-matchers', 'debug', 'experimental']
lint
Unexpected input(s) 'skip-pkg-cache', valid inputs are ['version', 'version-file', 'install-mode', 'install-only', 'working-directory', 'github-token', 'verify', 'only-new-issues', 'args', 'skip-cache', 'skip-save-cache', 'cache-invalidation-interval', 'problem-matchers', 'debug', 'experimental']
lint
Failed to restore: Cache service responded with 400
unit-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@1e31de5234b9f8995739874a8ce0492dc87873e2, actions/setup-go@4d34df0c2316fe8122ab82dc22947d607c0c91f9. 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/
unit-tests
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0I7DDaQAAAAAx2KdkWHepSLGyuZmkauO8UEhMMzBFREdFMDExNwBFZGdl
unit-tests
Failed to restore: Cache service responded with 400
integration-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@***e3***de5234b9f8995739874a8ce0492dc87873e2, actions/setup-go@4d34df0c23***6fe8***22ab82dc22947d607c0c9***f9. 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-***9-deprecation-of-node-20-on-github-actions-runners/
integration-tests
Failed to restore: Cache service responded with 400