**Updates
This thread helps someone access a dataset with user "nobody" and group name of your choice with permissions 770 by multiple jails each that are a part of the same group.
**End updates
I am trying to have the jail
I have:
I was able to fix this by changing the owner of the dataset
I suppose I could live with this, however I am not sure why it is necessary. The group
A few other things. I am using share type and ACL type Unix. Does anyone have any recommendations regarding dataset Share and ACL types for Unix vs Windows? My environment is all Windows computers and the FreeNAS, however I do plan on having a few linux bhyve vm's, that will also have access to some SMB and/or resilio sync shares.
Some websites I have found with this/similar problems mention logging into the jails machine and adding a group
So, to summarize my question(s):
Why can't the jails installation user
Additionally, is there a better way I should be doing this using ACL and/or sharetype Windows for some reason?
Any help appreciated.
This thread helps someone access a dataset with user "nobody" and group name of your choice with permissions 770 by multiple jails each that are a part of the same group.
**End updates
I am trying to have the jail
rslsync
11.2-RELEASE-p15, configured via plugin mount and read/write to dataset tank1/ds1/resilio
.I have:
- Installed Resilio Sync with defaults using the plugin.
- Created a user and group both named
resilio
with GID and UID 817. - Created a dataset
tank1/ds1/resilio/
with ownerbar
and groupresilio_backup
. - I added the auxiliary group
resilio_backup
to userrslsync
. - I have mounted the FreeNAS source dataset
/mnt/tank1/ds1/reslio
to the Jails destination/mnt/tank1/iocage/jails/rslsync/root/data
. - The dataset is default share type Unix and ACL type Unix.
/root/data/new_folder
I get the error "don't have permissions to write to the selected folder".I was able to fix this by changing the owner of the dataset
tank1/ds1/resilio/
to rslsync
.I suppose I could live with this, however I am not sure why it is necessary. The group
reslio_backup
should be sufficient, should it not? The dataset tank1/ds1/resilio/
has all 3 permission boxes checked for both user and group (not for other).A few other things. I am using share type and ACL type Unix. Does anyone have any recommendations regarding dataset Share and ACL types for Unix vs Windows? My environment is all Windows computers and the FreeNAS, however I do plan on having a few linux bhyve vm's, that will also have access to some SMB and/or resilio sync shares.
Some websites I have found with this/similar problems mention logging into the jails machine and adding a group
resilio_backup
to the rslsync
user. I have not yet tried this because it seems a little bit hacky and I am not 100% comfortable reversing it. It also doesn't make since. If the user is part of the group that has permissions on the freeNAS, why can't it write to the folder?So, to summarize my question(s):
Why can't the jails installation user
rslsync
write to the freenas dataset that is owned by the group resilio_backup
when the freenas user rslsync
has the auxillary group resilio_backup
added?Additionally, is there a better way I should be doing this using ACL and/or sharetype Windows for some reason?
Any help appreciated.
Last edited: