this post was submitted on 16 May 2026
33 points (100.0% liked)

Selfhosted

59861 readers
673 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

https://kb.synology.com/en-global/DSM/tutorial/Docker_container_cant_access_the_folder_or_file#x_anchor_idcd3f1170a3

Why allow "everyone" to have read write permission to shared folders in order to run container manager? Wouldn't this be insecure?

you are viewing a single comment's thread
view the rest of the comments
[–] Onomatopoeia@lemmy.cafe 2 points 4 weeks ago* (last edited 4 weeks ago)

To add to this, SMB implementations on Linux today simply respect the archaic model MS developed for LAN Manager (Windows 3.1, 1980's), before Windows had local user permissions (NT 3.51 mid 90's).

MS saw share permissions as a mechanism to provide admins some level of control for the small networks.

Once NT became the standard in business, we started ignoring share permissions and just letting file system permissions manage everything (since that could be managed via domain credentials).

It's a whole lot easier and more secure to manage Groups in the Domain than a bunch of share permissions, and they're lots more granular.

So we're stuck with share permissions though they're not all that useful - so most people (everyone?) simply ignore them and use just file system perms, which you have to manage even without shares.

TL:DR Share perms are a legacy thing and can simply be set to everyone read/write