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
Thanks for the suggestion. I tried and it still doesn't work. I updated the google docs notes with my steps if you want to see what I did.
Hmm, well it doesn't seem to be any problem with the docker compose then as best as I can tell. I picked a random ext4 flash drive and replicated your setup with the UID and GID set and it seems to work fine:
I was able to play the PXL.mp4 video from my desktop and write back the test.txt file
Have you checked the logs with
docker logs -f sambato see if there's anything there?Also you could try to access the HD from within the container, using
docker exec -it samba bashand then cd into /storage and see what happens.I'm CURSED I tells ya! I'll look at the logs tomorrow. Good to know that you can get it working. Maybe I'm close then.
What displays when you run "id" as your user? You'll want it to match what your inputting in the docker compose. I may have missed it but I didn't see you identify what your personal UID and GID are in the Google doc.
As a janky fallback, what if you just added a new smb user and password and see if that one connects: sudo smbpasswd -a