| | 15 | === Virtual Machines === |
| | 16 | |
| | 17 | In order to use a new VM (Virtual Machine) with pb, you have to follow a 3-step approach: |
| | 18 | 1. Create an appropriate VM using pb (or not if you prefer to create it outside with your preferred tools) |
| | 19 | {{{ |
| | 20 | pb -m os-ver-arch -i /path/to/os.ver.arch.iso newver |
| | 21 | }}} |
| | 22 | where you pass to the pb command the ISO image of your distribution media. If you prefer to deploy using PXE e.g. you have to use instead the qemu command directly. |
| | 23 | At the end of the installation, pb makes recommendations on what minimum packages have to be present (sshd and sudo e.g.) and their minimal setup. Something that has to be done manually, at worst, before being able to launch the second phase. |
| | 24 | 2. Set up the VM so it gets all what is needed to run pb in it: |
| | 25 | {{{ |
| | 26 | pb -m os-ver-arch setupvm |
| | 27 | }}} |
| | 28 | This step will install pb inside your VM, create a dedicated account for building packages, exchange dedicated ssh keys from your own account, and setup sudo rights so the build can be made non-interactively. The first time ou call that command, it will ask you the root passwd of the VM, in order to setup up auhtentication. |
| | 29 | Each time you want to re-align pb versiosn between your host and the guest, you'll have to re-run that command. The root passwd won't be asked this time, so it can be automated easily. (If you don't precise a specific VM to work on, all the the one declared in your configuration file will be updated). |
| | 30 | |
| | 31 | 3. Finally you're able to use your VM to build your software packages: |
| | 32 | {{{ |
| | 33 | pb -m os-ver-arch sbx2vm |
| | 34 | }}} |
| | 35 | Note that you can specify multiple VMs separated by ','. |
| | 36 | |
