Hi, I made this post a few days ago: https://lemmy.world/post/27391713 And I’ve been trying a lot of stuff and it doesn’t work and it’s driving me nuts. Now I tried again from the bottom and wrote down everything. You can see my notes here: https://docs.google.com/document/d/1vPplJhjZ13j1A2mEzHGS1B_sPSThE3LHxnGW82_F6Is/edit?usp=sharing Can anyone tell me why I keep banging my head against a wall here? Thanks :)
Update: It worked all along. All I needed to do was restart my windows machine and the errors would go away and I could enter the share. Good times.
You must log in or register to comment.
Don’t do this
Samba was not designed to be containerized. Install Samba native and try again. I’m almost certain the problem will go away.
Anyway, I would recommend you read this page https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs
Samba was not designed to be containerized.
There are some things that shouldn’t be containerized even tho they can be. I can see the benefit of a user wanting to containerize everything…it’s one neat little package. I look at on a case by case basis. For instance, Caddy I installed on bare metal instead of a container even tho there is one for Caddy.
Try the users suggestion from the other post and run “ls -an” to see the numeric user IDs rather than the names you’re assigning. I’ve recently been building a new server with proxmox and learned this same lesson already as user “1000” gets assigned as user “100000” inside containers there to prevent it from having host permissions automatically from my understanding.
Do I need to enter the container bash and change something then? I tried adding UID and GID to the docker compose file, but it still fails. I updated the google docs notes if you want to see my steps.
OK let’s run through some debug steps.
Test to see if samba is working by using a docker volume instead of trying to mount a file path.
If that works we can then assume its purely a file permission issue. U can check/test that by opening a shell inside the docker container and doing investigation from their.
If from the container shell u have perm issues then u will probably need to use the docker parameter to specify the user id of the container to match that of ur host or alternativly set the filesystem to match that of the container (this will lock u out of ur servers user access to the filesystem as u will no longer be owner).
If the container shell has perms to do shit in the mounted volume then it’s a samba config issue. I’ve never done it myself but I’ve heard that samba is a bitch to configure.
Does the docker user have permission to that folder?
How do I tell? In the docker-compose.yml file I put the user and password for my server user. I thought that was going to make it work?
