From 42bd54783a7dcae1cc9c2b209a5659b93e995a9e Mon Sep 17 00:00:00 2001 From: Dorian Date: Thu, 12 Feb 2026 12:50:02 +0000 Subject: [PATCH] Remove container_name from docker-compose to fix redeploy conflicts Portainer fails to redeploy when the old containers still exist with the same hardcoded names. Letting Compose auto-name them based on the stack/project avoids the conflict. Co-authored-by: Cursor --- docker-compose.yml | 3 --- 1 file changed, 3 deletions(-) diff --git a/docker-compose.yml b/docker-compose.yml index a58a3da..936c466 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -6,7 +6,6 @@ services: build: context: . dockerfile: Dockerfile - container_name: indeedhub-app restart: unless-stopped ports: - "7777:7777" @@ -27,7 +26,6 @@ services: # ── Nostr Relay (stores comments, reactions, profiles) ─────── relay: image: scsibug/nostr-rs-relay:latest - container_name: indeedhub-relay restart: unless-stopped volumes: - relay-data:/usr/src/app/db @@ -40,7 +38,6 @@ services: build: context: . dockerfile: Dockerfile.seed - container_name: indeedhub-seeder depends_on: - relay environment: