Recent content by samwathegreat

When someone asks for help (especially someone with more of a reputation than you) and you reply with "chatgpt it", that's rude. And it's not helpful. And it detracts from the community and discourages people from asking for help. Also, as I stated, this install goes back to early Proxmox 8 -...

Don't be a jerk. Just don't reply ;) I'm not interested in chatgpt's answer.

Hey Folks, I've been noticing lots of spam in my system log - every 10 minutes, I get the following: Nov 20 10:05:01 pve CRON[3946582]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0) Nov 20 10:05:01 pve CRON[3946584]: (root) CMD (command -v debian-sa1 > /dev/null &&...

I finally got it to work. Installing it produced an error about how arp-scan was required but not installed. But after rebooting container, it works. The built-in "update" script from installing the container from community-scripts appears to still be working too. I'm not seeing the log...

Won't let you uninstall:

after cd arp-scan, the command ./configure doesn't work. Am I missing a command?

This is fantastic. Can you advise a step-by-step guide on how to implement the fix on an existing watchyourlan container?

Hi Guys. This is a strange one... I have a standalone node named "ma", and I see my logs utterly spammed every second or two with the below error. This is really strange because this has ALWAYS been a standalone node, and it's name "ma", not "pve". The certificate configuration seems to be...

Sounds like you didn't bind mount, then. To bind-mount you have to edit the lxc conf file as I've described (look up bind mount in the proxmox FAQs for more info). Before you do that make sure you have actually created your ZFS dataset.... For example, if your ZFS raid 1 is called "myzfs"...

I'm not getting what you're trying to do... Are you asking what the command for the bind mount should be? If so, it should look something like this: mp0: /mnt/tank/immich,mp=/mnt/immich When the first part corresponds to the exact path on the HOST. If you are using ZFS you should have...

The mapping is actually unnecessary, and I feel there is a better way to do it. All you have to do is recursively "chown" the zfs dataset to the UID/GID the program on the container is using to write + 100000 So if the user (on the container) is immich:immich (just an example here), and say...