Based on feedback from PR #2319 code review: critical network operations
need explicit error handling and validation.
Added safeguards:
- curl -f flag: Fail on HTTP errors (429, 404, 500, etc)
- test -s check: Verify downloaded file is not empty
- tar extraction error check: Fail if tar extraction fails
- lib directory validation: Confirm bashio/lib exists after extraction
- Explicit error messages: Clear diagnostics if any step fails
This prevents silent failures where downloads could fail but build
continues with broken/missing bashio installation.
Prevents: Users pulling images with non-functional bashio
Impact: Build will fail explicitly with clear error messages if download/extraction fails
- Multi-architecture support restored (aarch64 builds)
- Error suppression removed for user diagnostics
- Circular dependency fix documented
- Config.yaml version tag corrected
CRITICAL FIXES:
1. Restore multi-architecture support - Use ARG BUILD_FROM/BUILD_ARCH instead of hardcoded amd64 base image
- Fixes: aarch64 builds were broken by hardcoded FROM ghcr.io/hassio-addons/base/amd64:11.1.0
- Now: FROM $BUILD_FROM allows alexbelgium build system to set correct base per architecture
2. Remove stderr suppression from agent command - Restore error visibility for debugging
- Fixes: Error messages were hidden by 2>/dev/null redirection
- Now: ./agent command output visible for user diagnostics
These changes ensure:
- Multi-arch builds work correctly (amd64, aarch64, armv7, armhf, i386)
- Users can debug configuration issues via visible error logs
- Circular dependency fix is fully compatible with existing build system
Adds changelog entry for alpine-sts version (30-12-2025) documenting:
- Fix for circular dependency that prevented Docker builds
- Restoration of official Portainer Agent image source
- Resolution of Issue #2318 (404 manifest unknown errors for users)
