Support thread for all my Docker Templates listed below.

• Tronbyt Server - https://github.com/tronbyt/server or @bigsing on the Tronybt Discord

• Joplin Server - https://hub.docker.com/r/joplin/server/

This thread is reserved for issues with the Unraid Docker templates. For issues with an application itself, please redirect your concern to the app's own support channels.

Edited May 20May 20 by bigsing

hello @bigsing I tried updating the joplin server container today and got these errors:

on first attempt:

Error: failed to register layer: symlink ../is-docker/cli.js /home/joplin/packages/tools/node_modules/is-inside-container/node_modules/.bin/is-docker: no space left on device

After deleting dangling images and trying the update again:

Error: failed to register layer: rename /var/lib/docker/image/btrfs/layerdb/tmp/write-set-1037592548 /var/lib/docker/image/btrfs/layerdb/sha256/5d0ffcca6050b9c12db964453426d0c2bf06c4a53fb7754feeda08f53a3cf424: file exists

Most recent error after restart of server

Error: failed to register layer: stat /var/lib/docker/btrfs/subvolumes/86b495e8380343d3afecd0d824c96ac20aad70eb2b482b84d7b2084b184633ae: no such file or directory

Any ideas for solution to this?

When i've seen this issue in the past it's either a corrupted docker image or the docker image was full. Typically you need to delete and rebuild the docker.img or setup a docker folder instead so it can grow as needed. Here's a good video on it - https://www.youtube.com/watch?v=XbsU1I810bw

Ok. Thanks for the quick response. I will take a look.

I just ran into a different issue with the tronbyt server container today after updating my unraid box to 7.3.0. It looks like /etc/localtime no longer works. I changed the variable to point at my local time zone instead (/usr/share/zoneinfo/America/Vancouver) and the container fired up.

edit: someone else pointed me to check my box's time zone setting, it had somehow gotten set to UTC-10 instead of -8. fixing this and then setting the container back to /etc/localtime worked..

Edited May 20May 20 by goalcam

On 5/19/2026 at 8:52 PM, bigsing said:

When i've seen this issue in the past it's either a corrupted docker image or the docker image was full. Typically you need to delete and rebuild the docker.img or setup a docker folder instead so it can grow as needed. Here's a good video on it - https://www.youtube.com/watch?v=XbsU1I810bw

Hey @bigsing, Just following up to say thanks. Rebuilding the docker image solved my problem.