aspiziri

Thank you for all of your investigations and work to pull this together! Clearly a lot of work went into it. Reading through this its also clear that I stood no chance of figuring it out on my own (previously leveraged NerdTools - and NerdPack before that - for python/borgbackup). Am I reading this thread correctly that to migrate away from NerdTools for my borgbackup install to this "native" solution I simply download these three attached packages, I place the python file in my /boot/extra/ directory and reboot my box which will install python. From there I can use python's PIP to install the other two packages? How are things like version bumps from borg handled? I assume an entirely new set of compilations need to be generated following the steps you did above? I ask as it seems a bit over my head and am worried I'll be installing a point-in-time version of python/borg and then stuck without the skillset to ever upgrade for bug fixes, etc.

Got it - ok thanks. Sounds like I only have one path then so things are pretty clear: Use NerdPack to uninstall any existing "packs" Uninstall the NerdPack plugin Upgrade to 6.12.x Install NerdTools Reinstall any "tools" that I need Update my User Scripts, etc. to account for any changes that come from this (ideally none?)

I am currently running 6.9.2 and have been looking into upgrading to latest and what it would take. One of the things I have found is that NerdPack was deprecated with the 6.11 release and has since been replaced by NerdTools from CA. My question is: If I simply perform the update to unraid what actually happens to the "already installed" nerdpack services? Do they continue working but with no way to manage them anymore (aka: uninstall everything first)? Do they disappear? If I install NerdTools and then re-install the corresponding services should all my user scripts continue working "as is" or do I likely have a bunch of tinkering in my future? Wondering if anyone already went through this process.

According to the dockerhub page there is literally only a single listed known issue: "Saving and restoring settings backup via the BlueIris interface does not work!"

+1 on this. I'd love to understand even at a high level the performance and resource usage comparison between the two.

I'm hitting the same issue that alael is using the default settings. As soon as the docker starts it hits this and fails out. I followed the guide video to make sure I removed the old version, etc before trying to install and run the latest so not sure what would be going wrong. Edit: It appears that switching to method 2 for downloading in the template does not have this error but instead the logs seem to indicate the download never completes. When I open the macinabox_Big Sur.log file I see I am going to download BigSur recovery media. Please be poatient! . . Product ID 001-83532 could not be found

Update on my issue: It does appear the setting is no longer available on the edit VM page but it can be changed. You need to do it from the VM list. Click on the name of the VM in the list and it will expand to show more details. From this additional details is where you can edit the vdisk size.

I've got the same issue on 6.8.3. Did we lose the ability to change vdisk size with the 6.8 upgrade?