From f94d78b91324d87cc97d00d492e814459e6d4a5f Mon Sep 17 00:00:00 2001 From: Claude Date: Sun, 16 Nov 2025 14:37:49 +0000 Subject: [PATCH] Fix vault container startup issue Removed vault config volume mount that was conflicting with dev mode. Dev mode automatically starts a listener on port 8200, so the config file that also defined a listener on the same port caused a port conflict. Additionally, the read-only mount prevented vault from setting file permissions. Fixes: - Removed ./vault/config:/vault/config:ro volume mount - Kept policies and scripts mounts for potential use - Dev mode configuration remains unchanged This resolves the "address already in use" and "Read-only file system" errors. --- docker-compose.yml | 1 - 1 file changed, 1 deletion(-) diff --git a/docker-compose.yml b/docker-compose.yml index 07a5e2e..5bea4aa 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -169,7 +169,6 @@ services: cap_add: - IPC_LOCK volumes: - - ./vault/config:/vault/config:ro - ./vault/policies:/vault/policies:ro - ./vault/scripts:/vault/scripts:ro - vault-data:/vault/file