snoopy86

This is old Logitech docker. It's removed. You need to switch to my LyrionMusicServer. You just install it and point to the same folders. Logitech was renamed to Lyrion.

I have multiple dockers. You need to be specific :) Are you talking about Logitech, Ubuntu, FFmpeg,...?

Hi, which docker?

Any updates on this? Looks like Roblox patched this workaround...

You are correct. This issue should be looked at by the dev team. We cannot have the GUI breaking up what is done in the XML or other way around. Not acceptable.

Adding this also here. https://forums.unraid.net/topic/198521-unraid-os-version-725-available/page/2/#findComment-1621088 To sum up, the driver i need to have is v580.159.03, and it gets overwritten somehow with the latest every time i do an update, even though v580.159.03 is selected. Plugin is v 2026.05.01. Also, the screen when you click update & download is blank, so i always have to download it manually via terminal with /usr/local/emhttp/plugins/nvidia-driver/include/download.sh

I updated the plugin to version 2026.05.01 before the Unraid update, and the outcome was the same.

Whenever i update Unraid, it messes up the Nvidia drivers for me. Because i have one GPU that needs v580.159.03 and it updates my driver to the latest even though i had v580.159.03 selected. Not sure this is connected to Nvidia plugin or Unraid.

There is a bug in the plugin. When you put a link ghcr.io/something/something in the repository tag in the template and then install the app, the repository URL looks like https://registry.hub.docker.com/r/ghcr.io/something/something

I have two Docker containers that have their network set as br0. I'm running them like this with different MAC addresses "Extra Parameters": --cap-add NET_ADMIN --mac-address 02:42:ac:11:00:02 --dns xx.xx.xx.13 --dns xx.xx.xx.23 They also have "Fixed IP address" set. It works just fine until a restart. When Unraid restarts, you cannot ping outside of those two containers. For example, ping 8.8.8.8 is failing. What I need to do is remove the "Fixed IP address", start the container, set "Fixed IP address" back to the same IP that was there initially, and then everything works again. Does anyone have any clue why this happens?

Yes, you can use your own parameters.

@BoKKeR tnx for maintaining this. Do you know why the statuses of VM's are unknown in HA? It is just a matter of sending this info trough MQTT because on the UI I can see that the API has this information.

Hi @janpeeters, sorry for the late response, but I have checked this, and there is a Tidal Local plugin available in LMS plugins.

@dlandoni'm getting this errors with the DB and the container does not work properly. Any ideas?

@itimpiOne thing i'm not clear is why can't we treat this change from REISERFS to XFS the same as a failed drive. When the drive fails (let's say this drive is REISERFS 1GB) you remove it and change it with another drive (2GB). The parity then does it's magic and the drive gets populated again where you choose the filesystem. Can't the same process be done with this?