fix: use legacy Docker builder for RunPod compatibility

- Set DOCKER_BUILDKIT=0 to use legacy builder
- BuildKit has permission issues in RunPod's containerized environment
- Legacy builder works reliably with RunPod's security constraints

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

Co-Authored-By: Claude <noreply@anthropic.com>

scripts/prepare-template.sh

@@ -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
@@ -116,6 +125,9 @@ build_docker_images() {
 
     cd /workspace/ai
 
+    # Use legacy builder (buildkit has permission issues in RunPod)
+    export DOCKER_BUILDKIT=0
+
     # Build orchestrator
     log_info "Building orchestrator..."
     docker compose -f compose.yaml build orchestrator