search

JonathanTreffler / backblaze-personal-wine-container

Run the Backblaze personal backup client in a docker container
https://hub.docker.com/r/tessypowder/backblaze-personal-wine
GNU Affero General Public License v3.0
396 stars 33 forks source link

(fix): change check for wine initialization #115

Closed xela1 closed 8 months ago

xela1 commented 9 months ago

I was doing some further testing and if a user attempted to use the last version of the container and it created /config/wine but failed to download the backblaze client they could be in a position where it thinks wine is already initialized when it's not.

This isn't urgent as most users can either remove the local volume they created and start again or a couple of restarts will fix, but this fix should stop the requirement for any user intervention

As an added benefit, I've found a way to suppress the mono prompt, I've tested and we don't seem to need it anyway

traktuner commented 8 months ago

Hey, thank you for the PR! Just a cosmetic change. Please put the WINEDLLOVERRIDES env at the top of the script, beneath WINEARCH.

xela1 commented 8 months ago

Done

traktuner commented 8 months ago

Done

Thank you! I am also very certain that mono is not needed since Backblaze is a C++ application.