Error: URL /v1/sys/health not accessible after 60000ms ❯ packages/testcontainers/src/wait-strategies/http-wait-strategy.ts:133:15 ❯ IntervalRetry.retryUntil packages/testcontainers/src/common/retry.ts:49:16 ❯ HttpWaitStrategy.waitUntilReady packages/testcontainers/src/wait-strategies/http-wait-strategy.ts:83:5 ❯ waitForContainer packages/testcontainers/src/wait-strategies/wait-for-container.ts:17:5 ❯ VaultContainer.startContainer packages/testcontainers/src/generic-container/generic-container.ts:232:5 ❯ VaultContainer.start packages/modules/vault/src/vault-container.ts:69:21 ❯ packages/modules/vault/src/vault-container.test.ts:46:29

packages/modules/vault/src/vault-container.test.ts > VaultContainer > should execute init commands using vault CLI: packages/testcontainers/src/wait-strategies/http-wait-strategy.ts#L133

packages/modules/vault/src/vault-container.test.ts > VaultContainer > should start Vault and allow reading/writing secrets: packages/testcontainers/src/wait-strategies/http-wait-strategy.ts#L133

Tests (vault, 24.x, podman) / Run

Process completed with exit code 1.

packages/modules/vault/src/vault-container.test.ts > VaultContainer > should execute init commands using vault CLI: packages/testcontainers/src/wait-strategies/http-wait-strategy.ts#L133

packages/modules/vault/src/vault-container.test.ts > VaultContainer > should start Vault and allow reading/writing secrets: packages/testcontainers/src/wait-strategies/http-wait-strategy.ts#L133

Tests (vault, 22.x, podman) / Run

Process completed with exit code 1.

packages/modules/vault/src/vault-container.test.ts > VaultContainer > should execute init commands using vault CLI: packages/testcontainers/src/wait-strategies/http-wait-strategy.ts#L133

packages/modules/vault/src/vault-container.test.ts > VaultContainer > should start Vault and allow reading/writing secrets: packages/testcontainers/src/wait-strategies/http-wait-strategy.ts#L133

Tests (vault, 20.x, podman) / Run

Process completed with exit code 1.

packages/modules/vault/src/vault-container.test.ts > VaultContainer > should execute init commands using vault CLI: packages/testcontainers/src/wait-strategies/http-wait-strategy.ts#L133

packages/modules/vault/src/vault-container.test.ts > VaultContainer > should start Vault and allow reading/writing secrets: packages/testcontainers/src/wait-strategies/http-wait-strategy.ts#L133

Tests (vault, 20.x, docker) / Run

Process completed with exit code 1.

packages/modules/vault/src/vault-container.test.ts > VaultContainer > should execute init commands using vault CLI: packages/testcontainers/src/wait-strategies/http-wait-strategy.ts#L133

packages/modules/vault/src/vault-container.test.ts > VaultContainer > should start Vault and allow reading/writing secrets: packages/testcontainers/src/wait-strategies/http-wait-strategy.ts#L133

Tests (vault, 24.x, docker) / Run

Process completed with exit code 1.

packages/modules/vault/src/vault-container.test.ts > VaultContainer > should execute init commands using vault CLI: packages/testcontainers/src/wait-strategies/http-wait-strategy.ts#L133

packages/modules/vault/src/vault-container.test.ts > VaultContainer > should start Vault and allow reading/writing secrets: packages/testcontainers/src/wait-strategies/http-wait-strategy.ts#L133

Detect packages to check

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: tj-actions/changed-files@ed68ef82c095e0d48ec87eccea555d944a631a4c. 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/

Lint (redpanda)

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

Lint (weaviate)

Lint (vault)

Lint (ollama)

Lint (localstack)

Lint (mongodb)

Lint (cassandra)

Lint (cockroachdb)

Lint (elasticsearch)

Lint (arangodb)

Lint (s3mock)

Lint (opensearch)

Lint (gcloud)

Lint (selenium)

Lint (chromadb)

Lint (nats)

Compile (nats)

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

Compile (elasticsearch)