On 2015-06-12 23:59, Marcus Reid wrote: > Hi, > > I'm doing zfs from within a jail, and there is one thing that's giving > me some trouble. > > First, the bits that get zfs working from inside a jail: > > /etc/jail.conf: > allow.mount; > allow.mount.zfs; > enforce_statfs = 1; > > /etc/sysctl.conf: > security.jail.mount_allowed=1 > security.jail.mount_zfs_allowed=1 > security.jail.enforce_statfs=1 > > zfs set jailed=on zroot/jails/git/git > > Finally, to get the dataset visible inside the jail, this is required > when the jail is running: > > zfs jail git zroot/jails/git/git > > So, in jail.conf, I do a: > > exec.poststart = "zfs jail git zroot/jails/git/git" > > Problem: zfs is not visible in jail after a reboot. This problem is > understood but I don't know the solution. > > exec.poststart is run after exec.start (the thing that runs /etc/rc in > the jail), so the zfs datasets are not yet visible when /etc/rc.d/zfs > runs in the jail. So, I have to log into the jail and do a 'zfs mount > -a' after everything comes up. Not ideal. If there were a > exec.postcreate directive in jail.conf that ran a command on the host > after jail creation but before /etc/rc starts, then I could run 'zfs > jail' before the jails init scripts are run. > > Am I going about that in the wrong way? jail.conf seems like the right > place for it, because you want your storage working after a 'jail -rc > git', right? > > Thanks, > > Marcus > _______________________________________________ > freebsd-jail@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-jail > To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org" >
If you set: zfs_enable="YES" in rc.conf inside the jail, it runs 'zfs mount -a' as part of the startup routine. This is how it is expected to work. -- Allan Jude
signature.asc
Description: OpenPGP digital signature
