I would greatly appreciate it if @SpaceInvaderOne or someone else could create a new tutorial explaining how to migrate from our older versions to a working setup that is compatible with the latest release.

Thank you very much in advance.

• x86_64 / amd64 processor. ARM is not supported.

• 4 GB RAM minimum.

• Docker is enabled in Unraid.

• Roon Remote devices on the same local network as the Unraid server.

  I would like to setup a Roon Server with minimal cost. I have several 3.5" HDD NAS 22TB drives by WD Red Pro and Seagate.

  So which enclosure? I also have two m.2.NVME2280 2Tb storage.

I'm currently working through a problem with my unRAID server. It started with a drive that had read errors. I ordered and installed a replacement drive, but had to shut down the system to do it as my system is not hot-swappable. When It came back up, the array status went good, but Drive 1 was not mountable. So, I went through the process of checking and fixing the file system (deleting dirty log). After this, the array came up properly, and I was able to access shares via SMB. However, while my Docker container (Pritunl) was visible, it wouldn't start. So, I tried restoring both the template (xml) and container (tar.gz) through Community Applications appdata backup. However, while the logs indicate success, Pritunl still won't start.

I tried restoring from multiple backups to see if that made any difference, but there was no difference. Any assistance would be very much appreciated.

Diagnostics attached.

Thanks,
Shaun

gisl-cr1-ur1-diagnostics-20260719-1523.zip

is it plenned to get native compose support? What I mean is there is nor not a good way to run multiple container stacks.

For example paperless with redix, it will kill itself on updating all the time since it has a dependency and redis needs to run first.

Right now I basically have to give up on container management through UI alltogether and move it into a VM. Also native VLAN assignment via Web GUI would be interesting and maybe native traefik support for SNI routing vs. using ports.

Is there something on the roudmap maybe?

docker: Error response from daemon: failed to set up container networking: Address already in use

When I change the IP it boots just fine and has no issues but for some reason I cant allocate it the same IP its had for years now,

I have tried,

• Turning off Docker and turning it On

• All other containers are stopped and nothing is using that IP

• No ping response from the network showing if something else has taken the IP within the network

• docker network inspect -v br0.101 shows nothing else is using the IP's running

The container has been working fine until a recent reboot to update my server and now just this one container wont start on the custom port. All other dockers appear to be working fine,

When I change it to another random IP it comes online however I have alot of things mapped to this IP so I would rather fix the issue than just change the port as something is taking this port or blocking docker from starting using this IP. Is there a way to force it to start knowing the IP is available?

Edit more testing

So did some testing and it seems no docker wants to use the address which I have allocated to Pihole on the network, so something is blocking any container using the specific IP. What would be blocking one specific IP from being used?

I unfortunately cannot start (some) containers anymore. When I go to the docker tab, click on the container image -> start, I just get "Execution error \n Error code 403" (btw: pretty useless. Please add more information here!).

When editing the config, I at least get some more information. I noticed when trying to install the "vorta" community application.

This is what I get:

$ docker run
-d
--name='vorta'
--net='bridge'
--pids-limit 2048
-e TZ="Europe/Berlin"
-e HOST_OS="Unraid"
-e HOST_HOSTNAME="..."
-e HOST_CONTAINERNAME="vorta"
-e 'VNC_PASSWORD'='...'
-e 'APP_NAME'='Vorta'
-e 'TZ'='...'
-e 'SECURE_CONNECTION'='...'
-e 'USER_ID'='...'
-e 'GROUP_ID'='...'
-e 'UMASK'='...'
-e 'DISPLAY_WIDTH'='1280'
-e 'DISPLAY_HEIGHT'='768'
-l net.unraid.docker.managed=dockerman
-l net.unraid.docker.webui='http://[IP]:[PORT:5800]'
-l net.unraid.docker.icon=''
-p '5811:5800/tcp'
-v '/mnt/user/':'/unraid/data':'ro'
-v '/mnt/user/':'/restore/':'rw'
-v '/mnt/user/appdata/vorta':'/config':'rw'
--hostname=unraid-vorta 'ghcr.io/borgbase/vorta-docker'
a5c72fab104a1c0bbb9271407d286916f79c88a4a1c786d392eb8dd215fbcfd6
docker: Error response from daemon: Address already in use.

The port 5811 shows up nowhere on the docker tab. Using sudo netstat -tulpn | grep 5811 in the terminal gives no result. That port is free.

Of course I tried using different ports, but it always is the same result. None works.

I tried pruning imagaes, old containers, networks, ... - no result.

Restarting did not help either.

Array and Cache have free memory, docker vdisk too.

The same error happens for StirlingPDF, too. I haven't used it for a while, so I can't say since when this happens.

Immich (managed by docker compose), pihole and another container interestingly work fine.

The system is running Unraid 7.2.3

What could be the problem?

Thanks in advance for help!

I have an image in private GitHub repo?

How can I add this repo in Unraid and create new container from private image?

Snippet-

Jul 8 19:41:21 BrunnhildeTwo nginx: 2026/07/08 19:41:21 [error] 14550#14550: *9 open() "/usr/local/emhttp/state/plugins/dynamix.docker.manager/images/binhex-prowlarr-icon.png" failed (2: No such file or directory) while sending to client, client: 10.0.1.151, server: 10-0-1-20.0f613bbcc2f814341fd47af475a59915536d584d.myunraid.net, request: "GET /state/plugins/dynamix.docker.manager/images/binhex-prowlarr-icon.png?1781878726 HTTP/2.0", host: "10-0-1-20.0f613bbcc2f814341fd47af475a59915536d584d.myunraid.net", referrer: "https://10-0-1-20.0f613bbcc2f814341fd47af475a59915536d584d.myunraid.net/Docker"

Jul 8 19:41:21 BrunnhildeTwo nginx: 2026/07/08 19:41:21 [error] 14550#14550: *9 open() "/usr/local/emhttp/state/plugins/dynamix.docker.manager/images/unpackerr-icon.png" failed (2: No such file or directory) while sending to client, client: 10.0.1.151, server: 10-0-1-20.0f613bbcc2f814341fd47af475a59915536d584d.myunraid.net, request: "GET /state/plugins/dynamix.docker.manager/images/unpackerr-icon.png?1781878726 HTTP/2.0", host: "10-0-1-20.0f613bbcc2f814341fd47af475a59915536d584d.myunraid.net", referrer: "https://10-0-1-20.0f613bbcc2f814341fd47af475a59915536d584d.myunraid.net/Docker"

Jul 8 19:41:21 BrunnhildeTwo nginx: 2026/07/08 19:41:21 [error] 14550#14550: *9 open() "/usr/local/emhttp/state/plugins/dynamix.docker.manager/images/PlexMediaServer-icon.png" failed (2: No such file or directory) while sending to client, client: 10.0.1.151, server: 10-0-1-20.0f613bbcc2f814341fd47af475a59915536d584d.myunraid.net, request: "GET /state/plugins/dynamix.docker.manager/images/PlexMediaServer-icon.png?1781878726 HTTP/2.0", host: "10-0-1-20.0f613bbcc2f814341fd47af475a59915536d584d.myunraid.net", referrer: "https://10-0-1-20.0f613bbcc2f814341fd47af475a59915536d584d.myunraid.net/Docker"

Currently running 7.3.2 but this may have started before the update.

brunnhildetwo-diagnostics-20260708-2001.zip

Registry/image names:

192.168.0.55:3001/vessosa/my-api:latest

192.168.0.55:3001/vessosa/my-web:latest

What works:

• docker login 192.168.0.55:3001 works

• docker pull 192.168.0.55:3001/vessosa/my-api:latest works

• docker pull 192.168.0.55:3001/vessosa/my-web:latest works

• containers run correctly after manual pull/recreate

• the registry is a self-hosted Gitea registry using standard Docker/OCI image support

What does not work:

• Unraid Docker UI shows "not available" for the version/update status

• Unraid does not reliably detect whether the local container is up to date

• Force Update does not behave like a normal registry update check unless the image was already manually pulled from

CLI

Expected behavior:

Unraid should support private OCI registries using host:port image references and compare the running container image digest/ID against the remote tag digest. It should show "up-to-date" or "update available" instead of "not available".

Possible cause:

The image reference contains two ":" characters:

192.168.0.55:3001/vessosa/my-api:latest

The first ":" is the registry port.

The final ":" is the image tag separator.

It looks similar to this older report:

https://forums.unraid.net/bug-reports/stable-releases/61210-cant-update-docker-container-with-port-in-url-r2585/

That report appears archived/locked, so I am opening a new one with a current reproduction using Gitea.

diagnostics-20260710-1523.7z

I'm experiencing a persistent issue where my Docker tab in the Unraid GUI hangs indefinitely on "Please wait..." and any attempt to pull a new image results in a "context deadline exceeded" or "request canceled while waiting for connection" error.

What happened: The issue started after a crash of a VPN container (Gluetun/Netbird). Since then, the Docker service seems to be in a deadlock.

Symptoms:

• The Docker UI tab never finishes loading.

• Pulling images consistently fails with timeouts.

• nslookup inside the terminal shows timeouts for standard lookups, seemingly attempting to route through a leftover Tailscale/VPN interface (100.100.100.100).

• I have already tried restarting the Docker service and pruning networks, but the issue persists after reboots.

• The docker.img has not been deleted to preserve data.

What I have tried:

• Verified network DNS settings (1.1.1.1/8.8.8.8) in the GUI, but the system still seems to attempt routing via the old VPN/Tailscale interface.

• Checked iptables and network interfaces, but unable to clear the deadlock.

• The logs show that the Docker daemon is struggling to connect to registry-1.docker.io.

I have attached my diagnostics file to this post. Could you please help me identify which zombie process or network interface is blocking the Docker daemon?

I want to avoid deleting the docker image/rebuilding everything if possible.

Thank you for your help!

asunastower-diagnostics-20260709-1325.zip

I just discovered that 1password has 2 containers in the Unraid App Store, and that got me thinking:

Is it possible to retrieve secrets from a 1password vault directly into the creation of docker containers via the Docker Web GUI?

I'm thinking of the ability to fill out environment variables with a secret name from the 1password vault instead of the API key (example) directly.

That would have been SO nice.

Let's face it; having all those API keys etc exposed when creating a multitude of containers isn't the best security

I have a template I did for redis which I did like all my other template (create on my system, click save, copy/paste and remove extra stuff like date installed).

In the template, I have 2 path but weirdly, when I installed from the CA, the second path is truncated:

XML:

CA New installation (ran from another server that never installed it):

XML: unraid_template/nodiaque/redis.xml at master · nodiaque/unraid_template

Can someone help me understand why? I've checked under invalid template and template error and all I find is

Duplicated Template: Nodiaque's Repository - redis - redis

But I only have 1 xml for redis so I don't understand.

Thank you

Now however, I need one of these containers (let's call this Source Container) to communicate with a Docker container hosted on another machine on my LAN (a Windows machine running the service in a Docker container using WSL 2).

From my research I am thinking that this might be possible adding my Source Container to a macvlan network to expose it to my LAN, but still keep it on the custom network to allow communication between the other containers on that custom network.

However, I have no idea how to actually implement it, and also don't really know if this is even the correct approach to solve this.

Specifically what I am trying to do is an Unraid container to access my Windows hosted container to get access to the Windows machines GPU.

For some time now I am experiencing a weird behavior with my containers. I'm running on 7.3.1 but the problem existet also on 7.3.0 or even before. And I'm using FolderView3.

The Problem: I have now experienced lots of containers disapearing and some times reapearing again. Most of the time after a reboot I get missing containers and some orphaned ones. Also some times after a "bulk"-Update in Folderview3 (Update all) I get orphaned images afterwards.

Notice in the sreenshot that it shows 4/6 started, but it shows only 4. The missing ones will probably be Immich-redis and the second one I'm not to shure right now which one it should be.

Also notice the docker folder showing 3/5 started, but only 3 container showed. One of the missing ones will be this one:

And there are more orphans by the way:

Whai I wxperience now for the first time is that the first 2 of them don't even show the name anymore, so I have no idea which ones are missing.

I can now delete the orphans and reinstall them, but I allways get an error:

docker: Error response from daemon: Conflict. The container name "/PortainerCE" is already in use by container "5d1124ae90bacea5f5725436caa80045b1e40cb755179f1ead0639029dfde56c". You have to remove (or rename) that container to be able to reuse that name.

Run 'docker run --help' for more information

The command failed.

I can now rename and install it as PortainerCE1, but then it is not in the correct Folder anymore and so on...

And sometimes a "lost" Container magicly reapears again after a restart, so it hapened with Luckybackup, of which I duddenly had 2, Luckibackup and Luckibackup1 (but normally I get more orphans after a reboot).

Any idea what is going wrong and how I can solve it? That is getting a little annoying...

unraid-diagnostics-20260623-2143.zip

Please be aware that errors concerning Ip-Adresses (especially 192.168.1.x and 10.10.10.x ) have to do with the fact that I had to change from the 192. -net to the 10. -net. last week/weekend, so ther may still be problems there I have to figure out, but the here decribed problems existed way before but have become more apparently because I had to restart the Unraid server a few times. Btw, for me no signs of an unclean shutdown or reboot so far...

Thank you

I have a lot of docker containers, and it's not easy to determine what network ports are available. I also use docker compose for some, and it doesn't have a "docker allocations" option.

The ol' Elgoogs said to spin up a home assistant docker, and to use the unraid and unifi addons. Before I do something as complicated as that, I wanted to see if anyone else have a similar situation and they use something that's more built into unraid.

Thank you in advance!

PS: Also can anyone recommend an e-sim provider that's not $80/year for 10GB of backup internet? Lol.

 <?xml version="1.0"?>
<Container version="2">
  <Name>MCPGateway</Name>
  <Repository>ghcr.io/wildfirebill-unraid/mcp-gateway-unraid:20260620</Repository>
  <Registry>ghcr.io/wildfirebill-unraid/mcp-gateway-unraid:latest</Registry>
  <Network>wildfire</Network>
  <MyIP>172.18.255.80</MyIP>
  <Privileged>false</Privileged>
  <Support>https://github.com/wildfirebill-unraid/mcp-gateway-unraid/issues</Support>
  <Project>https://github.com/wildfirebill-unraid/mcp-gateway-unraid</Project>
  <Overview>
    The MCP Gateway allows AI agents (Claude Desktop, VS Code, Cursor, etc.)
    to access MCP tools running in Docker containers. All communication stays
    within your local network — no data leaves your LAN.
    Features:
    • Run MCP servers as isolated Docker containers
    • Single endpoint for multiple MCP tools
    • Secrets management via .env files
    • No internet required once configured
    • Works with Claude Desktop, VS Code, Cursor, and any MCP client
  </Overview>
  <Category>Tools:Utilities</Category>
  <TemplateURL>https://github.com/wildfirebill-unraid/mcp-gateway-unraid/blob/577cb331eca8ca3e828da051bc9066271fbdf11b/unraid/mcp-gateway-unraid.xml</TemplateURL>
  <Icon>https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons@main/png/docker.png</Icon>
  <Platform>linux</Platform>
  <Support>https://github.com/docker/mcp-gateway/issues</Support>
  <Config Name="App Port" Target="8811" Default="8811" Mode="tcp" Description="Port the gateway listens on for MCP connections" Type="Port" Display="always" Required="false" Mask="false">59778</Config>
  <Config Name="Transport" Target="GATEWAY_TRANSPORT" Default="streaming" Mode="tcp" Description="Transport protocol: stdio, sse, or streaming (streaming recommended for LAN use)" Type="Variable" Display="always" Required="false" Mask="false">streaming</Config>
  <Config Name="Auth Token" Target="MCP_GATEWAY_AUTH_TOKEN" Default="" Mode="tcp" Description="Bearer token for MCP endpoint authentication. Clients must send this as Authorization: Bearer <token>. If empty, a random token is generated on each container restart." Type="Variable" Display="always" Required="false" Mask="true">redacted</Config>
  <Config Name="MCP Servers" Target="GATEWAY_SERVERS" Default="fetch,duckduckgo" Mode="tcp" Description="Comma-separated list of MCP servers to enable. Options: fetch, duckduckgo, filesystem, github-official, postgres, slack, etc." Type="Variable" Display="always" Required="false" Mask="false">fetch,duckduckgo</Config>
  <Config Name="Memory Limit" Target="GATEWAY_MEMORY" Default="2Gb" Mode="tcp" Description="Memory limit per MCP server container (e.g. 512Mb, 1Gb, 2Gb)" Type="Variable" Display="always" Required="false" Mask="false">2Gb</Config>
  <Config Name="CPU Limit" Target="GATEWAY_CPUS" Default="1" Mode="tcp" Description="CPU cores per MCP server container" Type="Variable" Display="always" Required="false" Mask="false">1</Config>
  <Config Name="Log Calls" Target="GATEWAY_LOG_CALLS" Default="true" Mode="tcp" Description="Enable logging of MCP tool calls" Type="Variable" Display="always" Required="false" Mask="false">true</Config>
  <Config Name="Verify Signatures" Target="GATEWAY_VERIFY_SIGNATURES" Default="false" Mode="tcp" Description="Verify Docker MCP image signatures. Disable for local/private servers." Type="Variable" Display="always" Required="false" Mask="false">false</Config>
  <Config Name="Docker Socket" Target="/var/run/docker.sock" Default="/var/run/docker.sock" Mode="rw" Description="Docker socket - required for gateway to launch MCP server containers" Type="Path" Display="always" Required="true" Mask="false">/var/run/docker.sock</Config>
  <Config Name="Config Directory" Target="/config" Default="/mnt/user/appdata/mcp-gateway/config" Mode="ro" Description="Mount a local MCP catalog config (optional)" Type="Path" Display="always" Required="false" Mask="false">/mnt/cache/appdata/ai/mcp-gateway/config</Config>
  <Config Name="Secrets Directory" Target="/secrets" Default="/mnt/user/appdata/mcp-gateway/secrets" Mode="ro" Description="Directory containing .env file with API keys/tokens (optional)" Type="Path" Display="always" Required="false" Mask="false">/mnt/cache/appdata/ai/mcp-gateway/secrets</Config>
  <Config Name="DOCKER_MCP_IN_CONTAINER" Target="DOCKER_MCP_IN_CONTAINER" Default="1" Mode="tcp" Description="Must be set to 1 to run outside Docker Desktop" Type="Variable" Display="always" Required="true" Mask="false">1</Config>
</Container>

I have attached logs, a screenshot of my containers and a screenshot of the update process.

tower-diagnostics-20260613-1945.zip

I have been having some issues recently with IPV6 on docker and it managing to break IPV6 on the VLAN.

I think I have managed to identify the issue with some AI help (who knew they can sometimes be helpful) but I wanted to check that this is the expected behaviour.

When I use SLAAC to give Unraid an IPV6 address it appears to configure a global address and then a link local address for the gateway. So far so good.

The issue appears because Docker IPAM then appears to allocate ::1 to the first container because no global IPV6 address has been defined within the subnet. The router then detects this and effective turns off IPV6 on the VLAN.

The only way to define the global IPV6 address for the gateway is to statically assign the IPV6 address for Unraid itself.

Im still a bit new to IPV6 networking but wanted to check if this is expected behaviour.

Im on the latest version of Unraid

Have mercy if I am doing something silly!

Thanks

https://docs.movary.org/

Is there someone who could assist me in creating a Docker container compatible with Unraid for this excellent project? I would greatly appreciate the help of someone experienced in this matter.

Thank you very much

I am also getting the following error when trying to reinstall apps from Hotio's repository "docker: Error response from daemon: pull access denied for hotio/autoscan, repository does not exist or may require 'docker login': denied: requested access to the resource is denied"

Here is an imgur album with the relevant info. https://imgur.com/a/630vRO7 I am not at all sure what to add in 'Download path' or 'Mapped path' in the RDT-client settings under download client. I am not sure how to set up remote path mapping with the settings I have. I did try to follow the trash guides and the github documentation for RDT-client but its not working as you can see. Thank you so much for any help!

In this specific case I tried to use the binhex-official-pihole container. I ran into several issues and posted on the PiHole forums. Apparently many of the variables are specified incorrectly, and others are out of date. I can't get help with this container there as it isn't supported on Unraid.

At that point I started looking here and there is no container support thread for this one. How is it in any way "official" if the dev team isn't supporting it, and neither is the Unraid team? Do I just pick a different release and move on?

Thanks!

Mike

I’m trying to diagnose a strange Plex performance issue on my Unraid server and would appreciate any ideas. I apologise in advance if this is not the right place for this post I wasnt sure where it fits because the issue is still unclear to me

System:

• Unraid kernel: Linux 6.12.24-Unraid x86_64

• Motherboard: Supermicro X10DRi-T4+

• CPU: Dual Intel Xeon E5-2699 v4

• RAM: 128 GB DDR4 ECC

• GPU: Intel Arc A380

• Plex container appdata: 2 TB WD m.2 NVME cache drive, fs BTRFS

• Media storage: ~340 TB Unraid array

• Plex running in Docker on Unraid
  

The issue:

Plex browsing is extremely slow. Posters, metadata, home screen rows, and library sections take a long time to load. However, once I click play, playback is perfect. Direct play and transcoding both work without buffering.

So the problem is not playback performance. It seems specifically related to metadata/library loading.
Here is an example of what I mean
https://imgur.com/a/rREBqrn

What I tested:

1. Existing Plex Docker on Unraid (at first i had thought it was a database/plex config error) I've deleted plex appdata and started everything from scratch - made no difference

   • Slow browsing/loading metadata

2. Fresh Plex Docker install on Unraid, same libraries. Tried different repos as well - binhex, official (plexinc/pms-docker), lscr.io/linuxserver/plex

   • Same slow browsing issue
     

3. Plex Media Server installed on my Windows admin PC, accessing the same Unraid media over SMB. That fixed it. Browsing was instant when the server ran on my pc. At first I though it might be that my pc has better hardware for plex. but then..
   

4. Windows 10 VM running inside the same Unraid server, Plex installed inside the VM, accessing the same Unraid media over SMB Browsing/loading is also instant!! It seems like running it on windows fixed it regardless of the hardware
   here is an example of how the virtual machine performed
   https://imgur.com/a/Zo4ovBi
   

This is what confuses me most. Plex inside a Windows VM on the same Unraid machine performs instantly, but Plex Docker on Unraid is slow.

My suspicion (as a super noob):

I’m wondering if this is related to:

• Plex appdata being on BTRFS?

• BTRFS CoW/write amplification with Plex metadata/database/cache (This is what chatgpt suggested)

I’m considering moving Plex appdata to an XFS or EXT4 SSD pool, or disabling CoW on the Plex appdata directory and rewriting the files.

Questions:

Any advice on what to test next would be appreciated

Or does that only affects the "Docker directory" (by default /mnt/user/system/docker/), Docker.img, whatnot.

Thanks!

after spending way to long to get the DB Connection for dawarich to work, I am now running into an error I can not fix. After starting the dawarich docker the log shows the following:

bottom of the log:

OIDC: Not configured (missing OIDC_CLIENT_ID or OIDC_CLIENT_SECRET)

top of the log:

ArgumentError: Missing secret_key_base for 'production' environment, set this string with bin/rails credentials:edit (ArgumentError)

raise ArgumentError, "Missing secret_key_base for '#{Rails.env}' environment, set this string with bin/rails credentials:edit"

I have tried to google myself out of this but had no luck for 2h so far.

I added an extra variable to the docker config named secret_key_base based on this https://github.com/truenas/apps/pull/4705 but I have absolutely no idea what value I have to fill in. I tried leaving it empty, I tried <%= ENV["SECRET_KEY_BASE"] %> based of this site https://stackoverflow.com/questions/23180650/how-to-solve-error-missing-secret-key-base-for-production-environment-rai but nothing is working.

Can anyone help me with this?

tldr; 10 pulls an hour unauthenticated. Can we get fields on docker settings page to input authentication information?

Im trying to install SparkyFitness and wondering if anyone else got it to work?

I'm not very good with postgress on how to set it up.

BR/ Emil

I spent tonight debugging why my Gluetun VPN containers refused to start after an array restart with an IPv6 error, even though IPv6 was working perfectly an hour before. Turns out this is the same underlying bug that's been biting people for years across different Unraid versions, and I think the root cause deserves its own clear explanation because the existing threads dance around it without nailing it down.

The symptom

After any array restart (or reboot), IPv6 stops working. Containers that need IPv6 fail. VMs lose their IPv6 addresses or connectivity. Matter/Thread devices go offline. The host has no IPv6 default route even though your router is advertising one correctly.

The root cause, as simply as I can put it

When Docker starts, it enables IPv6 packet forwarding on the host:

net.ipv6.conf.all.forwarding = 1

This is a Linux kernel-level thing — Docker needs it so containers can route traffic. The problem is that the Linux kernel treats any host with forwarding=1 as a router, and routers don't listen to Router Advertisements from other routers. So the kernel silently stops accepting RAs on all interfaces, which means your IPv6 default route (learned from your gateway via RA) disappears and never comes back.

You can verify this yourself:

sysctl net.ipv6.conf.br0.accept_ra

If it shows 0, that's your problem.

Why it worked before the reboot

Timing. If Docker was already running when you first configured IPv6, the existing RA-learned route might have still been in the routing table. It just doesn't survive a restart because the startup sequence goes: network comes up → RA installs default route → Docker starts → forwarding=1 kills RA acceptance → route expires → never renewed.

Why Unraid's rc.docker doesn't catch this

rc.docker actually does check for an IPv6 default route before deciding whether to start Docker with --ipv6:

if [[ -n $(ip -6 route show to default dev $PORT) ]]; then
    DOCKER_OPTS="--ipv6 --fixed-cidr-v6=$DOCKER0 $DOCKER_OPTS"

But this creates a chicken-and-egg problem. The route exists when Docker starts, so Docker gets --ipv6. Then Docker enables forwarding, which kills the route. Next reboot, the route might not be there in time, so Docker starts without --ipv6, and now the Docker bridge network doesn't have IPv6 either.

How this cascades to Gluetun

If you run Gluetun (https://github.com/qdm12/gluetun) with dual-stack WireGuard (both IPv4 and IPv6 in WIREGUARD_ADDRESSES), this bites extra hard.

Gluetun checks IPv6 support at startup by looking at the routing table inside its container namespace. If the Docker network doesn't have IPv6 (because rc.docker didn't see a default route and skipped --ipv6), Gluetun finds no IPv6 routes and refuses to start:

ERROR VPN settings: Wireguard settings: interface address is IPv6 but IPv6 is not supported: address 2a07:b944::2:2/128

This is logged as "IPv6 is not supported after searching N routes" — it's not a Gluetun bug, it's just reporting what it sees.

Any container using Gluetun's network namespace (qbittorrent, prowlarr, etc.) then also fails to start because the network namespace doesn't exist.

Related Gluetun issues:

- #1597 — interface address is IPv6 but IPv6 is not supported (https://github.com/qdm12/gluetun/issues/1597) (May 2023)

- #2713 — IPv6 suddenly no longer working (https://github.com/qdm12/gluetun/issues/2713) (Feb 2025)

The fix

One line in /boot/config/go:

sysctl -w net.ipv6.conf.br0.accept_ra=2

accept_ra=2 means "accept Router Advertisements even when forwarding is enabled."

This is the standard Linux fix for any host that needs to both forward packets and receive RAs — which is exactly what an Unraid box running Docker is.

This is a known upstream Docker bug

This was reported to Docker in March 2022: docker/for-linux#1373 (https://github.com/docker/for-linux/issues/1373) — "Docker sets forward=1 but not accept_ra=2 when enabling IPv6." Still not fixed as of today.

Unraid threads about the same underlying issue

- IPv6 RA inside UnRAID VM not accepted (https://forums.unraid.net/topic/138717-ipv6-ra-inside-unraid-vm-not-accepted/) (May 2023, Unraid 6.11.5)

- Docker IPv6 issues on 7.0.1 (https://forums.unraid.net/topic/188533-docker-ipv6-issues-on-701/) (June 2025)

- The state of ipv6 in unRaid's docker (https://forums.unraid.net/topic/193868-the-state-of-ipv6-in-unraids-docker/) (October 2025)

- [7.2.0] ipv6 networking to VMs no longer functional (https://forums.unraid.net/bug-reports/stable-releases/720-ipv6-networking-to-vms-no-longer-functional-r4136/) (2026)

The 7.2.1 fix ("load br_netfilter and set IPv6 FORWARD policy to ACCEPT") addresses the ip6tables side of things, but not the RA acceptance problem. They're related but separate issues.

Suggestion for LimeTech

Could rc.docker add sysctl -w net.ipv6.conf.$PORT.accept_ra=2 right after enabling IPv6 forwarding? That would fix this for everyone without needing manual go file edits. It's a one-liner and it's what every other Docker-on-Linux guide recommends.

Running Unraid 7.2.5 / OPNsense gateway with SLAAC / Gluetun WireGuard dual-stack.

I have been trying to get ownCloud working for a few weeks now. I tried the one from the appstore. I was able to get it to work with the exception of being able to put it behind traefik. Nothing I did would make it work.

So, I redid it manually using the owncloud repo. Everything seems to work great. I can login to the webui. I can sync using the client. But, anytime I try to add another client it seems to kill the container. There are no messages in the logs, but it stops responding, both the webui and the clients.

When it stops responding I am unable to stop, kill, restart, or delete the container. At this point all other containers and the unRAID webui work fine. If I try to add the client a second or third time all containers stop responding and so does unRAID. I can login using SSH, but no commands seem to work. If I try to reboot it gives the message that it is rebooting but never does. My only option at this time is to power off and then power back on. If I don't start the ownCloud container it will work for days with no issues. If I start the ownCLoud container and don't try to add any clients it seems to stay running as well.

my-ownCloud.xml

When running Emby in a docker container it sometimes shoots up in memory usage, i've seen it take over 10GB+ memory at some point.

Looking into it, with the help of the Emby developers, Emby it self only seems to use around 1.5GB in total while Unraid reports much more.

Looking up difference monitoring programs i get different kinds of results.

Some report what Emby does, others what Unraid does.

My question:

Does Unraid include cache, disk cache and so on in the memory usage for docker containers?

That would explain pretty much everything if it does.

Finished loading

Anyone know of any way to customize the name and icon of servers installed via Pterodactyl?

For example, this is Minecraft:

'

Clicking the icon shows only Start, Logs, and Remove.

Thank you!

This may have already been answered and if so I would be really grateful if you can point me in the right direction

I am currently running the below

UNRaid Version: 6.12.6

I have several Dockers.

I am looking to make a new UNRaid on version 7.30

I want to move all the dockers to the new server but I can't seem to find any simple instructions.

From what I have read I can create a new UNRaid install the dockers then I need to stop them on both servers then I need to copy some folders from old to new but I'm not sure which folders would need copying.

If anyone has already done this it would be amazing to get some advice.

Thanks very much for any and all help

J

PS if this is in the wrong area please tell me where to move it.

If no volume is specified, where does Docker store the files in that container?

The iGPU that I am trying to pass through to plex for hardware transcoding is the one within the Intel i3 N305.

I have tried the plugins for Intel GPU Top, SR-IOV, GPU statistics. I've tried adding "/dev/dri" to the Plex container for the igpu. I've tried adding "device /dev/dri" as additional resources. I've tried adding xe.conf with xe force_probe=46d9 with and without i915.conf having i915 force_probe=46d9 and with !46d9 instead. With and without the "blacklist i915" line.

The most I've ever seen from the dashboard gpu information was with xe.conf "xe force_probe=46d9" and i915.conf with "i915 force_probe=!46d9". This then shows the widget receiving at least some data as the voltage is fluctuating at 0.1v where as without the xe force probe and with blachlist and then force_probe=46d9 in i915.conf everything is 0.

In all of these different configs, I never see the checkbox for enabling hardware transcoding. Looking at the log for the Plex docker container... there is "Critical: libusb_init failed" but I think that is for trying to connect to the tvtuner and not a high priority as I haven't purchased a plex pass yet. I also don't want to go about buying a plex pass if hardware transcoding isn't going to work. Same goes for Unraid, which is currently in trial status. I came from terra-master's OS which has its own issues, but transcoding was functional there.

In Plex's logs, downloaded from the app's webui, the only thing I'm immediately seeing relating to the gpu is the following:

May 11, 2026 19:48:03.915 [22388067126072] INFO - Preemptively preparing driver imd for GPU Intel Alder Lake-N [UHD Graphics]

May 11, 2026 19:48:03.915 [22388067126072] DEBUG - [DriverDL/imd] Skipping download; already exists

May 11, 2026 19:48:03.915 [22388067126072] INFO - Preemptively preparing driver icr for GPU Intel Alder Lake-N [UHD Graphics]

May 11, 2026 19:48:03.915 [22388067126072] DEBUG - [DriverDL/icr] Skipping download; already exists

May 11, 2026 19:48:03.915 [22388067126072] INFO - Preemptively preparing driver imd for GPU Intel Alder Lake-N [UHD Graphics]

May 11, 2026 19:48:03.915 [22388067126072] DEBUG - [DriverDL/imd] Skipping download; already exists

May 11, 2026 19:48:03.915 [22388067126072] INFO - Preemptively preparing driver icr for GPU Intel Alder Lake-N [UHD Graphics]

May 11, 2026 19:48:03.915 [22388067126072] DEBUG - [DriverDL/icr] Skipping download; already exists

May 11, 2026 19:48:03.915 [22388067126072] INFO - Preemptively preparing driver imd for GPU Intel Alder Lake-N [UHD Graphics]

May 11, 2026 19:48:03.915 [22388067126072] DEBUG - [DriverDL/imd] Skipping download; already exists

May 11, 2026 19:48:03.915 [22388067126072] INFO - Preemptively preparing driver icr for GPU Intel Alder Lake-N [UHD Graphics]

May 11, 2026 19:48:03.915 [22388067126072] DEBUG - [DriverDL/icr] Skipping download; already exists

...which makes me think that Plex is seeing it, maybe??

What can I provide to help determine a solution for this?

Thanks in advance!

Ollama has been updated. my app under docker shows update available.

I click update, it does not update. Same version. I can try various ways, force update, it goes through the motions, but does not update.

I have to delete the old docker and reinstall, then its updated.

Is this a known issue?

How can we get it to just update to latest version?

Help is appreciated!!

Thanks

I am having a very odd issue, when I try to run the update of a docker container, it runs successfully but pulls 0 bytes, so the container never updated. 

I have provided a screenshot of the logs. Any suggestions on what I should do next? 

I would like to install Authentik (Ibracorp) from CA. If I am not mistaken I would require both the Server and the Worker. My question is: Would I have to install an instance of PostgreSql and Redis beforehand?

I already have two instances of PostgreSQL running. Versions 16 for Paperless-NGX and version 17 at the moment I am not certain what that is being used for. And an instance of Redis running as well.

Should I create new instances of PostgreSQL and Redis for my new Authentik install? Your time and assistance will be greatly appreciated. Peter

I came across SpaceInvader video https://www.youtube.com/watch?v=yBF9c0u2wCE "
Route Containers Through WireGuard – Advanced Docker Networking" which seemed perfect for avoiding some headaches of dockers with vpn support. I happen to use PIA just like him so I followed all his steps and I see the VPN connection is established. However, when I configure my docker to use my new vpn interface from the docker perspective everything works. However, I am no longer able to connect to the docker webui on my desktop.

Via Unraid command line, I can run curl to the webui ip and port which is the server's ip and the docker port 8080. But on my non unraid machine I can't access that webui. As soon as I switch the docker back to the bridge connection everything works again. Based on the VPN interface I can see traffic is being sent and received by the docker when its using the VPN interface.

I'm curious if anyone seen this issue and have any potential solutions. I spent about an our with ChatGPT and couldn't get the problem fixed.

I'm currently running Unraid 7.2.5 and the docker I'm testing this with is a new installation of linuxserver/qbittorrent. As a sanity check I tried this with handbrake to see if I could access the webui and that failed as well.