Not found the specific cause but running the create user script outside of a bash script produced a valid package but in a bash script resulted in a broken package. the user installed package was also corrupt.Creating the ISO directly from a downloaded installer (software -fetch-full-installer seem to work for the OS install but always pulled a more recent version that expected. the submodule used to build ISOs appears to cache some data and I was getting corrupt installers (alway latest version rather than actual version selected through script).

Just putting out here if anyone else has issues. Image always comes up fresh with standard registration screen sequence (created a different account to see whether packer was there in background but not seeing any other account apart from new registered account).Īll very odd. I can see the installation log on the built machine (via “log show -info -debug”) and can see the multiple phases of the installation but at no point do I see any reference to the passed in packages.I can create different ISOs with different shasum but they always go to latest (was 12.2 until today when it switched to 12.2.1 as part of upgrade). for some reason, using buildprereqs.sh and selecting a prior release of the OS, a machine always builds to the latest OS version.I tried reverting to original packages (pcaker and setupsshlogin) and also tried using signed copies of these without any difference.using the technique you suggested I can see startosinstall preload the OS and includes the CLI packages in the UnwrapperPackages subdirectory.Tried many things over last few days without success.

Macos big sur vmware fusion 11