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 <cursoragent@cursor.com>
This commit is contained in:
Dorian
2026-02-12 12:50:02 +00:00
parent 2c6e311705
commit 42bd54783a

View File

@@ -6,7 +6,6 @@ services:
build: build:
context: . context: .
dockerfile: Dockerfile dockerfile: Dockerfile
container_name: indeedhub-app
restart: unless-stopped restart: unless-stopped
ports: ports:
- "7777:7777" - "7777:7777"
@@ -27,7 +26,6 @@ services:
# ── Nostr Relay (stores comments, reactions, profiles) ─────── # ── Nostr Relay (stores comments, reactions, profiles) ───────
relay: relay:
image: scsibug/nostr-rs-relay:latest image: scsibug/nostr-rs-relay:latest
container_name: indeedhub-relay
restart: unless-stopped restart: unless-stopped
volumes: volumes:
- relay-data:/usr/src/app/db - relay-data:/usr/src/app/db
@@ -40,7 +38,6 @@ services:
build: build:
context: . context: .
dockerfile: Dockerfile.seed dockerfile: Dockerfile.seed
container_name: indeedhub-seeder
depends_on: depends_on:
- relay - relay
environment: environment: