Victor's room

Overview & Root Cause Summary: The error docker: Error response from daemon: Conflict. The container name "/app" is already in use by container "..." occurs when a user or automation pipeline attempts to create or run a container with a designated name, but an existing container (either currently running or stopped/exited) is already occupying that unique identifier in the Docker daemon’s namespace.

Understanding the Root Causes

• Exited Containers Not Removed: By default, executing docker run --name preserves the container state on disk even after the process exits unless the --rm flag was provided.
• Docker Compose Service Re-creation Conflicts: Renaming directories, switching branches, or altering project names leaves orphaned containers that block new deployments sharing identical container names.
• CI/CD Runner Pipeline Restarts: Build scripts executing repeated deploy stages fail if a previous build crashed before reaching the teardown step.
• Stale Docker Daemon State: Sudden host power loss or kernel panic leaving unlinked metadata files inside /var/lib/docker/containers/.

Step 1: Quick Fix (Identify and Remove the Existing Container)

Locate the stopped or active container holding the target name and remove it forcefully.

# 1. Search for all containers (including stopped ones) matching the name:
docker ps -a --filter "name=^/my-app$"

# 2. Forcefully stop and remove the conflicting container:
docker rm -f my-app

# 3. Re-run your container with the --rm flag to ensure automatic cleanup on exit:
docker run -d --rm --name my-app -p 8080:80 nginx:alpine

Step 2: Resolving Docker Compose Naming Conflicts

Ensure old containers and orphaned resources are pruned cleanly when managing multi-container stacks.

# 1. Stop and remove existing Compose stack containers and networks:
docker compose down --remove-orphans

# 2. Re-create and start the stack in detached mode:
docker compose up -d --force-recreate

# 3. If running multiple environments from the same compose file, use unique project names:
docker compose -p staging up -d
docker compose -p production up -d

Step 3: Automated Cleanup & Stale Daemon Reset

Prune all stopped containers from local storage or restart the Docker engine if the engine retains phantom references.

# 1. Remove all stopped containers across the host system:
docker container prune -f

# 2. If Docker still claims the name is in use after removal, restart the daemon:
# On Linux (systemd):
sudo systemctl restart docker

# On macOS / Windows:
# Restart Docker Desktop from the system menu bar.

Verification & Testing Steps

Confirm that the container starts smoothly under the desired name and verify its active status.

# 1. Verify that the new container is running without conflict:
docker ps --filter "name=^/my-app$"
# Status should display "Up X seconds"

# 2. Test application reachability:
curl -I http://localhost:8080

# 3. Check container inspect metadata for accurate name binding:
docker inspect -f '{{.Name}} - {{.State.Status}}' my-app

Summary Comparison Table