fix: update Docker daemon startup for RunPod environment

- Changed from systemctl/service to direct dockerd command
- Added --iptables=false --bridge=none flags (required for RunPod)
- Added proper error checking and 10s wait time
- Improved logging with verification step

This fixes Docker startup in RunPod's containerized environment where
systemd is not available and iptables require special handling.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
2025-11-21 15:00:42 +01:00
parent 0fa69cae28
commit 8f1d4bedd2

View File

@@ -70,11 +70,20 @@ install_docker() {
sh get-docker.sh
rm get-docker.sh
# Start Docker
systemctl start docker || service docker start
systemctl enable docker || true
# Start Docker daemon (RunPod requires --iptables=false --bridge=none)
log_info "Starting Docker daemon..."
pkill dockerd 2>/dev/null || true
sleep 2
dockerd --iptables=false --bridge=none > /var/log/dockerd.log 2>&1 &
sleep 10
log_success "Docker installed: $(docker --version)"
# Verify Docker is running
if docker ps &> /dev/null; then
log_success "Docker installed and running: $(docker --version)"
else
log_error "Docker failed to start. Check /var/log/dockerd.log"
exit 1
fi
}
# Install Docker Compose