Permissions bug about samba HOT 4 CLOSED

@htkoca sorry for the slow reply, I was out of town on vacation.

The -u flag will create a user on the system, for simple authentication needs.

Because this container is designed to be a simple and easy way to share a directory of files, it skips many more advanced features of samba and AD. All file access takes place as the smbuser user and group users. The USERID and GROUPID environment variables will be used for the smbuser and users user/group in the container.

This prevents most permission issues, also as users created in the container won't be created on the host running docker, there are fewer random IDs to deal with there. If you set USERID and GROUPID to a valid user on the docker server, the files will be owned by that user/group.

from samba.

Wait I'm curious: what exactly is the difference between the userid and groupid in -u and in the environment variables USERID and GROUPID?

from samba.

This container is a way to quickly and easily setup a simple share. All files are setup to be owned by one user and group (less to synchronize with the docker host). To set the UID and GID set the USERID and GROUPID environment variables. Just set them both to 0 and you should get the results that you want. Hope that helps.

from samba.

It worked! I just thought -e GROUPID=0 -e USERID=0 is equal to -u "root;root;0;0"

from samba.