Problem
When merging layered configs, packages from one distro flavor leak into others. For example, Debian-specific packages (e.g., build-essential) get inherited into Alpine builds where they don't exist, causing apk add failures.
This affects any multi-layer config setup where a parent layer specifies packages for one distro and a child layer targets a different flavor.
Options
- Distro-aware merge logic — merge engine understands which packages belong to which distro family and filters during Dockerfile generation
- Per-flavor package lists — schema supports
packages.debian / packages.alpine instead of a flat packages list
- Drop multi-distro support — simplify to a single supported base distro
Current impact
Alpine builds are broken in any project that inherits packages from a Debian-configured parent layer. Other non-Debian flavors would hit the same issue.
Problem
When merging layered configs, packages from one distro flavor leak into others. For example, Debian-specific packages (e.g.,
build-essential) get inherited into Alpine builds where they don't exist, causingapk addfailures.This affects any multi-layer config setup where a parent layer specifies packages for one distro and a child layer targets a different flavor.
Options
packages.debian/packages.alpineinstead of a flatpackageslistCurrent impact
Alpine builds are broken in any project that inherits packages from a Debian-configured parent layer. Other non-Debian flavors would hit the same issue.