From 21e956d9024ed334c450093c49c99a0cd50e3dc4 Mon Sep 17 00:00:00 2001 From: Dimitrios Vasilas Date: Fri, 15 May 2026 10:33:17 +0300 Subject: [PATCH] WKBCH-26: Launch vault via node instead of yarn start Vault 7.89.0 ships an .npmrc referencing ${NODE_AUTH_TOKEN} for build-time package authentication. Invoking yarn at container start makes yarn read that file and abort with 'Failed to replace env in config: ${NODE_AUTH_TOKEN}' because the variable is unset at runtime. Match the production Vault and MetaData pattern by launching the node entry point directly. This is what 'yarn start' resolves to (see Vault's package.json) and avoids reading the .npmrc altogether. --- templates/global/docker-compose.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/global/docker-compose.yaml b/templates/global/docker-compose.yaml index d296f3d..ea96d02 100644 --- a/templates/global/docker-compose.yaml +++ b/templates/global/docker-compose.yaml @@ -120,7 +120,7 @@ services: image: ${VAULT_IMAGE} container_name: workbench-vault network_mode: host - command: sh -c "chmod 400 tests/utils/keyfile && yarn start" + command: sh -c "chmod 400 tests/utils/keyfile && node --max-http-header-size=32768 vaultd.js" environment: VAULT_DB_BACKEND: LEVELDB volumes: