Common Docker-related issues and their solutions for the TurtleBot3 development container.
Docker Desktop not starting
If Docker Desktop won’t start, the container cannot run. Ensure virtualization is enabled in your system BIOS.
- Docker daemon is not running
- Container won’t start
Solutions:
Enable virtualization in BIOS
- Restart computer and enter BIOS (F2, F10, or Del key)
- Enable “Virtualization Technology” (Intel VT-x or AMD-V)
- Save and exit
Restart Docker service
Windows (PowerShell as Administrator):net stop com.docker.service
net start com.docker.service
# Restart Docker Desktop application
# Or restart docker daemon on Linux
sudo systemctl restart docker
Reset Docker Desktop (if needed)
- Right-click Docker Desktop system tray icon
- Troubleshoot → Reset to factory defaults
- Restart Docker
Permission denied (Linux)
Symptoms:
- “permission denied while trying to connect to Docker daemon”
Solution:
# Add user to docker group
sudo usermod -aG docker $USER
# Log out and back in, or:
newgrp docker
# Verify
docker run hello-world
Out of memory errors
Symptoms:
- Container build fails partway through
- “no space left on device” errors
Increase Docker resources (Docker Desktop)
Open Docker Desktop settings
Navigate to Settings → Resources
Adjust resource limits
- Memory: 8GB minimum, 16GB recommended
- CPUs: 4-6 cores
- Disk: 50GB+ recommended
Apply changes
Click “Apply & Restart”
# Remove unused images
docker image prune -a
# Remove unused volumes
docker volume prune
# Remove everything unused
docker system prune -a --volumes
Resource allocation on Linux
Resources are not limited by default on Linux. If you experience out of memory issues, check your system’s available resources:
# Check available memory
free -h
# Check disk space
df -h
# Check Docker disk usage
docker system df