Dozzle supports a main instance and multiple agent instances that act as agents.

I was able to load it in unraid as a compose file, but it would be ideal to extend the wrapper.

```

version: '3.8'

services:

dozzle:

container_name: dozzle

image: amir20/dozzle:latest

command: agent <----------

restart: always

environment:

- tailSize=1000

- DOZZLE_HOSTNAME=<redacted>

volumes:

- /var/run/docker.sock:/var/run/docker.sock

ports:

- 9095:7007

```

On 5/18/2026 at 2:20 PM, kurai said:

Further steps for Backblaze docker

The previous steps got Backblaze started and running ... for a while.

The Backblaze binaries seem to have some inbuilt mechanism for triggering detection of old executable versions and downloading of an update, despite the docker parameters 'Force Latest Update: False' and 'Disable Autoupdate: true' being applied.

Two hours after container start it would download a new .exe binary (interestingly, not the current version v.10.0.1.1037 but v.9.2.2.897). This would unpack and run an .msi installer, which would then abort after failing to satisfy a .NET dependency. This seems to have a greater than even chance of causing the main bzserv.exe service and/or bzbui.exe application to crash out. It would continue to retry this update process every 2 hours until the inevitable crash & black-screen.

The solution (that's been working for over 24 hours now) seems to be to replace the downloaded binary with an empty zero byte file and set it to root read-only (-r-------- [400]) so that it can't be replaced by the updater.

/appdata/Backblaze_Personal_Backup/wine/drive_c/Program Files (x86)/Backblaze/bzupdates/bzinstall-win32-9.2.2.897.exe [root -r-------- 0 B]

This seems to sidestep the issue by not allowing the installer process to begin at all.

Of course, this may not work forever ... the application does do a version check call-in at startup, and logs that it recieved a version obsolescence notice. Backblaze seem to be making definite steps to move forward with client versioning and may eventually reject connections from old enough clients rather than simply warning and trying to force an update.

Thanks for this idea, i'm trying the root read-only thing.

Until now i had the Backblaze docker restart with a user script every two hours.

Fingers crossed!

11 hours ago, EvilSpice said:

Fingers crossed!

It's been running uninterrupted since I posted that, so over 10 days now.

Hope it works for your install too 😄

re: Backblaze Docker

New version 2.0.1 has been published

Jonathan Treffler has undertaken a major refactor which results in the succesful implementation of Backblaze client v10.0.1.1037 (x64)

It also includes some nifty features for accessing network drives directly, which means some of the old workarounds are no longer neccessary.

(Several container options have changed, so read the release notes at https://github.com/JonathanTreffler/backblaze-personal-wine-container/releases)

Along the way he addressed the root causes of the majority of "black screen" errors we have been experiencing. 😜

I tested the new v2.0.1 release with a fresh container and it downloaded and installed the current v10 client from Backblaze and installed/ran it succesfully.

( I spun up a new container beause I couldn't get my ancient docker install to upgrade client succesfully - probably because of some of the crufty old nonsense I've got laying about in my Backblaze /appdata after a years-worth of tinkering.

However ... there's now a graceful fallback to just run the pre-existing old client version upon upgrade-failure, instead of crashing & causing the black screen 👍

No need for my kludgy permissions fix to the updater .exe any more - my backups with the old client continue to run fine. )

I'm at a loss. My Backblaze_Personal_Backup broke a few days ago. I'm not exactly sure of the timing; I think it was between the latest update and the one just prior. None of my Docker settings were changed, but suddenly I was back in a trial. My hostname ("Online name for this computer") had changed (I did NOT reinstall!), and I was unable to do anything about it. I tried using sed to update /config/wine/system.reg, but the change wouldn't stick.

That's where I am now. I have just updated the container to the latest 2.0.1 release - version shows 10.0.1.1037 (20260325214016) - but nothing has changed. I'm still in a trial, still on a different and unchangeable hostname. I think the correct path forward would be to perform an "inherit backup state," and I've tried, but can't complete it. The issue seems to be that I simply can't enter my email/password into the GUI.

I am open to any and all ideas.

Edited June 19Jun 19 by molasses2

@molasses2

For what it's worth - I finally got around to trying to actually use the new Selfhosters - Backblaze_Personal_Backup container with the v10.x client, instead of stumbling along with my old v9.x setup, and ran into much the same issue.

After futzing with it for a while I gave up and installed the iamfoz - Backblaze64 container instead.

This seemed to have the same issue, but while I was poking around in its logs I retried the Inherit process and this time it succeeded. 🤯

I never got to this point with the updated Selfhosters - Backblaze_Personal_Backupinstall even after several hours of tinkering.

The iamfoz - Backblaze64 install now appears to be operating correctly and uploading new data to the extant backup state.

Write-up here: https://forums.unraid.net/topic/199284-support-backblaze-64-backblaze-personal-backup-10x-64-bit-under-wine/#findComment-1628631

Edited June 21Jun 21 by kurai

@kurai Thank you SO MUCH for this suggestion! I guess I was under the impression that Backblaze64 was geared toward B2 storage rather than the personal backup. That's my fault for not reading carefully.

In any case, I was successful in performing an inherit backup state. I didn't have to do anything special to make it work - didn't even have to change the default UID/GID or set the container to privileged. I read foz' post that discussed timeout concerns, but couldn't figure out how to adjust that in B_P_B.

I am likewise grateful to @TessyPowder and @foz for their work!!!

Edited June 22Jun 22 by molasses2