Updating fedora 8
Generally speaking you should not use --no-network.
But here are some reasons why you might want to: , both of which bypass the host page cache.
You can use shell glob characters in the specified path.
Be careful to escape glob characters from the host shell, if that is required. Be careful to properly quote the expression to prevent it from being altered by the shell.
You can give this option multiple times to specify multiple sources. Note that you should not point --source to sources that you don’t trust (unless the source is signed by someone you do trust). represents a newline character, which is guessed by looking at the existing content of the file, so this command does the right thing for files using Unix or Windows line endings. To insert several lines, use the same option several times: Delete a file from the guest.
Or delete a directory (and all its contents, recursively).
Note that virt-builder does not install guests from scratch.
It takes cleanly prepared, digitally signed OS templates and customizes them.
Please take a look at "FIRST BOOT SCRIPTS" for more information and caveats about the first boot scripts. Run command (and arguments) inside the guest when the guest first boots up (as root, late in the boot process). They run in the same order that they appear on the command line.
You probably want to ensure the volume(s) or filesystems in the attached disks are labelled (or use an ISO volume name) so that you can mount them by label in your run-scripts: You can have multiple --attach options, and the format can be any disk format (not just an ISO). Check/don’t check the digital signature of the OS template. For ordinary builds, this selects the output format. Note this method is deprecated: there is a separate tool for this, virt-get-kernel(1), which has more options for the file extraction.
See also: --run, "Installing packages at build time from a side repository", genisoimage(1), virt-make-fs(1). The default is to check the signature and exit if it is not correct. The kernel and initramfs are written to the current directory, unless you also specify the --output directory name.
Note if you don’t set --root-password then the guest is given a random root password which is printed on stdout. These include: --run/--run-command, which run a shell script or command while the disk image is being generated and lets you add or edit files that go into the disk image. For example: During the customization phase, the given disk is attached to the libguestfs appliance. If the output of the program is redirected to a file, ANSI colour sequences are disabled unless you use this option. (The fingerprint is a long string, usually written as 10 groups of 4 hexadecimal digits). If you have multiple source URLs, then you can have either no fingerprint, one fingerprint or multiple fingerprints.
--firstboot/--firstboot-command, which let you add scripts/commands that are run the first time the guest boots. This is used to provide extra software repositories or other data for customization. Also this doesn't cache packages (the --install, --update options). If you have multiple, then each must correspond 1-1 with a source URL. To create an old-style qcow2 file (for compatibility with RHEL 6 or very old qemu (in fact it works for any VM disk image, not just ones built using virt-builder).
--cache DIR sets the directory to use/check for cached template files. The format of the disk image is automatically detected unless you specify it by using the --format option.