benfishbus

Earlier this month, the following was posted as an issue in the github repo for this plugin: So, maybe not dead after all?

When preview is set to "Icon only", there's no way to tell which containers are started/stopped. Please correct me if I've missed an option somewhere. Assuming not, I have some suggestions for how this could be addressed: Optionally restrict "Add preview open WebUI" to only started containers (since stopped containers' WebUI link is dead anyway, don't bother displaying it) Optionally limit preview to started containers Optionally include state icon (started/stopped) in "Icon only" preview

I was excited about the fixed MAC address feature but am concerned about collisions. If I set a container's fixed MAC address to the address Docker randomly assigned it, or some other address I made up, is there anything stopping Docker from trying to reuse it elsewhere? The MAC addresses currently assigned to my containers seem to span all the "locally administered" bits (X2-XX-XX-XX-XX-XX, X6-XX-XX-XX-XX-XX, XA-XX-XX-XX-XX-XX, and XE-XX-XX-XX-XX-XX) per wikipedia. Can we reserve one of those for only fixed addresses? Or are collisions so unlikely that I should just not worry about it?

Thanks! (yes, I was running 2026.04.01d)

The plugin won't allow me to rename a share. Literally can't type anything in the Share Name field. Tried disabling the share first, but it made no difference. What am I missing?

I opened one specific issue on github, but I appear to be having broader issues with this "request guard" blocking nearly anything I try to do. I can't enable "Lazy previews" or "Performance mode". I can't bulk move containers between folders. These both result in: A pop-up warning entitled "Runtime preference save failed" with the message "Request failed for /plugins/folderview.plus/server/prefs.php. HTTP 400 error - Blocked by request guard." An entry in phplog just like the one I get when trying to add a folder: "RuntimeException in /usr/local/emhttp/plugins/folderview.plus/server/lib.php:638 | Blocked by request guard." Am I the only one experiencing this?

I prefer hd over fhd quality and normally set this in the options file, but the quality preferences hardcoded into this container's script always take precedence. Could you expose the quality selection as an environment variable like you have other arguments/parameters? Ideally the filename output format would be similarly exposed. Also, not a big deal, but the script variable ATOMIC_PARSELY_FILEPATH contains a misspelling. Thanks!

I don't know. My current sources.list: https://mirrors.slackware.com/slackware/slackware64-15.0/slackware64/ 15.0 https://slackers.it/repository/slackware64-current/ conraid https://raw.githubusercontent.com/ich777/slackware/master/slackware64-15.0/slackware64/ ich777 https://raw.githubusercontent.com/shinji257/unraid_pkgs/main/slackware64-current shinji257

If you install the un-get plugin, you can install the necessary packages: un-get install mandb man-pages groff Unfortunately, the pages do not include find or many other useful commands.

I know this topic is old, but I got bit by this recently. An Ubuntu 20.04 VM that had been running flawlessly suddenly acts like it can't find the vdisk. It comes up in UEFI shell, and the only filesystems available are the unraid shares mounted via virtiofs. I checked the vdisk offline with qemu-img, mounted it on unraid as a nbd, mounted the main linux partition and copied some files from it. The vdisk seems perfectly fine. I didn't mount the EFI partition, maybe I'll do that and make sure something didn't get screwed up there. But I haven't monkeyed with this VM at all in a very long time. The only recent changes are upgrading unraid to 7.0.0 and installing regular Ubuntu 20.04 updates.

docker buildx install creates a 'docker build' alias This thread helped me out, thanks!

Sorry, I read the wrong tooltip - the Shares tab says it is "Primary Storage to Secondary Storage"

I upgraded my cache last September to a mirrored zpool of two SSDs. It is my first time using zfs. Lately I've been getting temperature warnings for both SSDs, and haven't been able to figure out why. I did notice one thing that seemed odd - the zfs dataset corresponding to one of my shares getting destroyed and recreated every day. Output from zpool history: 2024-07-01.03:40:02 zfs destroy cache/ben 2024-07-01.03:43:45 zfs create cache/ben 2024-07-02.03:40:01 zfs destroy cache/ben 2024-07-02.03:47:29 zfs create cache/ben 2024-07-03.03:40:11 zfs destroy cache/ben 2024-07-03.03:41:10 zfs create cache/ben 2024-07-04.03:40:02 zfs destroy cache/ben 2024-07-04.03:45:12 zfs create cache/ben 2024-07-05.03:40:03 zfs destroy cache/ben 2024-07-05.03:49:03 zfs create cache/ben Diagnostics attached. 5 shares hit the cache. 3/5 are "primary storage cache, exclusive access", and their dataset was created 9/19/23. 2/5 are "primary storage array", and their datasets were created 6/24/24 (shared) and 7/14/24 (ben). The timestamps line up with when Mover is scheduled to run. Is this a thing Mover is expected to do with a zfs cache? jimbob-diagnostics-20240714-1658.zip

Regarding sound? Not sure if this is what you're asking for, but virt-manager lists 3 models for me to choose from - "AC97", "HDA (ICH6)", and "HDA (ICH9)". I don't know if these are the options everyone sees, or just me based on my host hardware. I have always had success with HDA (ICH9). Virt-manager adds this to the XML: <sound model="ich9"> <address type="pci" domain="0x0000" bus="0x00" slot="0x1b" function="0x0"/> </sound> <audio id='1' type='spice'/> Can't remember whether sound actually worked in a SPICE session, or if I had to turn on/install RDP in the guest and connect that way...

The virtiofs support is working great with my ubuntu VM. I just had one small problem which I managed to solve with a workaround. Ubuntu could not automount via fstab an unraid share with the tag "media". I don't exactly know why. DMESG in the vm looked like this: [ 24.644594] systemd[1]: Mounting /mnt/unraid/ben... [ 24.647784] systemd[1]: Mounting /mnt/unraid/media... [ 24.669726] virtiofs virtio0: virtio_fs_setup_dax: No cache capability [ 24.679994] virtiofs virtio1: virtio_fs_setup_dax: No cache capability [ 24.685471] virtio-fs: tag </media> not found I tried additional shares, and all of them worked - but not the "media" share. I tried changing the order of the shares in fstab - same result. If I ran "sudo mount -av" at a command prompt, ubuntu would mount the "media" share no problem - but never at bootup. The workaround was to specify the "media" share manually in the vm config, using some other tag like "xmedia" - and suddenly ubuntu had no problem automounting the share. Now if only I didn't have to resort to xml or virt-manager to add a virtual sound card to a vm in unraid...

Text is all legible now, thanks!

No. Do you want a list of the plugins I do have installed?

6.11.0 release. Tried resetting Firefox theme in case it might be interfering - no change. Behaves the same for me in Edge. Just tried changing Unraid themes - "Gray" renders the same popup this way: Solves legibility for me. Unfortunately I also hate the layout of that theme, so would still love to figure this out. (If only Unraid made color scheme and layout separate options...) In experimenting with the different Unraid themes, I thought this seemed strange with the "White" theme: Guessing that Unraid's theming function is not as robust as it could be.

Problem: Pop-up dialogs created by compose.manager don't use unraid webui theme, leading to unreadable text. I use Black color theme. When I go to Edit Stack, the menu displays: Not unusable, but then when I go to UI Labels, it looks like this:

Thanks for making this. While we wait for whatever Docker changes await in 6.10, this is fun to play with. How about adding a Compose Logs button? Also, the plugin allows you to rename a running stack, then can't control it - i.e., you hit Compose Down button and it says no container with the new name is running.

I've been getting this too on 6.9.2 - the Docker page was basically unusable - and finally pulled diagnostics (attached). Docker.log was full of...something. Uptime on all my containers looked fine, though. Well, for some reason I decided to run docker container prune which cleared out all the stopped containers...and stopped the refreshing. I added back all the stopped containers I still need, which was easy because the templates were still there. jimbob-diagnostics-20220219-2131.zip

Agreed, it’s night and day. I had already enabled turbo, so the improvement for me was all down to CPU scaling. Would like to understand why this needed to be changed and what other consequences will be.

I have noticed the same thing. My Win10 VM ran like a top on 6.8.3, and since 6.9.0 it's unbearably slow. I regularly watched streaming video in this VM, and now it struggles even to load the smallest applications. I haven't run numbers on the performance, and would have no baseline to compare them to if I did. Unless some solution turns up, I'll have to go back to 6.8.3.

Yep, I have the same problem.