buildx bake failed with: ERROR: target rust-log-service: failed to solve: process "/bin/sh -c if [ \"$ENABLE_AVX512\" = \"1\" ]; then export CXXFLAGS=\"-mavx512f -mavx512dq -mavx512bw -mavx512vl\" && export CFLAGS=\"-mavx512f -mavx512dq -mavx512bw -mavx512vl\" && export RUSTFLAGS=\"${RUSTFLAGS} -C target-feature=+avx,+fma\" && echo \"Building with AVX512 optimizations for hnswlib and AVX for Rust\"; else echo \"Building without AVX512 optimizations\"; fi && build_target=$( [ \"${ADDRESS_SANITIZER}\" = \"1\" ] && echo '--target x86_64-unknown-linux-gnu' || echo '' ) && release_flag=$( [ \"$RELEASE_MODE\" = \"1\" ] && echo '--release' || echo '' ) && cargo build ${build_target} --workspace $(printf -- '--exclude %s ' $EXCLUDED_PACKAGES) ${release_flag} && if [ -n \"$LOG_SERVICE_CARGO_FEATURES\" ]; then cargo build ${build_target} -p chroma-log-service --bin log_service --features \"$LOG_SERVICE_CARGO_FEATURES\" ${release_flag}; fi && build_dir=$( [ \"$RELEASE_MODE\" = \"1\" ] && echo release || echo debug ) && build_dir=$( [ \"${ADDRESS_SANITIZER}\" = \"1\" ] && echo \"x86_64-unknown-linux-gnu/${build_dir}\" || echo \"${build_dir}\" ) && for bin in chroma garbage_collector_service chroma-load log_service heap_tender_service query_service compaction_service sysdb_service spanner_migration; do mv \"target/${build_dir}/${bin}\" \"./${bin}\"; done" did not complete successfully: exit code: 101

Process completed with exit code 101.

Process completed with exit code 1.

Process completed with exit code 1.

Cleanup failed: Failed to unmount sticky disk: Failed to unmount /var/lib/buildkit after 3 attempts: Command failed: sudo umount "/var/lib/buildkit" umount: /var/lib/buildkit: target is busy.

buildx bake failed with: ERROR: target rust-log-service: failed to solve: process "/bin/sh -c if [ \"$ENABLE_AVX512\" = \"1\" ]; then export CXXFLAGS=\"-mavx512f -mavx512dq -mavx512bw -mavx512vl\" && export CFLAGS=\"-mavx512f -mavx512dq -mavx512bw -mavx512vl\" && export RUSTFLAGS=\"${RUSTFLAGS} -C target-feature=+avx,+fma\" && echo \"Building with AVX512 optimizations for hnswlib and AVX for Rust\"; else echo \"Building without AVX512 optimizations\"; fi && build_target=$( [ \"${ADDRESS_SANITIZER}\" = \"1\" ] && echo '--target x86_64-unknown-linux-gnu' || echo '' ) && release_flag=$( [ \"$RELEASE_MODE\" = \"1\" ] && echo '--release' || echo '' ) && cargo build ${build_target} --workspace $(printf -- '--exclude %s ' $EXCLUDED_PACKAGES) ${release_flag} && if [ -n \"$LOG_SERVICE_CARGO_FEATURES\" ]; then cargo build ${build_target} -p chroma-log-service --bin log_service --features \"$LOG_SERVICE_CARGO_FEATURES\" ${release_flag}; fi && build_dir=$( [ \"$RELEASE_MODE\" = \"1\" ] && echo release || echo debug ) && build_dir=$( [ \"${ADDRESS_SANITIZER}\" = \"1\" ] && echo \"x86_64-unknown-linux-gnu/${build_dir}\" || echo \"${build_dir}\" ) && for bin in chroma garbage_collector_service chroma-load log_service heap_tender_service query_service compaction_service sysdb_service spanner_migration; do mv \"target/${build_dir}/${bin}\" \"./${bin}\"; done" did not complete successfully: exit code: 101

Process completed with exit code 1.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dorny/paths-filter@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: marocchino/sticky-pull-request-comment@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/

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/setup-python@v5, actions/upload-artifact@v4, astral-sh/setup-uv@v6. 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/

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/bake-action@v5. 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/

Skipping sticky disk commit due to previous step failures

- Step: unknown (failed)

Found 3 failed/cancelled steps in previous workflow steps

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, arduino/setup-protoc@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, arduino/setup-protoc@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, arduino/setup-protoc@v3, astral-sh/setup-uv@v6. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, arduino/setup-protoc@v3, pnpm/action-setup@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/

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/setup-go@v5, actions/upload-artifact@v4, docker/bake-action@v5, docker/login-action@v2.1.0. 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/

Skipping sticky disk commit due to previous step failures

- Step: unknown (failed)

Found 5 failed/cancelled steps in previous workflow steps

Expose ID not found in state, skipping sticky disk commit

Unmount failed, retrying (2/3)...

Unmount failed, retrying (1/3)...

⚠ /var/lib/buildkit/history.db: Integrity check failed: Command failed: sudo systemd-run --scope --quiet -p MemoryMax=512M -p RuntimeMaxSec=6s bbolt check "/var/lib/buildkit/history.db" 2>&1

⚠ /var/lib/buildkit/cache.db: Integrity check failed: Command failed: sudo systemd-run --scope --quiet -p MemoryMax=512M -p RuntimeMaxSec=6s bbolt check "/var/lib/buildkit/cache.db" 2>&1