Thanks, plenty more to come!

yes. we can't afford clunky machines running at 100w and cost $200 electricity per year. So I double up things by hosting pbs, nas all in the same pve host. And backup all vms/lxcs to pbs, including pbs and nas lxc themselves. Reminds me of the cartoon where the snake eating its own tail... LOL

​@@fool9111z what is a pbs? thanks in advance

Thanks, glad it was useful

Same for me, thanks a lot !!!

Thanks, appreciate the feedback

Glad it was useful, thanks for the comment.

Glad it worked, thanks for the feedback

Wow, thanks! 👍

Glad it was helpful!

That's great, thanks Will

Thanks for the feedback, you're welcome 😁

Glad it was helpful!

Thanks, really appreciate that feedback

Thanks, you're welcome

You're welcome

Hope it helps :)

Thanks, yes I'll come onto ansible soon, it's a complex topic.

No, I will take a look. Previously I've used syncthing

Provided it can access over the network (e.g., firewall rules) it should be fine.

I think it's similar to a VM, you can just mount it. I only use unprivileged though.

@@Jims-Garage I installed a new unprivileged lxc and was able to see the files in the NAS using "ls /mnt/nas", but when I tried to add the folder to the media library it's empty and I'm getting this error in the logs: System.UnauthorizedAccessException: Access to the path '/mnt/nas' is denied Do you know how I can fix this? Thank you.

It was to display both options, in case you want to script etc. plus, it's easier than having to open each file

Interesting, I will test. My understanding is that it would dynamically appear as it would on the host.

@@Jims-Garage i want to avoid installing autofs in the host. I have been using autofs in vm. It is all solid. But a tool like this can be disruptive to a custom host kernel

@@Jims-Garage i did some research looks like the key is to have _netdev and x-systemd.automount flag. The first is to delay mount until the network is up. The latter is to delay until the mount is needed. I can actually see when rebooted, the host mount point belongs to root:root, until I did a ls on the mount point, after that the mount point ownership changed to pbs:pbs, indicating the mount occurred after ls.

Thanks. Amend the docker compose directory to match your setup (use whatever folder structure you want, or create one called docker-compose).

@@Jims-Garage thanks for taking your time to reply. Maybe I sound stupid, but I guess this structure must be already created (I don't know what my current home directory in in this container) and I don't know if docker-compose is already created and I need to edit it.

@@juansebastian79 you essentially need to change the left hand side of the colon in the docker compose file to match your setup. Change /ubuntu to your username, create a folder called docker-compose in /Ubuntu or just change it to whatever structure you want.

@@Jims-Garage thank you, I'll have a look. As soon as I finish with this one I'll check your other videos because I reaaly like your style

@@juansebastian79 thanks 👍

Did you set to read only?

11000 is the gid in LXC, 10000 is the equivalent in Proxmox

@@Jims-Garage Is it possible to specify a specific group on the lxc machine (changing lxc_shares to smth else) ? For example, I have 2 shared repo and I want to give access to only one of them to a user.

I believe that would work, however I wanted to cover both angles as I'd invariably be asked.

It's likely a permissions issue. Try mounting the LXC with rwx

@@Jims-Garage By that do you mean changing, mp0: /mnt/lxc_shares/nas_rwx/,mp=/mnt/nas,ro=1 to mp0: /mnt/lxc_shares/nas_rwx/,mp=/mnt/nas,rwx=1 ?

@@Jims-Garagepermissions issue it was, needed to add user ‘Plex’ to the lxcshares group!

Turns out that to make it work I had to use the UID and GID for jellyfin in the fstab.

If you mount to both hosts it should failover. I don't believe privileged is any different.

@@Jims-Garage The fix if you want to add to your script would be to add shared=1 at the end = mp0: /mnt/lxc_shares/nas_rwx/,mp=/mnt/nas,ro=1,shared=1

I think it waits 5 mins then continues regardless.

Oh 😅 maybe I was too inpatient.

I see no reason why it couldn't, but you'll need to make sure that permissions are right across all of the VMs/LXC

@@Jims-Garage OK so I gave it a go and I used a helper script to create the LXC its unprivileged. I used your guide and made sure to add the back up user too. i can read and write to the share in the PBS shell but when it comes to backing up it always fails. looks like a permissions error but i cant seem to figure it out.. Error: fchmod "/mnt/nas_pbs/ct/101/2024-05-30T12:16:46Z/pct.conf.tmp_FPsn3z" failed: EPERM: Operation not permitted. hope you can help

@@sohail579 looks like a permissions issue. You likely need to add the pbs user

@@Jims-Garage I did that at the start I used your guide and did this "usermod -aG" for the user which is called "backup" is there a way to check if there is another user also? from the log it looks like its writing a temp file and when its changing the temp files permission it fails

Yes, I mentioned that in prior videos. Change the render group (typically 128)

I prefer CIFS for simpler compatability with Windows and mixed environments. If a purely Linux environment then NFS would make sense and is also more performant. This same process applies for both.

@@Jims-Garage This video came at a good time. I've setup 4 proxmox nodes with HA for my HL, and jellyfin-LXC does not like auto mounting the shares 100% of the time when being migrated. I'll test this set up on it, I will try NFS over SMB since nothing in my house uses windows anymore... except my work laptop, but that's segregated from my home network anyways.

You could use variables to remove that issue, but even in a worse case it would give you access to the SMB, not the Proxmox host.

@@Jims-Garage "You could use variables to remove that issue" But even with variables -- that would still be storing the password in plain text, no? "but even in a worse case it would give you access to the SMB, not the Proxmox host." I think that will depending on how you have your SMB share set up. If you have a separate SMB share that's hosted by another system -- that will put that system, potentially, at risk (by storing said SMB password in plain text). Conversely, if you want to consolidate your system such that your Proxmox host is ALSO the source of your SMB share, then this statement wouldn't be true, as you would be risking the Proxmox host itself.

@@ewenchan1239 the LXC shouldn't have permissions to read the files owned by root on the host

@@Jims-Garage "the LXC shouldn't have permissions to read the files owned by root on the host" If you have another LXC container that's managing the SMB share, and that LXC container runs on the same Proxmox host, you're still going to have this issue. In either case, storing the password in plain text is generally a bad idea, and there ought to be a better way of being able to do or accomplish the same goal that this is trying to accomplish, without the all of the downsides that comes with storing said SMB share password, in plain text. I would think that you would agree that storing (or hard coding) your SMB share password, in plain text (or any password for that matter), would be generally a bad idea, no? Furthermore, for the media files -- if you don't want those files to be owned by root, on the host, then the media files should probably be uploaded/stored on said host, under a different user account, in the first place, no? Therefore; even if the Proxmox host was also the SMB host (as a result of consolidation), from the user account perspective, the media files won't be owned by root, but you'd still be accessing the host as a result of having a SMB password stored in plain text. The concern shouldn't be where you are hosting your SMB files, but rather, that the LXC container is mounting that SMB share using a password that's stored in plain text. I would think that you'd agree that that's not a great way to store a SMB password.

@@ewenchan1239 as stated, you can use variables to hide it and protect with user permissions. At the end of the day something always has to be able to read it. LXCs cannot host SMB, that's why you need to mount on the host and share it. Permissions are ultimately determined by the smb, then the user the host mounts it with.

That's great, thanks