Ed from the Uncast show explains this well here:

Edited May 19May 19 by peterg23

I updated from 7.2.5 to 7.3.0, and now almost all my Docker containers are gone. Why would you release a beta version as a stable release? I am absolutely furious.

3 minutes ago, Gaertner said:

I updated from 7.2.5 to 7.3.0, and now almost all my Docker containers are gone. Why would you release a beta version as a stable release? I am absolutely furious.

Where is your diagnostics file and a detailed list of containers that are missing. These are all things that will be needed before your problems can be solved. It would also be better if you were to open a thread in the General Support forum as your problem may take several responses to address.

6 minutes ago, Frank1940 said:

Where is your diagnostics file and a detailed list of containers that are missing. These are all things that will be needed before your problems can be solved. It would also be better if you were to open a thread in the General Support forum as your problem may take several responses to address.

That’s not necessary, as I know how to get everything up and running again. I just have to manually reinstall all the missing Docker containers using the existing template. I just wanted to mention that the update didn't go smoothly for everyone. I actually waited a few days before updating specifically to avoid any potential bugs.

There are other users with the same problems. https://www.reddit.com/r/unRAID/comments/1td5v2i/what_the_heck_happened_after_the_update_to_730/?tl=de

Update: I have restored the faulty containers. It wasn't exactly easy; I had to manually delete the broken containers via the console. After restarting Unraid, the other containers suddenly appeared broken—even though they had been fine just moments before. Consequently, I had to restore the remaining containers as well. The result: All Docker containers were broken following the update.

May 19 04:41:09 BlackBook rc.docker: Docker daemon...  Started.
May 19 04:41:09 BlackBook rc.docker: Starting network...
May 19 04:41:09 BlackBook kernel: Bridge firewalling registered
May 19 04:41:09 BlackBook root: Error response from daemon: RWLayer of container 5224cf2190caab06dc6c89b2e66e289db9995b98ba06daf622e846b5a2eabefb is unexpectedly nil
May 19 04:41:09 BlackBook root: Error response from daemon: RWLayer of container 945827b57775f5fb7b03bca0d00546c8c5d94c4fb3eb2ace0f3159c9bf821351 is unexpectedly nil
May 19 04:41:09 BlackBook root: Error response from daemon: RWLayer of container b51034e4bcbd22ad313a986ecd87055a1db67fc7cd417bba410defc8cc1ef6db is unexpectedly nil
May 19 04:41:09 BlackBook root: Error response from daemon: RWLayer of container da91db5689e801b033fcf9171ce6e0c09d1cac5e0228b0bcbf47fb55de30edc2 is unexpectedly nil
May 19 04:41:09 BlackBook root: Error response from daemon: RWLayer of container d61bc8c7f993e528bfebb9c238d37defb897c0318eeaabfbd7075a7ef2c9ca62 is unexpectedly nil
May 19 04:41:09 BlackBook root: Error response from daemon: RWLayer of container f91cf5921bfc56c3798701c7aab1295853fb56b6431f50d74b8987dc45713d9a is unexpectedly nil
May 19 04:41:10 BlackBook root: Error response from daemon: RWLayer of container 232b4976213788c52660080005e46c073298bd524db1f396dc638671b122bc6b is unexpectedly nil
May 19 04:41:10 BlackBook root: Error response from daemon: RWLayer of container 6837b27979037b099ae7830063657f957501111c95b4fdd05af40d920e78a57c is unexpectedly nil
May 19 04:41:10 BlackBook rc.docker: Processing... br0
May 19 04:41:10 BlackBook rc.docker: created network macvlan br0 with subnets: 192.168.178.0/24;

Edited May 19May 19 by Gaertner

On 5/15/2026 at 5:39 PM, ds9 said:

Thanks, so the issue is not limited to Private Browsing.
I guess that when using Firefox when the Web service is not fully started and we try to access the web interface, we have a cookie created that prevents access.
The weird cookie value I'm seeing is created by code in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout/HeadInlineJS.php

For a sucessful sesssion, the cookie has a different value format - such as 55b41aba704666854bd545ecf3791689

and the cookie is coming from Unraid correct?

5 hours ago, Gaertner said:

That’s not necessary, as I know how to get everything up and running again. I just have to manually reinstall all the missing Docker containers using the existing template. I just wanted to mention that the update didn't go smoothly for everyone. I actually waited a few days before updating specifically to avoid any potential bugs.

There are other users with the same problems. https://www.reddit.com/r/unRAID/comments/1td5v2i/what_the_heck_happened_after_the_update_to_730/?tl=de

Update: I have restored the faulty containers. It wasn't exactly easy; I had to manually delete the broken containers via the console. After restarting Unraid, the other containers suddenly appeared broken—even though they had been fine just moments before. Consequently, I had to restore the remaining containers as well. The result: All Docker containers were broken following the update.

May 19 04:41:09 BlackBook rc.docker: Docker daemon...  Started.
May 19 04:41:09 BlackBook rc.docker: Starting network...
May 19 04:41:09 BlackBook kernel: Bridge firewalling registered
May 19 04:41:09 BlackBook root: Error response from daemon: RWLayer of container 5224cf2190caab06dc6c89b2e66e289db9995b98ba06daf622e846b5a2eabefb is unexpectedly nil
May 19 04:41:09 BlackBook root: Error response from daemon: RWLayer of container 945827b57775f5fb7b03bca0d00546c8c5d94c4fb3eb2ace0f3159c9bf821351 is unexpectedly nil
May 19 04:41:09 BlackBook root: Error response from daemon: RWLayer of container b51034e4bcbd22ad313a986ecd87055a1db67fc7cd417bba410defc8cc1ef6db is unexpectedly nil
May 19 04:41:09 BlackBook root: Error response from daemon: RWLayer of container da91db5689e801b033fcf9171ce6e0c09d1cac5e0228b0bcbf47fb55de30edc2 is unexpectedly nil
May 19 04:41:09 BlackBook root: Error response from daemon: RWLayer of container d61bc8c7f993e528bfebb9c238d37defb897c0318eeaabfbd7075a7ef2c9ca62 is unexpectedly nil
May 19 04:41:09 BlackBook root: Error response from daemon: RWLayer of container f91cf5921bfc56c3798701c7aab1295853fb56b6431f50d74b8987dc45713d9a is unexpectedly nil
May 19 04:41:10 BlackBook root: Error response from daemon: RWLayer of container 232b4976213788c52660080005e46c073298bd524db1f396dc638671b122bc6b is unexpectedly nil
May 19 04:41:10 BlackBook root: Error response from daemon: RWLayer of container 6837b27979037b099ae7830063657f957501111c95b4fdd05af40d920e78a57c is unexpectedly nil
May 19 04:41:10 BlackBook rc.docker: Processing... br0
May 19 04:41:10 BlackBook rc.docker: created network macvlan br0 with subnets: 192.168.178.0/24;

yes i had this issue also, dockers disappeared and if you reboot different ones came and went.

all sorted now but i spent hours sorting out.

next issue is time machine no longer works

this has been the worst update for me.

That's quite annoying. I just find it strange that it seems to be a small group that has Docker problems. Many apparently had no problems after the update. If there are problems with Docker, e.g. because of a new version. Then a note should have been given that the containers might have to be recreated after the update to 7.3.0. Then you know that you have a bit of work to do afterwards and can plan accordingly.

That's why I always wait a few days until I update so that I don't get into a situation like this. But no one had reported Docker issues. I think that many are coming from 7.3.0 beta and possibly many are still on 7.2.6.

I would be interested to know what went wrong.

23 minutes ago, Gaertner said:

That's quite annoying. I just find it strange that it seems to be a small group that has Docker problems

23 minutes ago, Gaertner said:

I would be interested to know what went wrong.

Nothing went wrong. This is how software development works. There will always be small groups that have issues no one else has. There will always be small bugs, even in stable releases. The devs are not gods and do not possess or have the power to test releases on every hardware configuration out there.

29 minutes ago, Gaertner said:

That's why I always wait a few days until I update so that I don't get into a situation like this.

That is wise, but even then, you're not 100% safe. Life is not 100% safe, shit happens, always.. It's just a question of when.

1 hour ago, Gaertner said:

If there are problems with Docker, e.g. because of a new version. Then a note should have been given that the containers might have to be recreated after the update to 7.3.0. Then you know that you have a bit of work to do afterwards and can plan accordingly.

As mentioned what's expected is mentioned in release notes, but there will always be cases where something unexpected breaks. Price of self-hosting, you're the admin who has to deal with it instead of just paying for a service that takes care of it behind the scenes.

6 hours ago, strike said:

Nothing went wrong. This is how software development works. There will always be small groups that have issues no one else has. There will always be small bugs, even in stable releases. The devs are not gods and do not possess or have the power to test releases on every hardware configuration out there.

That is wise, but even then, you're not 100% safe. Life is not 100% safe, shit happens, always.. It's just a question of when.

That wasn't directed at the devs—in case you thought it was. What I meant was: what specific combination of circumstances leads to this error occurring?

I just want to understand it so that something like this doesn't happen again. However, I suspect that this error was just a one-off.

15 minutes ago, Gaertner said:

That wasn't directed at the devs—in case you thought it was

14 hours ago, Gaertner said:

Why would you release a beta version as a stable release?

With this comment you posted earlier, I was sure it was, yeah. But if it wasn't, then I apologize if you took my comment personally. I just can't stand these comments in most stable release threads, and I couldn't bite my tongue. What I've learned as an IT hobbyist over the years is that you should always consider software as beta. Stable is just a beta with bugs that no one has found yet. You may not get the opportunity to encounter them yourself, but trust me, if you look hard enough, they're there.

26 minutes ago, Gaertner said:

What I meant was: what specific combination of circumstances leads to this error occurring?

I just want to understand it so that something like this doesn't happen again. However, I suspect that this error was just a one-off.

Probably just a one-off, yeah. But if you want to dig deeper, you should post your own thread if you have the diagnostics from when it happened. If you don't, then it's anyone's guess.

Updated fine but somethings happened to homeassistant container. It's still there but not able to run it & won't let me re-add it.

How can I get it back working easily?

Screenshot is what happens if I click add container & choose homeassistant template.

Appdata folder is all still there...

7 minutes ago, dopeytree said:

Updated fine but somethings happened to homeassistant container. It's still there but not able to run it & won't let me re-add it.

How can I get it back working easily?

Screenshot is what happens if I click add container & choose homeassistant template.

Appdata folder is all still there...

Open Terminal --> docker rm -f homeassistant

Next, select "Add Container" — use the Home Assistant template.

On 5/18/2026 at 8:27 PM, JorgeB said:

You can get them from the CLI or over SSH.

UnRAID 7.3.0 doesn't like my "USB drive". I've been using a 2.5" USB enclosure and an SSD for years, 7.3.0 boots fine with the USB enclosure, but it doesn't load the GUI because it doesn't like the GUID of the USB enclosure... let's see if this happens to other people. (7.2.x does not have this problem with my 2.5" USB enclosure)

I copied the contents of the case to a USB flash drive and it boots perfectly. I'll have to transfer the license to new USB if I want to use 7.3.x. 😒

Because honestly, I'm not very interested in using the internal method; I don't like using a partition in the cache, and if I switch the USB from the enclosure to a SATA port, then I'll be left without a SATA port that I can use in the array.

EDIT: Once the license was transferred, I must say that version 7.3.0 of the moment works very well on my server:

Regards 🙂

Edited May 21May 21 by PoMpIs

The documentation says this kernel version is 6.18.28 but file shows it's 6.18.29:

bzimage: Linux kernel x86 boot executable bzImage, version 6.18.29-Unraid (root@Develop) #1 SMP PREEMPT_DYNAMIC Mon May 11 15:54:50 PDT 2026, RO-rootFS, swap_dev 0X8, Normal VGA

3 hours ago, bobbintb said:

The documentation says this kernel version is 6.18.28 but file shows it's 6.18.29:

bzimage: Linux kernel x86 boot executable bzImage, version 6.18.29-Unraid (root@Develop) #1 SMP PREEMPT_DYNAMIC Mon May 11 15:54:50 PDT 2026, RO-rootFS, swap_dev 0X8, Normal VGA

root@The-Borg:~# uname -r

6.18.29-Unraid

root@The-Borg:~#

must be a typo somewhere unraid 7.3 is using kernel 6.18.29

Hello,

no problems on my side upgrading Unraid from 7.2.5 to 7.3.0 (flash drive). The update process completed without any errors, all Docker container up and running, no errors in the Dashboard. I also had no errors during the onboarding after the first login. I was a little skeptical because of the negative experiences some users had

regards,

9 hours ago, bmartino1 said:

root@The-Borg:~# uname -r

6.18.29-Unraid

root@The-Borg:~#

must be a typo somewhere unraid 7.3 is using kernel 6.18.29

Seems so. I submitted a PR for the wiki page but @SpencerJ will have to change the post on the forum thread.

2 hours ago, bobbintb said:

Seems so. I submitted a PR for the wiki page but @SpencerJ will have to change the post on the forum thread.

thanks for the PR!

I've updated the original post here as well.

due to the recent https://forums.unraid.net/topic/198979-unraid-727-now-available
7.27 update can we get a confirmation that 7.3 has the updated binaries as well?

are the same cve updated in 7.3?

as repoprted in 7.2???

aaa_glibc-solibs: 2.42 → 2.43

• avahi: 0.8-3_SBo_LT → 20260508 (CVE-2023-38469, CVE-2023-38470, CVE-2023-38471, CVE-2023-38472, CVE-2023-38473)

• curl: 8.19.0 → 8.20.0 (CVE-2026-4873, CVE-2026-5545, CVE-2026-5773, CVE-2026-6253, CVE-2026-6276, CVE-2026-6429, CVE-2026-7009, CVE-2026-7168)

• docker: 29.3.1 → 29.5.1

• glibc: 2.42 → 2.43 (CVE-2025-15281, CVE-2026-0861, CVE-2026-0915)

• gnutls: 3.8.12 → 3.8.13 (CVE-2026-33846)

• jq: 1.6 → 1.8.1 (CVE-2024-53427, CVE-2025-9403)

• libvirt-php: 0.5.8-8.3.29 → 0.5.8-8.3.31

• nginx: 1.27.2 → 1.30.1 (CVE-2025-53859, CVE-2026-1642, CVE-2026-27651, CVE-2026-27654, CVE-2026-27784, CVE-2026-28753, CVE-2026-28755, CVE-2026-32647, CVE-2026-40460, CVE-2026-40701, CVE-2026-42934, CVE-2026-42945, CVE-2026-42946)

• php: 8.3.29 → 8.3.31 (CVE-2025-14179, CVE-2026-6722, CVE-2026-6735, CVE-2026-7258, CVE-2026-7259, CVE-2026-7261, CVE-2026-7262, CVE-2026-7568)

• zfs: 2.3.4_6.12.82_Unraid → 2.3.4_6.12.90_Unraid
  
  are you telling us to down grade then move to this for CVEs or is a 7.3.1 soon to be release???...

1 minute ago, bmartino1 said:

due to the recent https://forums.unraid.net/topic/198979-unraid-727-now-available
7.27 update can we get a confirmation that 7.3 has the updated binaries as well?

are the same cve updated in 7.3?

as repoprted in 7.2???

aaa_glibc-solibs: 2.42 → 2.43

• avahi: 0.8-3_SBo_LT → 20260508 (CVE-2023-38469, CVE-2023-38470, CVE-2023-38471, CVE-2023-38472, CVE-2023-38473)

• curl: 8.19.0 → 8.20.0 (CVE-2026-4873, CVE-2026-5545, CVE-2026-5773, CVE-2026-6253, CVE-2026-6276, CVE-2026-6429, CVE-2026-7009, CVE-2026-7168)

• docker: 29.3.1 → 29.5.1

• glibc: 2.42 → 2.43 (CVE-2025-15281, CVE-2026-0861, CVE-2026-0915)

• gnutls: 3.8.12 → 3.8.13 (CVE-2026-33846)

• jq: 1.6 → 1.8.1 (CVE-2024-53427, CVE-2025-9403)

• libvirt-php: 0.5.8-8.3.29 → 0.5.8-8.3.31

• nginx: 1.27.2 → 1.30.1 (CVE-2025-53859, CVE-2026-1642, CVE-2026-27651, CVE-2026-27654, CVE-2026-27784, CVE-2026-28753, CVE-2026-28755, CVE-2026-32647, CVE-2026-40460, CVE-2026-40701, CVE-2026-42934, CVE-2026-42945, CVE-2026-42946)

• php: 8.3.29 → 8.3.31 (CVE-2025-14179, CVE-2026-6722, CVE-2026-6735, CVE-2026-7258, CVE-2026-7259, CVE-2026-7261, CVE-2026-7262, CVE-2026-7568)

• zfs: 2.3.4_6.12.82_Unraid → 2.3.4_6.12.90_Unraid
  
  are you telling us to down grade then move to this for CVEs or is a 7.3.1 soon to be release???...

https://docs.unraid.net/unraid-os/release-notes/7.3.0/#updated-packages-141

cross-referenced per docs still need to double check on usb...

I would not describe 7.2.7 as “telling you to downgrade from 7.3.” It looks like 7.2.7 is a security/maintenance patch for the 7.2 branch, while 7.3.0 is the newer feature branch with internal boot / TPM licensing / newer kernel / newer ZFS stack.

The uncomfortable part: 7.2.7 is newer than 7.3.0 in a few specific security package binaries. So my concern is valid.

Cross-reference: 7.2.7 vs 7.3.0

Package	7.2.7	7.3.0	Is 7.3 older?
aaa_glibc-solibs	2.42 → 2.43	not listed as updated in 7.3.0 package list	Likely yes / not shown updated
avahi	0.8-3_SBo_LT → 20260508_3737842-1_SBo with CVE-2023-38469 through CVE-2023-38473	not listed in 7.3.0 updated packages	Likely yes / missing from 7.3.0 list
curl	8.19.0 → 8.20.0	8.19.0 → 8.20.0	No, same fixed version
docker	29.3.1 → 29.5.1	29.3.1 → 29.4.3	Yes, 7.3.0 is older
glibc	2.42-2_LT → 2.43	not listed in 7.3.0 updated packages	Likely yes / missing from 7.3.0 list
gnutls	3.8.12 → 3.8.13	3.8.12 → 3.8.13	No, same fixed version
jq	1.6 → 1.8.1	not listed in 7.3.0 updated packages	Likely yes / missing from 7.3.0 list
libvirt-php	0.5.8-8.3.29 → 0.5.8-8.3.31	0.5.8-8.3.29 → 0.5.8-8.4.21	7.3 is different/newer PHP ABI build, not directly older
nginx	1.27.2 → 1.30.1	not listed in 7.3.0 updated packages	Likely yes / missing from 7.3.0 list
php	8.3.29 → 8.3.31	8.3.29 → 8.4.21	No, 7.3 is newer major/minor
zfs	2.3.4_6.12.82 → 2.3.4_6.12.90	2.3.4_6.12.82 → 2.4.1_6.18.29	No, 7.3 has newer ZFS + newer kernel build

Sources: 7.2.7 lists the 11 updated security packages, including Docker 29.5.1, glibc 2.43, nginx 1.30.1, PHP 8.3.31, and ZFS rebuilt for kernel 6.12.90. 7.3.0 lists Docker 29.4.3, curl 8.20.0, GnuTLS 3.8.13, PHP 8.4.21, ZFS 2.4.1_6.18.29, and says “Downgraded packages (0).” Your pasted 7.3 package list matches the official 7.3.0 package section, including curl, docker, gnutls, PHP, and ZFS.

The important conclusion

7.3.0 does not appear to contain every package refresh that 7.2.7 contains.

Specifically, based on the public release notes:

7.3.0 appears behind 7.2.7 on:

docker: 7.3.0 has 29.4.3, while 7.2.7 has 29.5.1
nginx: 7.3.0 does not show the 1.30.1 security bump
glibc / aaa_glibc-solibs: 7.3.0 does not show the 2.43 bump
avahi: 7.3.0 does not show the 20260508 CVE bump
jq: 7.3.0 does not show the 1.8.1 CVE bump

7.3.0 is not behind on:

curl: same 8.20.0
gnutls: same 3.8.13
php: 7.3.0 has 8.4.21, newer than 7.2.7's 8.3.31
zfs: 7.3.0 has 2.4.1 on kernel 6.18.29, newer than 7.2.7's 2.3.4 on kernel 6.12.90
kernel: 7.3.0 has 6.18.29, while 7.2.7 has 6.12.90

33 minutes ago, bmartino1 said:

due to the recent https://forums.unraid.net/topic/198979-unraid-727-now-available
7.27 update can we get a confirmation that 7.3 has the updated binaries as well?

are the same cve updated in 7.3?

as repoprted in 7.2???

aaa_glibc-solibs: 2.42 → 2.43

• avahi: 0.8-3_SBo_LT → 20260508 (CVE-2023-38469, CVE-2023-38470, CVE-2023-38471, CVE-2023-38472, CVE-2023-38473)

• curl: 8.19.0 → 8.20.0 (CVE-2026-4873, CVE-2026-5545, CVE-2026-5773, CVE-2026-6253, CVE-2026-6276, CVE-2026-6429, CVE-2026-7009, CVE-2026-7168)

• docker: 29.3.1 → 29.5.1

• glibc: 2.42 → 2.43 (CVE-2025-15281, CVE-2026-0861, CVE-2026-0915)

• gnutls: 3.8.12 → 3.8.13 (CVE-2026-33846)

• jq: 1.6 → 1.8.1 (CVE-2024-53427, CVE-2025-9403)

• libvirt-php: 0.5.8-8.3.29 → 0.5.8-8.3.31

• nginx: 1.27.2 → 1.30.1 (CVE-2025-53859, CVE-2026-1642, CVE-2026-27651, CVE-2026-27654, CVE-2026-27784, CVE-2026-28753, CVE-2026-28755, CVE-2026-32647, CVE-2026-40460, CVE-2026-40701, CVE-2026-42934, CVE-2026-42945, CVE-2026-42946)

• php: 8.3.29 → 8.3.31 (CVE-2025-14179, CVE-2026-6722, CVE-2026-6735, CVE-2026-7258, CVE-2026-7259, CVE-2026-7261, CVE-2026-7262, CVE-2026-7568)

• zfs: 2.3.4_6.12.82_Unraid → 2.3.4_6.12.90_Unraid
  
  are you telling us to down grade then move to this for CVEs or is a 7.3.1 soon to be release???...

7.3.1 is coming too.

On 5/19/2026 at 7:06 PM, Gadgetman said:

yes i had this issue also, dockers disappeared and if you reboot different ones came and went.

all sorted now but i spent hours sorting out.

next issue is time machine no longer works

this has been the worst update for me.

That's wild.
Sorry to hear it: this has been the best update for me since the jump to v7.

My CPU now runs cooler, and draws around 25w less on average with no performance degradation, thanks to the improvements to the EPP AMD Pstate drivers. The Tips & Tweaks plugin (now known as Tips & Tweaks Next) has also been updated to easily change between them, too, and better support the different approaches to Intel & AMD power profiles.

All my Dockers worked without issue from the get-go. I don't know why some people are having problems with Docker. I know the jump with the eailer 7.2.5 (or .6?) updated the Docker engine, which caused some troubles, but mine were quickly reolved.

So I say again: well done, Unraid. I'm very pleased with this update.

Hello good people:)

With this update 7.3 is a new feature TPM.. Do i have to change anything in my setup before updating?? like a bios change?? or is it just like every other update?? I am still going to keep using my usb-stick as primary key..

Is there any other settings that has to be changed, before updating??

Thank you!

regards

51 minutes ago, Mattti1912 said:

I am still going to keep using my usb-stick as primary key..

You don't need to change anything. If the server has TPM 2.0, and is enabled, you have the option to transfer the license to it.