enable acl in CT

Henry

Member
Jan 1, 2016
83
0
6
51
I am installing Samba in a CT and have discovered I need acl extensions enabled in the fs. I have configured LVM for my CTs and believe the CT is using ext4

root@ares:~# mount | grep "^/dev"
/dev/mapper/virtual--machines-vm--1013--disk--1 on / type ext4 (rw,relatime,data=ordered)

The following article suggests the resolution is to enable ACL extensions on the host by editing fstab:

-- Thats no big deal, simply edit /etc/fstab from something like this:
-- UUID=deviceID /vzstorage ext3 noatime 0 1
-- to this:
-- UUID=deviceID /vzstorage ext3 noatime,acl 0 1

https://www.skelleton.net/2012/08/01/setting-up-an-active-directory-with-samba/

My host fstab reads:

root@pve:/# cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext4 errors=remount-ro 0 1
/dev/pve/data /var/lib/vz ext4 defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0

My question is how should this be edited to enable ACL extensions in my CT?
 
I don't see a noacl in the mount options, so it should already be enabled.

You can also test directly:
Code:
apt-get install acl
mkdir /var/testacl
setfacl -m d:g::rwx /var/testacl
rm -r /var/testacl

If the setfacl doesn't report "Operation not supported" then acl's are enabled.
 
Last edited:
My CT is using "vm-1001-disk-1"

root@pve:~# cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext4 errors=remount-ro 0 1
/dev/pve/data /var/lib/vz ext4 defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0

root@pve:~# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
data pve -wi-ao---- 50.38g
root pve -wi-ao---- 24.75g
swap pve -wi-ao---- 12.38g
vm-1001-disk-1 virtual-machines -wi-ao---- 4.00g
vm-1013-disk-1 virtual-machines -wi-ao---- 8.00g
vm-1015-disk-1 virtual-machines -wi-a----- 32.00g
 
You have to test from inside the container. Through the web console or on the host with pct.

Code:
pct enter 1013
 
Yes, acls are enabled. It was a Samba error that has another resolution however the error implies acls were not enabled. All good now thanks.