Selfhosted

45341 readers

1085 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

[email protected]

samba docker compose help ver2 (lemmy.world)

submitted 5 days ago* (last edited 15 hours ago) by [email protected] to c/[email protected]

15 comments fedilink hide all child comments

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 are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 5 days ago

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.