Selfhosted

44058 readers

547 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

Help with lxc write access (discuss.tchncs.de)

submitted 1 week ago* (last edited 3 days ago) by laggytoast@discuss.tchncs.de to c/selfhosted@lemmy.world

12 comments fedilink hide all child comments

I need some help with my setup please, I am fairly new to selfhosting and the information I found searching hasn't helped me understand what is wrong. But I have miniPC running proxmox with all my stuff running jellyfin/arr stack etc. I then have another machine running my file share using SMB (maybe this is the wrong way to do it). I can add the share to my datacenter in proxmox and see it and but I cannot get my unprivileged container to write to the share. I can get privileged containers to write when I mount using cifs but this I read this is bad practice.

I have changed permissions on the file share to try give write access, I have tried Option 3 from this link I have been through this reddit thread and others.

Should I just make the lxc's that need to access the file privileged or is there something I am just not understanding here. I assumed this would be a fairly common setup and be fairly easy to configure but I am often wrong.

UPDATE: I changed to use NFS to manage the files and followed this guide allowing both the lxc and the main node on proxmox access to the files and this has solved the issues for me. My file share is just shared from a Debian server I am hosting potentially I will come across this issues when I swap to TrueNas in the future.

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

[–] corroded@lemmy.world 1 points 1 week ago* (last edited 1 week ago) (5 children)

I'm leaving this here for continuity, but don't follow what I said here. I have my containers set as privileged. I was wrong.

I have a server that runs Proxmox and a server that runs TrueNAS, so a very similar setup to yours. As long as your LXC is tied to a network adapter that has access to your file server (it almost certainly is unless you're using multiple NICs and/or VLANs), you should be able to mount shares inside your LXC just like you do on any other Linux machine.

Can you ping your fileserver from inside the container? If so, then the issue is with the configuration in the container itself. Privileged or unprivileged shouldn't matter here. How are you trying to mount the CIFS share?

Edit: I see that you're mounting the share in Proxmox and mapping it to your container. You don't need to do this. Just mount it in the container itself.

[–] egonallanon@lemm.ee 1 points 1 week ago (1 children)

Can you mount SMB shares in unprivliged containers? I thought that was blocked.

[–] corroded@lemmy.world 1 points 1 week ago

I believe you're correct. I didn't realize that I had my containers set to privileged. That would explain why I've never had issues with mounting shares.

load more comments (3 replies)