Limitations

Overview

Factory depends on host permissions, available APT package indexes, and the ISO assets supplied with a build.

1. Host and container requirements

• Rootfs and ISO builds require effective UID 0. Containers must also permit the required chroot, mount, and device operations; UID 0 in a rootless container does not guarantee those capabilities.
• The APT worker needs Python-APT available to its interpreter or to /usr/bin/python3. Rootfs builds also need the selected archive compressor; ISO builds need the tools required by the supplied assets.
• Factory does not mount /proc or /sys during rootfs package installation. Package maintainer scripts that depend on those filesystems or working device nodes may fail.

2. Package sources

Rootfs builds can use only binary packages available from the configured APT sources for the selected architecture. A missing baseline package, requested package, or required dependency stops the build. Package snapshots include only the names selected in their configuration; they do not mirror a complete repository.

3. ISO builds

ISO builds depend on the stages and tools supplied through iso.data_dir. Factory validates the asset layout and stage names, but cannot determine whether user-supplied stages produce a complete or bootable image.