bmartino1

the compose manger plus plugin is gaining traction and adds compose abilties to unraid. https://forums.unraid.net/topic/197334-plugin-compose-manager-plus/ this has my vote for implementation to the host os.

by default, the URaid of the Docker system allows us to set a location where the Docker appdata folder is. The default unraid option is folder "/mnt/user/appdata/" Example Docker edit By default, with this plugin the data is found under advanced: so I can see a Default master control setting. that sets the default Docker Compose stacks following the Unraid Docker setting. as by default the plugin saves them on the flash drive.. so the default stack location is located at: "/boot/config/plugins/compose.manager/projects" If I'm understanding the git clone and add to stack. These are the things that already exist that can be edited to fit the need. ? so the questioning then becomes how do you want to handle input of a stak project that can be git cloned and detected if any. some compose and projects require data and a setup script run to prebuild to your env... So I'm not sure a transition plan to add a git pull project into this plugin is in the making or works. But my understanding of the user's questions where the stack data is located is based on the settings of that stack or the project location which already have a set place and are editable.

see script: https://forums.unraid.net/topic/178033-bmartino1-user-scripts/#findComment-1478661 turn off / disable any times machine share via unraid web ui. Stop the array. go to settings> smb in smb extra make a manual share: [TimeMachine] path = /mnt/user/TimeMachine browseable = yes read only = no guest ok = no # time machien requires a samba user connected! valid users = samba_user root writeable = yes acl map full control = yes acl allow execute always = yes map archive = yes map system = yes map hidden = yes create mask = 0660 force create mode = 0669 directory mask = 0770 force directory mode = 0770 force user = root force group = root vfs objects = catia fruit streams_xattr fruit:encoding = native # If you want Unraid to advertise this as a Time Machine target: fruit:time machine = yes # If you want unraid asigned size quota ; fruit:time machine max size = 0 fruit:metadata = stream fruit:resource = stream fruit:locking = none # ACL + extended attributes ea support = yes store dos attributes = yes

you most likely have a permission issue. stop all dockers and run the set new docker safe perm

That would be awesome! I'd be interested in looking into the scsi connected and network boot variants. I wonder how hard it would be to render part of this to be used in something like pxe netboot. It is nice sometimes having the mem test and I often use the unraid USB for memtest and some quick Linux terminal commands for disc execution for recovery. But so far yes, the installer works great and I'm happy to see an evolution of this nature.

Would you be more willing to share or explain then on how one would use the unraid usb for the license then? I'm more trying to understand what your actual setup and requirements would be for this: https://unraid.net/blog/unraid-7-3-beta.1?srsltid=AfmBOopz_zT7WWOn5GDbJLneiqE988kR3ZRhxluxK-NZxTAXfleeHs7K Internal Boot and Licensing: Connected, But Not the Same ThingInternal Boot determines where Unraid boots from. Licensing determines what hardware your license is tied to. These are separate choices, and that distinction matters: Boot internally + and keep your flash drive for licensing Boot internally + and use TPM for licensing, if your hardware supports it Getting very little support. When I'm mainly just trying to get clear clarification requirements and expectations. As virtualed vtpm will be flagged (this is a good security thing) and unraid still needs something to validate and be a license. Example... Does this mean I can just pass a usb device and use that as a license only? or just use the usb at that point? I only bring it up as quite a few Motherbaords are using swtpm and software TPM firmware on board. Are all the software firmware TPM then not usable? -from the tpm 1.x bios move to support win 11...

Be Forewarned! with talking with support, they are still anti OS in a Hyper V and against Urnaid being virtualized and currently will not support this method. (It is only becuase its is in Beta this is sometimes the best time to attempt and take a look...) That said usb passing a license Unraid also works even in trial mode, as I was retesting this applicable use case for Myself and another... as they may also want a similar internal boot but are happy with the USB licensed pass-through atm(that is known working). it just would be nice for the VDisk to also be the internal boot and left be the mnt cachedisk for are docker enviroment for docker dev testing(something they have also advised aginst...). for pve backup. some in java virtual box were able to make a VDisk USB device as a licensed boot disk in the past... That said per support: Quote Thanks for following up. To clarify my previous email " I do apologize but we don't currently officially support the virtualization of Unraid, and don't have a VM option for the license key. (This forum link) As you may have seen, many users have had success with using USB pass through in the past. You could attempt this with the free 30 day trial license on a new USB. You can set up a trial key by using the unraid installer to install a qualified flash USB device. https://docs.unraid.net/unraid-os/getting-started/set-up-unraid/create-your-bootable-media/ Upon booting from the USB, the system will prompt you to complete the trial registration> So in thoery one could tranfer there usb key and or a tiral key once generated. Internal Boot is supposed to use the TPM and ZFS-generated GUID for it licensing. adational reall hardware may need to be passed to qualify and meet physical hardware and Unriad Licenseing standartds. While I have a free license I don't want to kill the curently licensed usb device thus the pictures and incomplete post above. More just a over view of some PVE based settings and proff of concept. at this time the beta will not move past testing due to licensing issues and access to other setups... with PVE I have sucessfuly allowed the pve host to handle disks and was able to map the host path via virtio fs and map points with out issues. thus the need for disk by id passing or a HBA is not alwys needed. taht sid this would still require teh unassinged disk and adatioanl bind mapping to /mnt/remotes/addons/teh datapath on host to properly use ont eh sytem... example: example user scirpt in unraid to pass host level disk paths. # Create mount points mkdir -p /host mkdir -p /mnt/remotes/RACKPVE_Dockers mkdir -p /nfs # Mount VirtioFS shares from PVE mount -t virtiofs data /host #Mke unriad and other things happy mkdir -p /mnt/remotes/addons/host mount --bind /host /mnt/remotes/addons/hostThe musing of a mad man testing things and doing things because I Can. Again, THIS DOESN'T MEAN ITS STABLE! And can only recommend following the supported recommendation and License TOS.

... https://github.com/bmartino1/unraid-docker-templates/blob/main/Guides/Compose/Immich/ImmichReadme.md Brandon Martino - Personal SiteImmich-on-Unraid-Docker-Compose-GuideBrandon Martino - Personal Site...

see also

Following information per the iso post and support. Thanks Limetech and SimonF! https://docs.unraid.net/unraid-os/troubleshooting/tpm-licensing-faq/ VM unirad will still need a USB passed. https://unraid.net/blog/unraid-7-3-beta.1?srsltid=AfmBOopz_zT7WWOn5GDbJLneiqE988kR3ZRhxluxK-NZxTAXfleeHs7K Internal Boot and Licensing: Connected, But Not the Same ThingInternal Boot determines where Unraid boots from. Licensing determines what hardware your license is tied to. These are separate choices, and that distinction matters: Boot internally + and keep your flash drive for licensing Boot internally + and use TPM for licensing, if your hardware supports it As another has said you could pass a USB formatted fat and Labled UNRIAD to act as the license only. This will act as a GUID license. to still use internal boot. but it would be easier to just use the USB for unraid. and pass the USB at that point...

Let's take a look around Yes, this installation makes the boot partition a ZFS Partition: I've noticed a small PVE QEMU virtualized unraid issues where its format doesn't allocate or read the VM disk even when set to raw. I ofter after in have to add 10 GB-ish more to the Virtual disk to help with disk size and format allocation. In my case, this is VM 101 and the disk is sata0 the PVE command to assign more data to the VM disk as I only gave 80 GB but as you can see per the web UI its reading 85... qm resize 101 sata0 +10GNote adding size doesn't change the partition. Usually, other disk commands are needed when you add storage to expand and use the added space... Power off and power on and lets take another look... (as this is/ was more for testing... ) I'm not ready to move a paid key over and boot mode requires a paid key can't do a trial at boot on beta instance for test... Given Virtualized HD is being read as "Invalid".) Unraid OS No Boot Device tower-diagnostics-20260401-1646.zip Outside of that, there side things I would recommend to a virtualized Unraid 1 set the pve qemu to run qemu guest tools as seen here: https://forums.unraid.net/topic/179219-guide-proxmox-virtualize-unraid-experimental-with-v7/#findComment-1484536 Thanks simon. we do this by editing the go file in boot cd /boot/config/ nano go as seen here: root@Tower:/boot/config# cat go #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp #Guest Tools /usr/bin/qemu-ga -l /var/log/qemu-ga.log -d

ISO installer boot Unraid internal boot setup The ISO lads and the initial Boot Process begin. We must first download the Uriad Zip file: We then select option 2 with the current ISO pointing at the beta zip file. By Default the Option is NO But lets see the Log and what it did: Thats it We now need to power off and tell boot options to boot to the HD first. It is better to Power off And now enjoy unriad booting form a HDD:

Some recommended side options for the web UI PVE and edits. One of the first things I do is keep the connections SATA at creation teh HD is sata 0 So let's remove the disk drive and readd it as sata 1. Now that the cd rom is removed, we need to recreate it. We alos want to add a VirtIO RNG and edit the display options to asist GUIi based installs via ISO With that done we now need to fix boot options and set the disk drive to boot. Now it time to start the console and enter BIOS by clicking in the console and hitting "esc" multiple times to get to the boot menu: The goal is to disable secureboot and enable custom Secure Boot keys. This should get you into PVE boot menu Go to Device Manger > Secure Boot Configuration arrow keys to the X and hit space bar and change standard to Custom Mode DON"T FORGET TO HIT f10 and y to SAVE! Then hit "esc" multiple times and hit continue to boot You have successfully set up Unraid for Generic Default Linux Secure Boot and Stable VM Boot

Step 1 setup PVE VM for unraid: Some Recommend PVE Options. First lets create a VM: It Is Important to Note THE internal Boot needs TPM and Potentaly Secure boot key... Pleas Note YOU MUST TURN OFF BALLONNING AND ALLOW KSM! Unraid exists in RAM even after boot. This is a bare min PVE configuration on lattest PVE version 9.1.6 as of writing.

Pined guide: https://forums.unraid.net/topic/29679-guide-virtualizing-unraid-on-proxmox-31/ PVE INSTALL guide: https://forums.unraid.net/topic/179219-guide-proxmox-virtualize-unraid-experimental-with-v7/ NEW Internal HD ISO Boot disk https://forums.unraid.net/topic/197992-new-iso-installer-for-testing/ So yet another Virtualize Unriad guide post.

I will retest and share data. Thank you.

Additional Data: The documentation link that was followed to attempt to assist others. Please see Support Post https://support.plex.tv/articles/repair-a-corrupted-database/ I think chuck PA scirpt might ahve a depper repair but that would require high level docker knowledge and the ability to execute the script manually in the original Plex Docker.(they may require docker mods and 3rd party docker adon to execute the script.) https://github.com/ChuckPa/DBRepair Which is what this docker is based off of. But I don't think the deeper level was added to that script. the plex forum would be the area I would ask for further support if attempting to repair. Notes for future users. example Plex fourm post: https://forums.plex.tv/t/database-is-corrupt-or-maintenance/882894

Page 111421: btreeInitPage() returns error code 11 [2026-03-31 22:22:26] Check : com.plexapp.plugins.library.blobs.db ok [2026-03-31 22:23:02] Vacuum : com.plexapp.plugins.library.db Error: stepping, database disk image is malformed (11) it means teh comand that is ran via autmatic fialed to coreclty edit and fix the database. Correct, sadlly it is better to delete teh dataabse and start over at that point. sorry. com.plexapp.plugins.library.db is corrupted enough that VACUUM cannot run on it. Your log shows two separate things: PRAGMA integrity_check on the main DB fails with Page 111421: btreeInitPage() returns error code 11 then VACUUM fails with database disk image is malformed (11) That means this is beyond a simple optimize/reindex pass. VACUUM only helps when SQLite can still read the structure well enough to rebuild it. Plex’s own docs say to try VACUUM and REINDEX for lighter corruption, but for deeper corruption the next step is low-level recovery with .recover, using Plex SQLite, not generic sqlite3. in theroy it can still be recovered but with that much damage it would be hard to fix.

I will give the iso a test in a Virtual PVE environment. Writing another guide how I did it in pve https://forums.unraid.net/topic/198068-guide-yet-another-proxmox-pve-unraid-guide/

I made a unraid lxc matrix Discord alternative that I'm running a few for quite a bit of folks... see post: https://forums.unraid.net/topic/127917-guide-matrix-synapse-w-postgres-db-chat-server-element-web-client-coturn-voice/page/4/#findComment-1611571

First, I want to Thank you For making this. This HAs helped in may areas for others! Now onto a small complaint... The only additional requirements / warning I would have is that you add the smb conf to the smb extra. # Custom SMB Shares plugin include = /boot/config/plugins/custom.smb.shares/smb-custom.conf Installing this plugin seems to purge the exising smb-extra file... It would be nice if you kept the data... root@BMM-Tower:~# cd /boot/config root@BMM-Tower:/boot/config# ls (I had nonsence in here of using overwride as a note to myself and found that oh, this says the smb file the plugin makes now instead...) In testing This plugin will overwrite any exising data. further you limit the share where I'm forced to click the folder paths. Where I want to copy and paste the long list instead of click click click to get to the sub folder... Other then theses 2 side complaints This is a Awesome Plugin. But I think I will stick to my override and overwrite... https://forums.unraid.net/topic/178033-bmartino1-user-scripts/#findComment-1478661

not sure if tempalte is pointing to the githb repo yet atempted to install form CA Stabe not beta. Downloading plugin plugin: installing: compose.manager.plg Executing hook script: CA_preHook Clearing Community Applications plugin cache Executing hook script: pre_plugin_checks plugin: downloading: compose.manager-package-2026.03.27a.txz ... plugin: compose.manager-package-2026.03.27a.txz download failure: Invalid URL / Server error response Executing hook script: CA_postHook Clearing Community Applications plugin cache Executing hook script: post_plugin_checks Plugin installed manula install form link is failing as well: https://raw.githubusercontent.com/mstrhakr/compose_plugin/main/compose.manager.plg plugin: installing: compose.manager.plg Executing hook script: CA_preHook Clearing Community Applications plugin cache Executing hook script: pre_plugin_checks plugin: downloading: compose.manager.plg ... done Executing hook script: CA_preHook Clearing Community Applications plugin cache plugin: downloading: compose.manager-package-2026.03.27a.txz ... plugin: compose.manager-package-2026.03.27a.txz download failure: Invalid URL / Server error response Executing hook script: CA_postHook Clearing Community Applications plugin cache Executing hook script: post_plugin_checks going to <!ENTITY pluginURL "https://raw.githubusercontent.com/&github;/main/&name;.plg"> https://raw.githubusercontent.com/&github;/main/&name;.plg hits 404, causing install issue atm. Please double-check the template path Thank you

cool, thank you looking forward to trying this.

is this compatible with the folder view 3 plugin chagnes? or should i uninstall both the compose manger and folder view 3 before attempting this plugin? https://forums.unraid.net/topic/197223-plugin-folderview3/

I added the docker xml into unraid. ?what issues are you having?