Skip to main content

Troubleshooting

Common Startup Issues​

Ports Already in Use​

Symptom: error Bind for 0.0.0.0:8081 failed: port is already allocated

Solution:

# Check which process is using the port
lsof -i :8081

# Stop the conflicting process or change the port in .env

Insufficient Docker Memory​

Symptom: containers terminate with OOM Killed error

Solution:

  • Ensure Docker is allocated at least 16 GB of RAM
  • On Windows/macOS: open Docker Desktop settings → Resources → increase the memory limit

Containers Fail to Start​

Symptom: docker compose up exits with an error

Solution:

# Check Docker versions
docker --version        # Requires 20.10.0+
docker compose version  # Requires 2.22.0+

# View logs for a specific service
docker compose logs <service-name>

# Rebuild from scratch
docker compose down -v
docker compose -f docker-compose.yml -f docker-compose.dev.yml up --build -d

WSL2 Not Configured (Windows)​

Symptom: Docker Desktop does not start on Windows

Solution:

  1. Open PowerShell as Administrator
  2. Run: wsl --install
  3. Restart the computer
  4. Launch Docker Desktop

Checking System Status​

To check the status of all containers:

docker compose ps

To view logs in real time:

docker compose logs -f

Full Reset​

If the system is not functioning correctly, perform a full reset:

# Stop all containers
docker compose down -v

# Remove build cache
docker system prune -f

# Restart
docker compose -f docker-compose.yml -f docker-compose.dev.yml up --build -d
caution

The docker compose down -v command will delete all data stored in Docker volumes (databases, MinIO files). Use with caution.

Contacting Support​

If you are unable to resolve the issue on your own, contact technical support.