<div dir="ltr">Sorry, hit send to soon. Here's the correctly-edited response<div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 22, 2017 at 5:36 PM, <a href="mailto:support@translators.at">support@translators.at</a> <span dir="ltr"><<a href="mailto:support@translators.at" target="_blank">support@translators.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
hi folks,<br>
<br>
have a zfs-root-raid system with<br>
dedicated zfsroot/opt partitioned.<br>
upon zfs-root running ubuntu 16.04 lts.<br>
already installed snap-lxd.<br>
<br>
now want to attach containers to zfsroot/opt.<br>
no chance because of :<br>
«error: custom loop file locations are not supported»<br>
<br>
then tried<br>
lxc storage create testpool dir source=zfsroot<br>
«error: custom loop file locations are not supported»<br>
<br>
any idea?<br></blockquote><div><br></div><div><br></div><div style="font-size:12.8px"><div>Snap has restricted access to filesystem, limiting what directories it can access. </div><div><br></div><div>On ubuntu 16.04, you can specify custom loop file location with newer lxd package (e.g. "apt install -t xenial-backports lxd") instead of snap:</div><div>lxc storage create testpool dir source=/zfsroot/opt</div><div><br></div><div>Note that you need to specify the directory/mount point when using "dir", not the dataset. And "dir" might not be what you want, look at "zfs" driver instead.</div></div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px"><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
regards<br>
karl<br>
<br>
ps.: if you run zfs-root with auto-snapshots and so on,<br>
why do lxd nesting zfs storage in those tricky ways?<br>
</blockquote><div><br></div><div><div style="font-size:12.8px">You mean "why lxd use zfs on top of image on top of zfs root"?</div><div style="font-size:12.8px">You don't have to. Loopback zfs is the default setup that would fit "beginners" usage scenario, but should be change for production (e.g. using zfs driver, lvm, or btrfs)</div><span class="gmail-im" style="font-size:12.8px"></span></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> other way round:<br>
wouldn't it be better during «lxd init» to be asked whether<br>
you want to have zfs additionally or not? plain <dir> is<br></blockquote><div> <br></div><div><div>If you use lxd package, you can just run</div><div>lxc storage create testpool zfs source=zfsroot/opt<br></div><div><br></div><div>Note that in this case you specifiy the pool or dataset name, not the mountpoint.</div><span class="gmail-im"><div style="font-size:12.8px"><br></div></span></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
not the answer. basically it doesn't matter what you choose<br>
everythings will be in the /var/snap/lxd - cage. the<br></blockquote><div><br></div><div><div style="font-size:12.8px">That is because you use snap.</div><span class="gmail-im" style="font-size:12.8px"></span></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
consequences are put lxd on extra disk. but what when<br>
not possible?<br></blockquote><div><br></div><div><div style="font-size:12.8px">Don't use snap for that purpose. Use normal lxd package.</div><div class="gmail-yj6qo gmail-ajU" style="margin:2px 0px 0px;font-size:12.8px"></div></div><div></div></div><br></div><div class="gmail_extra">-- </div><div class="gmail_extra">Fajar</div></div>