Milspeccqb

I have a VM on the unraid server that I have in a separate subnet. That subnet can't reach the subnet with the unraid server front end. I am trying to use the "unraid share mode" feature to share some of the directories to the VM. But I want them to be shared to the VM in read only mode. Is that possible? I don't see an option for that on in the vm config page. Is there a setting somewhere in the shares themselves or possibly in the settings that I'm not seeing?

Running into trouble with one of the plugins, and I need to run a pip install to fix it, but I cannot find pip anywhere in the container. I see references to it in the past but it doesn't exist in those locations anymore? Did it get removed?

Have been using a separate plex server for years without any issues. Recently upgraded to 7.1.2 and then these problems started cropping up. Specifically streaming will halt on the plex server and then you have to wait a few minutes and you can restart your show. On the plex server, which has an unraid share as a mount, I see this error on the plex side: Aug 11 03:56:26 plexserver kernel: [1387274.154052] CIFS: VFS: \\192.168.1.5 has not responded in 180 seconds. Reconnecting... Aug 11 03:57:26 plexserver kernel: [1387334.220430] CIFS: VFS: \\192.168.1.5 Send error in SessSetup = -11 I don't always see corresponding logs on the Unraid side but occasionally this will show up at the same timestamp in the Unraid syslog Aug 9 22:49:26 unraid smbd[1500923]: [2025/08/09 22:49:26.939894, 0] ../../source3/smbd/smb2_read.c:264(smb2_sendfile_send_data) Aug 9 22:49:26 unraid smbd[1500923]: smb2_sendfile_send_data: sendfile failed for file media/movie.mkv (Broken pipe) for client PID=1500923,CLIENT=8beae7b4-904b-3041-a678-2a029c90c722,channel=0,remote=ipv4:10.0.0.10:49670,local=ipv4:192.168.1.5:445. Terminating Not sure where else to look for logs of what might be going on. Any possibility it's related to my upgrade to 7.1.2?

I have not but I guess that could work. I don't "think" backing up the data would be affected if the container is running. It does say "NOT RECOMMENDED" next to that option. What are the implications of setting that?

Is there a way to prevent certain containers from being restarted after the backup? I have a script that handles about half of my containers in a specific way but I still want them backed up. Currently when those containers are started with the plugin they fail to start and the backup generates errors.

I have some containers that I pulled down through the Apps marketplace and several others that I manually pulled and ran with a script. Right now the ones I manually pulled are refreshed every day via a User Scripts script. That process works fine. What I would like to be able to do is, ssh into the unraid server and run "Apply Update" from the docker page UI but do it via a script or just CLI. The problem is if I pulled the container from the marketplace, it's config is completely controlled by the UI. And if instead I ran commands in the terminal to pull the container via the CLI it's config is completely controlled by the commands I ran and I cannot see or manipulate the container settings from the UI. It would be nice if those things were harmonized or at the very least I knew how to run "apply update" or start, stop, change settings of the marketplace containers from the CLI but still remain a marketplace app and have it's config visible and editable from the UI.

You can see attached where I've defined the ports but obviously as you've said if I set a custom IP it ignores those. Possibly some sort of note indicating that when setting the network type to anything custom. It's difficult to show but when launching the WebUI from the docker page it uses the correct port instead of the ones I defined. On a separate note, would it be possible to create a separate docker NAT for several other containers? Such that I want to setup a reverse proxy on 80 / 443 for several containers however I don't want to interfere with the unraid host UI running on 80 / 443. Basically have Unraid on 192.168.1.10 using 80/443 and then have a Traefik container on 192.168.1.20 on 80/443 and then have several containers not accessible from outside that Traefik will manage.

I'm running a container on a custom port but it appears to not be listening. The container is using Custom: br0 as it's network type and is set for a custom IP. When I add the container I set custom ports and the interface appears to show me the that it's actually using the custom ports I set on the docker page. But when I try to access it on those ports I get nothing. If I use the default port the container wanted to use I'm able to access the webpage. I also curiously found that even though the docker page shows the port mapping that I set if I click the container image button and select "WebUI" it launches the original default port. It feels very much like the container is not listening to the custom ports I'm setting. Is there a place where I can find out what ports are being set when the container is launched in the terminal? Basically I'm trying to find the settings in the unraid system where the docker launch commands are stored.