Home / Docker / Docker Container Exit Code 1: Immediate Exit Troubleshooting Guide

Docker

Docker Container Exit Code 1: Immediate Exit Troubleshooting Guide

Learn how to diagnose and fix Docker containers that exit immediately with code 1, including application errors, missing dependencies, and configuration issues.

Published: Nov 12, 20256 min readBy FixWikiHub Editorial Team

Abstract illustration for a troubleshooting knowledge base category.

# Docker Container Exit Code 1: Immediate Exit Troubleshooting Guide

You've started a container, but it exits almost immediately with exit code 1. No logs, no clues—just a dead container. This is one of the most frustrating Docker issues because the container disappears before you can investigate.

Exit code 1 typically indicates a general application error. Unlike exit code 0 (success) or exit code 137 (killed by OOM), code 1 means something went wrong inside your application or its startup process.

Introduction

This article covers troubleshooting steps and solutions for Docker Container Exit Code 1: Immediate Exit Troubleshooting Guide. The error typically occurs in production environments and can cause service disruptions if not addressed promptly.

Symptoms

Common error messages include:

bash

docker ps -a --filter "status=exited" --format "table {{.Names}}\t{{.Status}}\t{{.Image}}"

bash

docker logs <container_name>

bash

docker logs --tail 100 <container_name>
docker logs --since 5m <container_name>

Common Causes

When a container exits with code 1, one of these scenarios is usually responsible:

Application crash during initialization - Your app throws an unhandled exception
Missing configuration files - Required config files aren't in the expected location
Environment variable issues - Required env vars are missing or malformed
Dependency failures - Database connections, external APIs, or services unavailable
File permission problems - The container user can't read/execute necessary files
Invalid command or entrypoint - The CMD or ENTRYPOINT is incorrect

Step-by-Step Fix

Diagnosing the Problem

Check Container Status and Exit Code

First, verify the exit code and see how recently the container exited:

bash

docker ps -a --filter "status=exited" --format "table {{.Names}}\t{{.Status}}\t{{.Image}}"

Look for containers that show "Exited (1)" in the status. The timestamp tells you if this is a recurring issue.

View Container Logs

The most important step is checking what the container tried to output before dying:

bash

docker logs <container_name>

If the container exits too fast, you might miss logs. Try:

bash

docker logs --tail 100 <container_name>
docker logs --since 5m <container_name>

If there are no logs at all, the application might be silently crashing or writing to a different output stream.

Inspect Container Configuration

See exactly how the container was configured:

bash

docker inspect <container_name> --format '{{json .Config}}' | jq

This shows the entrypoint, command, environment variables, and volumes. Pay attention to: - Cmd and Entrypoint - Are they correct? - Env - Are required environment variables set? - WorkingDir - Is the working directory correct?

Run Interactively for Debugging

When logs don't help, run the container interactively:

bash

docker run -it --entrypoint /bin/sh <image_name>

For Alpine-based images:

bash

docker run -it --entrypoint /bin/ash <image_name>

Once inside, you can: - Check if files exist where expected - Test running the application manually - Verify environment variables with env - Check file permissions with ls -la

Common Fixes

Fix 1: Missing Environment Variables

If your application requires specific environment variables:

bash

docker run -d \
  -e DATABASE_URL=postgres://user:pass@host:5432/db \
  -e API_KEY=your-api-key \
  --name myapp \
  myimage:latest

For Docker Compose, ensure variables are defined in docker-compose.yml or an .env file:

yaml

services:
  myapp:
    image: myimage:latest
    environment:
      - DATABASE_URL=${DATABASE_URL}
    env_file:
      - .env

Fix 2: Incorrect Entrypoint or Command

Sometimes the Dockerfile specifies a wrong entrypoint. Override it:

bash

docker run -d --entrypoint "" myimage:latest /app/start.sh

Or fix the Dockerfile directly:

```dockerfile # Wrong ENTRYPOINT ["./app"] CMD ["--wrong-flag"]

# Correct ENTRYPOINT ["./app"] CMD ["--correct-flag", "--port", "8080"] ```

Fix 3: Missing Configuration Files

If your app needs config files that aren't in the image:

bash

docker run -d \
  -v /host/path/config.yml:/app/config.yml:ro \
  --name myapp \
  myimage:latest

Verify the mount is correct:

bash

docker exec <container_name> ls -la /app/config.yml

Fix 4: Dependency Connection Issues

If your app fails because it can't reach a database or service:

1.Ensure the dependency is running first
2.Use proper networking in Docker Compose:

```yaml services: db: image: postgres:15 healthcheck: test: ["CMD-SHELL", "pg_isready -U postgres"] interval: 5s timeout: 5s retries: 5

app: image: myapp:latest depends_on: db: condition: service_healthy ```

Fix 5: File Permission Issues

If the container runs as a non-root user and can't access files:

```bash # Check current user docker run --rm myimage:latest whoami

# Fix permissions on host chmod -R 755 ./config chown -R 1000:1000 ./data ```

Or run as root temporarily for testing (not recommended for production):

bash

docker run -d --user root myimage:latest

Verification

After applying your fix, verify the container stays running:

```bash # Start the container docker run -d --name test_container myimage:latest

# Wait a moment and check status sleep 5 docker ps --filter "name=test_container"

# Check logs docker logs test_container

# Verify uptime docker inspect test_container --format '{{.State.StartedAt}}' ```

If the container is still running after a few minutes, your fix worked.

Prevention

To avoid exit code 1 issues in the future:

Always include health checks in your Dockerfile
Use proper signal handling in your application
Set a reasonable restart policy: --restart on-failure:3
Log to stdout/stderr instead of files for Docker to capture
Validate configuration at startup with meaningful error messages
Use dependency checks in Docker Compose with depends_on and healthcheck

Exit code 1 is frustrating but almost always solvable with systematic debugging. Start with logs, then inspect configuration, and finally run interactively to isolate the root cause.

[Fix docker build cache invalidated unnecessary layers Issue in Docker-Errors](docker-build-cache-invalidated-unnecessary-layers)
[Fix Docker Build Cache Invalidation Optimization Issue in Docker](docker-build-cache-invalidation-optimization)
[Fix docker build context slow large files Issue in Docker-Errors](docker-build-context-slow-large-files)
[Fix docker build multi stage copy from not found Issue in Docker-Errors](docker-build-multi-stage-copy-from-not-found)
[Fix docker buildkit export local tar layer missing Issue in Docker-Errors](docker-buildkit-export-local-tar-layer-missing)

Was this guide helpful?

Related search paths

People also search for

If the symptom is close but not identical, these search paths usually surface the right neighboring fixes faster than scrolling the full archive.

Docker Container Exit Code 1: Immediate Exit Troubleshooting Guide Docker Container Exit Code 1: Immediate Exit Troubleshooting Guide Docker Docker Container Exit Code 1: Immediate Exit Troubleshooting Guide troubleshooting Docker Container Exit Code 1: Immediate Exit Troubleshooting Guide fix Learn how to diagnose and fix Docker containers that exit immediately with code 1, including application errors, missing dependencies, and configuration issues Docker Learn how to diagnose and fix Docker containers that exit immediately with code 1, including application errors, missing dependencies, and configuration issues

Explore Related Topics

Browse Guides from Other Categories

Discover troubleshooting guides from related categories to expand your knowledge.

FAQ

Docker Troubleshooting FAQs

Common questions about troubleshooting and preventing similar issues

How do I know if this docker-errors troubleshooting guide applies to my situation?

This guide is designed for docker-errors issues. If you're experiencing similar symptoms described in the article, follow the step-by-step instructions. Start with the most common causes and work through the diagnostic process.

Is it safe to follow these docker-errors troubleshooting steps?

Yes, all steps are designed to be safe and non-destructive. We recommend creating backups before making significant changes and testing each step before proceeding to the next.

How long does it typically take to resolve this type of docker-errors issue?

Most docker-errors issues can be resolved within 30 minutes to 2 hours, depending on the complexity and root cause. Follow the troubleshooting flow to identify and fix the problem efficiently.

How can I prevent this docker-errors issue from happening again?

Regular maintenance, monitoring, and following best practices for docker-errors configuration can help prevent recurrence. Consider implementing automated checks and alerts for early detection.

Written by

FixWikiHub Editorial Team

Our editorial team consists of experienced DevOps engineers, systems administrators, and cloud architects with hands-on experience in production environments across AWS, Azure, GCP, and on-premises infrastructure.

Every guide undergoes technical review for accuracy and is updated when software versions, commands, or best practices change.

Last updated: Nov 12, 2025

About our team

Important Notice

Disclaimer & Safety Guidelines

The troubleshooting steps in this guide are provided for educational and informational purposes. Before applying any changes to production systems:

Test in a staging environment first — Always verify commands and configurations in a non-production environment before deploying to live systems.
Create backups — Ensure you have current backups of databases, configurations, and critical files before making changes.
Understand the impact — Review how each step may affect your specific environment, dependencies, and users.
Consult official documentation — This guide supplements, but does not replace, official vendor documentation and best practices.

FixWikiHub is not responsible for any damages arising from the use of this content. See our Terms of Use for more information.

Resources

Official Documentation & Further Reading

For authoritative information, consult the official documentation for the technologies discussed in this guide. Our troubleshooting content supplements, but does not replace, vendor documentation.

AWS Documentation — Official Amazon Web Services guides and API references
Kubernetes Documentation — Official Kubernetes documentation
Nginx Documentation — Official Nginx web server documentation
Apache Documentation — Official Apache HTTP Server documentation
Docker Documentation — Official Docker container documentation

Docker Container Exit Code 1: Immediate Exit Troubleshooting Guide

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Diagnosing the Problem

Check Container Status and Exit Code

View Container Logs

Inspect Container Configuration

Run Interactively for Debugging

Common Fixes

Fix 1: Missing Environment Variables

Fix 2: Incorrect Entrypoint or Command

Fix 3: Missing Configuration Files

Fix 4: Dependency Connection Issues

Fix 5: File Permission Issues

Verification

Prevention

People also search for

Browse Guides from Other Categories

WordPress

SSL

DNS

Docker Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading

Docker Container Exit Code 1: Immediate Exit Troubleshooting Guide

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Diagnosing the Problem

Check Container Status and Exit Code

View Container Logs

Inspect Container Configuration

Run Interactively for Debugging

Common Fixes

Fix 1: Missing Environment Variables

Fix 2: Incorrect Entrypoint or Command

Fix 3: Missing Configuration Files

Fix 4: Dependency Connection Issues

Fix 5: File Permission Issues

Verification

Prevention

Related Articles

People also search for

Share this guide

More Docker Troubleshooting Guides

Browse Guides from Other Categories

Docker Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading