Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Several unrelated docker containers suddenly failing with healthcheck failure "Output: ttrpc: closed: unknown"

Featured Replies

I've noticed recently that many of my docker containers have been stopping unexpectedly. These are common official docker containers such as NodeRed and Plex.

They all stop for the same reason - docker healthcheck failure due to the error: "Output": "ttrpc: closed: unknown"

I found the error with the "docker inspect" command.

Interestingly, only docker containers with a healthcheck set are failing.

This started happening after updating Unraid to 7.2.0 - I don't remember what version I was on before, but it was at least 6 months older.

I've tried searching docker forums for similar issues, but the only relevant one I could find was fixed 5 years ago: https://github.com/containerd/containerd/issues/4483

Any ideas?

UPDATE (Edit because I can't post more than once a day yet)

I'm starting to see other docker containers stop for different reasons now too:

  • docker: Error response from daemon: failed to create task for container: failed to start shim: start failed: SIGBUS: bus error

  • Exit Code 137

It sort of sounds like an OOM error, but I'm not even close to the limits (Docker is using 3GB, I have around 10GB free).

eggsbenjamin-diagnostics-20251107-1052.zip

Edited by Sprakle
Update

  • Community Expert

Nov 6 04:01:02 EggsBenjamin kernel: SQUASHFS error: xz decompression failed, data probably corrupt

Nov 6 04:01:02 EggsBenjamin kernel: SQUASHFS error: Failed to read block 0xe5a480: -5

Nov 6 04:01:02 EggsBenjamin kernel: SQUASHFS error: xz decompression failed, data probably corrupt

Nov 6 04:01:02 EggsBenjamin kernel: SQUASHFS error: Failed to read block 0xe5a480: -5

Nov 6 04:01:02 EggsBenjamin kernel: SQUASHFS error: xz decompression failed, data probably corrupt

Nov 6 04:01:02 EggsBenjamin kernel: SQUASHFS error: Failed to read block 0xe5a480: -5

These are typically the result of a bad flash drive, but can also be a hardware issue, like bad RAM, though I would start with the flash drive, since it is by far the main reason for these.

  • Author

Oh thanks for noticing that! Okay this makes sense, I'll try swapping the drive.

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.