Captured from the email with subject:
SMB server is now "zone-aware"
Date: Apr 28, 2015
You can now run the native SMB service in a zone, as of this commit today:
For most purposes, SMB server administration within a (non-global)
zone should look the same as it does in the global zone. Windows
environments will view each zone as an entirely separate machine, with
it's own workgroup or domain membership etc.
There's just one major limitation: (that I know about:-)
While the SMB server is now "zone-aware", the share manager code is
not yet zone-aware.
What that means is: until sharemgr is also zone-aware, the convenient
method of defining SMB shares using "zfs set sharesmb=name=foo
dataset" works only in the global zone. However, in a non-global zone
you can define SMB shares using "sharmgr(1M)". For example:
sharemgr create -P smb tsgrp
sharemgr add-share -r foo -d "foo in zone tsmb" -s /foo tsgrp
In this case /foo is a ZFS dataset that I've delegated to this zone.
(See zonecfg(1M) for details on how to do that.) Here's my zonecfg:
root@gwr1oi:~# zonecfg -z tsmb export
This work was a long time coming (three years for some of it). Thanks
to everyone who helped get this ready for integration, including
everyone listed in the commit message, and probably others I've
forgotten to mention.
Author: Gordon Ross <email@example.com>
Date: Wed Dec 7 00:03:44 2011 -0500
1527 SMB server in non-global zones
Reviewed by: Dan McDonald <firstname.lastname@example.org>
Reviewed by: Stepan Zastupov <email@example.com>
Reviewed by: Albert Lee <firstname.lastname@example.org>
Reviewed by: Thomas Keiser <email@example.com>
Approved by: Garrett D'Amore <firstname.lastname@example.org>