Saturday at 03:38 AM4 days 4 minutes ago, aaronwt said:I did another manual mover test today, on yet a different unRAID server. And like the other three, the mover progress bar stays at zero. Of course the file is actually moved. But, both progress bars never advance and they always show 0%.Any idea what could be causing this? because it is not isolated to just one system for me.I have seen other posts about this problem. Apparently, the progress bar does not moved until the first file is completely transferred. (You seem to indicate that you are only moving one file. In that case, if the proceeding is true, you would never see the bar move!)
Saturday at 08:02 AM4 days 4 hours ago, aaronwt said:I did another manual mover test today, on yet a different unRAID server. And like the other three, the mover progress bar stays at zero. Of course the file is actually moved. But, both progress bars never advance and they always show 0%.Any idea what could be causing this? because it is not isolated to just one system for me.SAre you using ay mover tuner plugin?
Saturday at 11:05 AM4 days On 11/12/2026 at 2:06 AM, warpspeed said:The temporary plugin here seems to fix the lscr docker issue:GitHubfix(docker): use resolved manifest URL for update checks...With recent unraid updates, docker update checks for lscr.io images showed up as "not available". This seems due to lscr.io redirecting to ghcr.io and this caused part of the authorizatio...Looks like this was merged into main yesterday, yay. Just gotta do it this way until the point release I suppose.
Saturday at 12:08 PM4 days 59 minutes ago, Moniker_30 said:Looks like this was merged into main yesterday, yay. Just gotta do it this way until the point release I suppose.I just changed my repo in the Docker from e.g. lscr.io/linuxserver/swag to linuxserver/swag(forgive me if I have the preceding URL incorrect - I can't remember what it was)Turns out 2/3 of my LinuxServer containers I was running were already missing the initial URL, anyway.So no need to wait for the fix to make it to main, nor apply the patch.
Saturday at 02:14 PM4 days Subject: Unraid 7.4.0 — qBittorrent Docker fails to start after update due to network conflictFollowing my update to Unraid 7.4.0, my previously working qBittorrent Docker container would no longer start.Original configuration:Network Type: BridgeExtra Parameters: --net=container:GluetunVPNVPN: GluetunVPN using PIA/OpenVPNDocker error:failed to set up container networking: container sharing network namespace with another container or host cannot be connected to any other networkfailed to start containers: qbittorrentResolution:Changing Network Type from Bridge to None, while retaining --net=container:GluetunVPN, immediately resolved the issue.qBittorrent now starts successfully and remains bound to the VPN interface (tun0).The original configuration worked before updating to 7.4.0.Could you confirm whether this is an intentional change in Unraid 7.4.0 and whether None is now the recommended Network Type when sharing another container's network namespace?Thank you.
Saturday at 03:14 PM4 days 11 hours ago, Frank1940 said:I have seen other posts about this problem. Apparently, the progress bar does not moved until the first file is completely transferred. (You seem to indicate that you are only moving one file. In that case, if the proceeding is true, you would never see the bar move!)Yes. Every test was only one file. I used one 60GB test file each time. Let me try it with some multiple, small, 25GB files. Thanks. Edited Saturday at 03:19 PM4 days by aaronwt
Saturday at 03:16 PM4 days 7 hours ago, SimonF said:SAre you using ay mover tuner plugin?I'll need to check. I'm not sure offhand.
Saturday at 04:08 PM4 days I see now. I found a folder with a several hundred pictures on it and transfered the folder to several unRAID setups. I saw the progress bars working there when I manually initiated the mover.I was thinking that it would actually keep track of the progress during the file move. But, it only keeps tracks of progress based on when the file has finished moving. Most of my mover activity are file sizes between 60GB and 100GB. So, for me, I'm more curious how long each individual file will take to move. But, at least, I understand what it is doing now. And why my progress bar was only at 0% for one file move. Edited Saturday at 04:10 PM4 days by aaronwt
Sunday at 12:03 AM3 days Thank you for another uneventful upgrade. Update from 7.3.4 with no issue. Keep up the great work!
Sunday at 09:01 AM3 days 18 hours ago, Panapat said:Could you confirm whether this is an intentional change in Unraid 7.4.0 and whether None is now the recommended Network Type when sharing another container's network namespace?Unraid 7.4.0 includes a newer Docker engine, which is the most likely reason this now prevents the container from starting.The recommended setup is to use the built-in option instead of the extra parameter:1. Edit the qBittorrent container.2. Set Network Type to Container.3. In Container Network, select GluetunVPN.4. Remove --net=container:GluetunVPN from Extra Parameters.5. Click Apply.This gives the same result as your current setup, without needing the extra parameter. Your current setup (None plus the extra parameter) should also keep working.
3 hours ago3 hr Just updated, still testing, but everything seems normal. What's weird is that I didn't get the docker not available issue.
1 hour ago1 hr 1 hour ago, Reda.Saiko said:Just updated, still testing, but everything seems normal. What's weird is that I didn't get the docker not available issue.if one of your containers uses lscr.io and updates are working, then it's perhaps still somewhere in cache.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.