lm.inu.is
  • Communities
  • Create Post
  • Create Community
  • heart
    Support Lemmy
  • search
    Search
  • Login
  • Sign Up
hardful9856@programming.dev to Selfhosted@lemmy.worldEnglish · 3 hours ago

Why allow "everyone" to have read write permission?

kb.synology.com

external-link
message-square
4
link
fedilink
15
external-link

Why allow "everyone" to have read write permission?

kb.synology.com

hardful9856@programming.dev to Selfhosted@lemmy.worldEnglish · 3 hours ago
message-square
4
link
fedilink
My container cannot access the mapped folder or file and displays
kb.synology.com
external-link
Synology Knowledge Center offers comprehensive support, providing answers to frequently asked questions, troubleshooting steps, software tutorials, and all the technical documentation you may need.

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?

  • anamethatisnt@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 hours ago

    I mean unless specified otherwise most Synology container management dockers will run as root. With that said, if you want to secure things then there are guides.

    An alternative path would be to setup a specific docker user and use docker compose to use that user when installing images
    https://drfrankenstein.co.uk/step-2-setting-up-a-restricted-docker-user-and-obtaining-ids/

    Jellyfin example
    https://drfrankenstein.co.uk/jellyfin-in-container-manager-on-a-synology-nas-hardware-transcoding/

    From there you could go further and use the guides above to create one user per docker image and give them different permissions depending on need.

Selfhosted@lemmy.world

selfhosted@lemmy.world

Subscribe from Remote Instance

Create a post
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world

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:

  • 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!

Visibility: Public
globe

This community can be federated to other instances and be posted/commented in by their users.

  • 1.59K users / day
  • 3.33K users / week
  • 5.94K users / month
  • 16.2K users / 6 months
  • 2 local subscribers
  • 59.2K subscribers
  • 6.27K Posts
  • 152K Comments
  • Modlog
  • mods:
  • Ruud@lemmy.world
  • Loki@lemmy.world
  • CannaVet@lemmy.world
  • devve@lemmy.world
  • HybridSarcasm@lemmy.world
  • HybridSarcasm@lemmy.hybridsarcasm.xyz
  • BE: 0.19.15
  • Modlog
  • Instances
  • Docs
  • Code
  • join-lemmy.org