I have been using linux for a couple of years already, very casually, just browser, media, games. Recently I bought dell micro pc and installed proxmox on it. I don’t have a lot of hdds or raid or anything, just one 6tb usb external drive. I know, I could lose everything, but I don’t have anything important in there, just media. It’s a relatively new drive, so I hope it will hold for at least half a year, and then I plan to buy proper hdds.
Hdd is connected to the proxmox host with usb, and then with mount points to lxc containers. Audiobooshelf, samba, qbittorent, all containers are debian 12.
When I download book with qB lxc, it automatically shows up in audiobookshelf (abs) lxc thanks to mount points. Abs can play it but, I can’t change cover, delete, move it etc, because of permissions. This screenshot is from proxmox host.
Same thing happes when I manually upload the book to audiobookshelf, then other lxc containers have problem accessing it. Or when I upload something to the server with samba.
I know how to change it with chmod and chown, but when I download new book it is the same thing again, I don’t want to manually change permissions and ownership every time new folder/file appears in hdd. In lxc container I cant even change ownership, it says: “Operation not permitted” even though I have root.
This is my samba config. It’s terrible and unsecure, but after 2 days of trying to make it work, I just wanted to try everything. I will probably switch to nfs, idk if it will help.
I’m really lost, idk how to make lxc containers talk to each other through those mounts points without breaking permissions/ownership. Is there some other way? Idk if there is a very simple solution and I just made fool of myself. I know that root and 777 eveywhere is bad idea, but I wanted to at least first get everything working. And I don’t plan to connect anything to the internet in the near future anyways.
It’s really late here, and I have to work tomorrow, so I won’t be able to reply until tomorrow evening.
I had something that sounds similar to this I think, using Samba and Docker; the issue turned out to be related to mapping the UUID on the host system to the same UUID in the container. Full disclosure, I couldn’t remember the details so I asked chatgpt to jog my memory for this next bit:
When mapping a UUID from a host system to a UUID in a container, you might encounter the following issues:
1. Namespace Conflicts: If the UUID is used to identify unique resources (like files, devices, or network interfaces), having the same UUID in both the host and container can cause conflicts or ambiguity.
2. Isolation Breakdown: Containers are intended to be isolated from the host system. Sharing UUIDs can lead to unintended interactions or dependencies between the container and the host.
3. Consistency Issues: If the UUIDs are different, it can create inconsistencies, especially if the container expects the same UUID for resources to maintain state or continuity.
In general, it’s not a problem if UUIDs are different between the host and the container as long as the container operates within its expected scope and resources are correctly mapped and isolated.
Topic starter don’t use docker containers. He use lxc containers. LXC is virtual machines on host kernel. Case is that: He have 3 virtual machines with shared disk. In 3 VMs have 3 different applications. Applications work under different users and can’t rewrite data on shared disk. That is user permissions problem.
I’ve never used LXC, I thought it was like a native container system and that the same issues I had might occur with container systems other than docker (such as podman, or what I thought LXC was). Sorry for being wrong when I was trying to contribute, I know I’m inexperienced but I’m not entirely stupid despite all appearances. I’ve had a pretty bad day and your condescending phrasing here is just the dingleberry on top so I’ll tell you what, I’ll delete my drivel and stop trying to participate here. Thanks.