Marking as won't fix in the current state of LXD as it's not yet clear whether this is in scope or not for our zfs work.
Even when we support multiple storage pools, I'd still be opposed to overriding any configuration that the user made already, possibly with the exception of mountpoint which we certainly should set to none regardless. If the user has a pool which they marked as noexec or nosuid, I would actually expect the containers to fail and require them to adjust their settings, rather than alter security configuration for them automatically (which may conflict with security certifications or company policies). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629824 Title: lxd should explicitly create "containers" and "images" datasets on ZFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1629824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
