Selfhosted
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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!
view the rest of the comments
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.