This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
cluster:139 [2015/08/03 14:29] hmeij |
cluster:139 [2018/08/01 15:24] hmeij07 [Warewulf Stateless] |
||
---|---|---|---|
Line 63: | Line 63: | ||
* Lethal error thrown by module: / | * Lethal error thrown by module: / | ||
* answer is here https:// | * answer is here https:// | ||
+ | * quoting | ||
+ | |||
+ | < | ||
+ | What it appears you'll need to do initially is build out a chroot | ||
+ | directory. For example, for a Scientific Linux 6.x install, you'd do: | ||
+ | |||
+ | # wwmkchroot sl-6 / | ||
+ | to store them at -- run wwmkchroot -h for the help) | ||
+ | |||
+ | That will give the base chroot for the VNFS at / | ||
+ | You'll then set the environment variable CHROOTDIR when you execute | ||
+ | wwinit. | ||
+ | |||
+ | # CHROOTDIR=/ | ||
+ | |||
+ | I know when you use the ' | ||
+ | chroot based upon the host OS. But none of the other wwinit scripts, | ||
+ | by default, create one; So you will need to build the chroot and | ||
+ | specify where the directory is. Then when the VNFS part of wwinit is | ||
+ | ran, it will build the VNFS and import it into the datastore at that | ||
+ | time, setting the one specified as the default VNFS in the | ||
+ | configuration. | ||
+ | </ | ||
So we start by making the chroot directories, | So we start by making the chroot directories, | ||
Line 322: | Line 345: | ||
</ | </ | ||
+ | |||
+ | [[cluster: | ||
Useful links | Useful links |