Where Does ArchISO Put Built ISOs?
ArchISO builds into work and out folders you choose, defaulting inside the profile dir. Flags and layout.
Last updated
ArchISO writes nothing to a fixed location. Working files and finished images land in folders you name per run, defaulting to work and out inside the current directory or profile folder. The flags choose everything: working dir, output dir, and which profile builds.
That user-chosen design means guides quoting one path describe their own machine. Check the flags on your build command before hunting folders. Keep profile sources under version control; work trees regenerate and output ISOs archive per release.
Where ArchISO stores this, by platform
./out (mkarchiso -o output dir)
Finished ISOs land here; working files in ./work (-w flag). Defaults sit inside the profile directory when flags are omitted. Clean work trees between builds when switching profiles to avoid stale packages.
Frequently asked questions
How do I change where ArchISO writes the ISO?
Pass -o with the target directory on the mkarchiso command line. Working scratch moves with -w likewise. Both default into the current profile folder, so explicit flags are the portable habit.
What is the ArchISO work folder for?
Build scratch: package caches, squashfs staging and intermediate images. It regenerates every run and dwarfs the final ISO. Delete it after successful builds or keep it for faster rebuilds of the same profile.
Where are ArchISO profiles stored?
Wherever you keep them: /usr/share/archiso/configs ships the releng baseline to copy from. Custom profiles live in your own repos. Build from the profile dir so relative includes resolve.
Notice an outdated path? Let us know.