Selfhosted

49527 readers

933 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

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

-1

samba docker compose help (lemmy.world)

submitted 3 months ago* (last edited 3 months ago) by basic_user@lemmy.world to c/selfhosted@lemmy.world

4 comments fedilink hide all child comments

Hi, I've tried running samba from docker compose on ubuntu server with this resource https://hub.docker.com/r/dockurr/samba I changed the default volume from "- ./samba:/storage" to "- /mnt/my_ext_hdd/my_dir/my_subdir" The container deploys fine, but I get permission error when trying to access the shared volume from windows? Anyone with some suggestionshoew to fix? Thanks

you are viewing a single comment's thread
view the rest of the comments

[–] foggy@lemmy.world 0 points 3 months ago (1 children)

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.

[–] sugar_in_your_tea@sh.itjust.works -1 points 3 months 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.