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:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Proxmox maps user ids between itself and lxc containers and it took me a bit of time to figure it out. I would highly suggest reading the following link as it's how I worked it out. I ended up chown'ing to 101000 which maps to user 1000 - the default user - in my lxcs.
https://www.itsembedded.com/sysadmin/proxmox_bind_unprivileged_lxc/
I have had these permission issues in the past. Once I switched to mounting directly in the LXC they all went away.
Figure out the uid/gid (numeric) for the user in lxc, then change the data permissions to those.
Or should i solve it by chmod instead of owner/group?
I’m making some assumptions, namely that you’re using an unprivileged LXC container and the mount point is a bind mount.
Unprivileged LXC shift user ID numbers so that an escape won’t result in root access to the host. The root user (uid 0) in the container is actually uid 100000 from the perspective of the Proxmox host.
What I usually do is set ownership of my bind mounts to that high-numbered ID (so something like chown -R 100000:100000 /path/to/bind/mount) from Proxmox. Then the root user in the container will be able to set whatever permissions you need directly.