Submitted 1 week ago by basic_user@lemmy.world to selfhosted@lemmy.world
Hi, I’ve tried running samba from docker compose on ubuntu server with this resource hub.docker.com/r/dockurr/samba I changed the default volume from
My advice (if you can): Create a dedicated NAS VM and use samba the native way.
Or use a dedicated storage server with native samba.
The easy way, but not the most secure: identify GID and UID of files created by your samba docker container with "ls -la". Then assign ownership of files and directories of shared volume to that user/group "chown -R GID:UID /path/to/shared”
Do I just enter the container shell and check GID and UID of a random file?
Does the docker user have permission to that folder?
foggy@lemmy.world 1 week ago
You’re running into that permission error because of how Docker handles file permissions between the host and the container. It’s by design for security reasons. The user inside the container likely doesn’t have access to the mounted directory unless the UID and GID match what’s on the host. You can work around it, but it’s locked down intentionally.
Also, what’s the use case here? What do you need file sharing via Samba in a Docker container for? If it’s just about moving files in and out, docker cp or docker exec -it container /bin/bash might be easier.
basic_user@lemmy.world 1 week ago
Well, I’m trying to share from within the docker container. I just want to run the samba service from a container. The share is an external hard drive connected to the server. I want to be able to move files to and from the ext hdd.
foggy@lemmy.world 1 week ago
Okay, the permission error is almost certainly because the Samba process inside the container doesn’t have the right Linux permissions for the host directory /mnt/my_ext_hdd/my_dir/my_subdir.
On your server running docker, find the numeric UID and GID for that directory: ls -ln /mnt/my_ext_hdd/my_dir/my_subdir
you likely need to set PUID=<uid_from_step_1> and PGID=<gid_from_step_1> in the environment: section of your docker-compose.yml file for the Samba service.
Recreate the container (docker compose up -d --force-recreate).
WARNING: This assumes you are only accessing Samba from within your secure local network. Never expose Samba directly to the internet. Doing so is a major security risk and makes you a target for attacks.
sugar_in_your_tea@sh.itjust.works 1 week ago
Idk about OP, but I want to run all of my exposed services in containers for security benefits, and I use samba to provide an SMB share for Windows clients.