LogForge now starts local Docker monitoring inside the appliance. New installations do not need a separate local-agent container or enrollment step.
- The first-run guide confirms local readiness and explains optional remote enrollment.
- Docker unavailability is visible in setup status. The embedded collector retries safely and recovers with the same identity; collector failures do not stop the application.
- Monitoring uses in-memory queues and the existing Docker collector. Existing local deployments are retained to avoid duplicate monitoring.
- Usage reports identify installation and agent software versions when reported. Older versions remain “Not reported.” Startup includes a follow-up sample after local enrollment.
- Hardware views report logical CPUs and total RAM capacity. Engine capacities are listed individually when physical-host overlap cannot be verified; utilization is not collected by this publisher feed.
Images logforge/unicron:3.0.1 and logforge/unicron-agent:3.0.1 support linux/amd64 and linux/arm64. Both latest aliases are updated. Packaged startup was verified on native ARM; amd64 checks covered Docker outage, unexpected collector termination, stable identity after restart, and onboarding.
For new Unraid installations, use the updated Community Applications template. Existing containers must add the read-only Host root mapping (/ to /host/root) for local file-tail collection. Keep the existing appdata volume. Remote agents remain optional and require their own enrollment and updates.
The source template is published at https://raw.githubusercontent.com/log-forge/logforge/main/templates/logforge-unicron.xml. Community Applications indexing can refresh separately. A physical Unraid host was not available for an operating-system-specific installation check.
Unraid update channel
The Unraid template now follows logforge/unicron:unraid, and its built-in updater stays on that channel. Both unraid and the refreshed 3.0.0 compatibility tag point to the tested software version 3.0.1 for amd64 and arm64. The agent image has matching tags. Previous 3.0.0 images are preserved as 3.0.0-before-unraid-20261028.
For an existing Unraid container, edit Repository to logforge/unicron:unraid, add or set UNICRON_UPDATE_IMAGE_REF=logforge/unicron:unraid in advanced settings, preserve appdata, and apply the update. Keep the read-only host-root mapping described above. Existing latest and 3.0.0 installations can pull the current build immediately.