Repository navigation
Tags
Tags
v2.3.3 — Bug fixes for Arch Linux, Windows WSL2, and healthcheck tuning Fixes: - Osmantic#551: Arch/Void/Alpine distro-native Docker install + PyYAML dependency - Osmantic#552: Windows port 8080 conflict + ComfyUI tier gating for low-tier systems - Osmantic#553: Healthcheck timing tuning for first-run startups (embeddings + Open WebUI)
fix(installer): Windows port 8080 conflict + ComfyUI tier gating (Osm… …antic#552) * fix(installer): Windows port 8080 conflict + ComfyUI tier-aware gating Two issues reported by beta tester on Windows 11 + WSL2 (7GB RAM, NVIDIA 940MX 2GB VRAM, Tier 0): 1. Port 8080 conflict: Windows env generator hardcoded OLLAMA_PORT=8080, but wslrelay occupies port 8080 on every WSL2 system. Changed default to 11434, matching the Linux default in .env.example. The Docker internal port stays 8080 — only the host-facing port changes. 2. ComfyUI crashes low-RAM systems: Full Stack silently enabled ComfyUI, which requests shm_size 8GB + memory limit 24GB. On a 7GB system, Docker can't allocate shared memory, causing a network bridge failure that kills the entire compose-up. Added tier-aware auto-disable for Tier 0 and Tier 1 in Full Stack mode, with a warning and re-prompt in Custom mode. Changes: - env-generator.ps1: OLLAMA_PORT 8080 → 11434 - ui.sh: Full Stack auto-disables ComfyUI on Tier 0/1 with user message - install-core.sh: add --no-comfyui / --comfyui flags + usage docs - 03-features.sh: Custom mode warns Tier 0/1 users and flips default to N Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix(windows): add ComfyUI tier-aware gating to Windows installer PR Osmantic#552 added ComfyUI tier gating for the Linux bash installer but the Windows PowerShell installer has its own parallel code paths that were untouched. ComfyUI was always included in the compose stack on Windows because the service skip switch had no "comfyui" case. This was the actual root cause of the beta tester's fatal crash on Windows 11 + WSL2 (7GB RAM, Tier 0) — ComfyUI's shm_size: 8g exceeded available memory, crashing Docker's network bridge creation. Changes: - install.ps1: add -Comfyui and -NoComfyui switch parameters - install-windows.ps1: add params, context vars, and "comfyui" case to the service skip switch (the critical fix) - 03-features.ps1: add $enableComfyui variable, Full Stack auto-disables on Tier 0/1 with user message, Custom mode adds ComfyUI prompt with tier warning, Core Only disables ComfyUI Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix: strip spurious UTF-8 BOMs from PowerShell files Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix(installer): add ComfyUI tier safety net for non-interactive mode The tier-aware ComfyUI gating only ran inside the interactive menu block. Non-interactive installs (--non-interactive / -NonInteractive) skipped the menu entirely, leaving ENABLE_COMFYUI=true on Tier 0/1 systems where ComfyUI's shm_size 8GB exceeds available RAM. Add a safety net after the interactive block on both Linux and Windows that unconditionally disables ComfyUI on Tier 0/1. In interactive mode this is a no-op (menu already handled it). In non-interactive mode this prevents the crash. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix(installer): scope ComfyUI safety net to non-interactive mode only The safety net unconditionally overrode ENABLE_COMFYUI on Tier 0/1, which would silently undo an explicit user confirmation in Custom mode (user says Y to ComfyUI, Y to the tier warning, then safety net disables it anyway). Guard with ! $INTERACTIVE (Linux) / $nonInteractive (Windows) so it only fires in headless mode where the user was never prompted. Interactive mode already has its own tier checks in the menu. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix(windows): remove incorrect nonInteractive guard from Custom mode warning The previous commit accidentally applied the $nonInteractive guard to the Custom mode tier warning prompt inside the interactive menu block. Since the menu block itself is gated by -not $nonInteractive, the condition was always false and the warning never fired. The guard should only be on the safety net after the menu block. The Custom mode warning is interactive by definition. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
v2.3.1 — Optional ComfyUI, Security Fixes, Windows Vulkan Fix Changes since v2.3.0: • fix: add ENABLE_IMAGE_GENERATION to .env schema (Osmantic#516) • security: bind OpenClaw Pro gateway to localhost only (Osmantic#514) • feat: make ComfyUI + FLUX optional, saves ~34GB when disabled (Osmantic#513) • fix(windows): update Vulkan llama-server binary to b8248 (Osmantic#512) • fix: add missing backslash line continuations in bootstrap launch (Osmantic#511) • fix: correct model path in upgrade-model.sh
v2.3.0 — Bootstrap Fast-Start & Installer Hardening Highlights: • Bootstrap model pattern: Tier 1+ installs download a tiny 2B model (~1.5GB, ~1 min) first. Chat immediately while full model downloads in background and auto-swaps when ready. • Fixed: missing line continuations that crashed bootstrap launch • Fixed: .env patched with bootstrap model values before compose up • Fixed: curl exit code preserved in health checks • All timeouts bumped to 60 min (downloads) / 20 min (health checks) • curl | bash works — all interactive reads use /dev/tty • wget replaced with curl for model downloads (faster, one less dep) • test-install.sh for fast Tier 0 testing • --no-bootstrap flag to opt out of fast-start
v2.2.0 — CLI improvements, CPU-only support, AMD hardening New features: - dream repair <service> — stop, nuke volumes, recreate, re-seed config - dream CLI symlinked to /usr/local/bin/dream during install - Compose flag caching (.compose-flags) for faster CLI commands - CPU-only compose overlay (docker-compose.cpu.yml) for machines without GPU - Post-install Perplexica config re-validation if phase 12 failed - AMD render/video group membership warning at install summary - Dashboard GPU detection now shows AMD-specific troubleshooting Fixes: - Docker 29.3.x AMD GPU device passthrough workaround (auto-downgrade to 29.2.1) - /dev/kfd and /dev/dri verification before launching AMD GPU containers - Shell injection fix in repair-perplexica.sh (os.environ instead of interpolation) - .compose-flags invalidated on dream enable/disable - CI: ShellCheck, gitleaks allowlist, test isolation, port contract alignment - Manifest schema: ui_path and health_timeout formally validated Testing: - dream-doctor.sh test suite (13 tests) added to CI - CPU-only compose selection BATS test
PreviousNext