fix: stop forced-update

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

374 stars 35 forks source link

fix: stop forced-update #145

Closed traktuner closed 4 months ago

traktuner commented 4 months ago

In this PR:

send official update URL to localhost to stop forced update (to gain more control over client updates).

This seems to be the only URL where official updates get pulled from.

should fix #144

francop311 commented 4 months ago

I added comments to the https://github.com/JonathanTreffler/backblaze-personal-wine-container/issues/144 --but wanted to add it here as well:

BTW. For me the update did not work.

It seems that the entry for f000.backblazeb2.com in the /etc/hosts is not being populated, as I get a "permissions denied" when startup.sh script is trying to update the hosts file.

lps-rocks commented 4 months ago

Same here: This is due to the fact that the startapp.sh runs as UID 1000 but /etc/hosts needs root permissions to be modified. since the UID 1000 user is not in sudoers it can't use sudo either.

I'm working on a more advanced way of doing this too. There's multiple avenues that can be taken to blocking updates - Another one I found that might work is blocking the bzupdates folder from being utilized.

traktuner commented 3 months ago

@lps-rocks I like the way how you disable the updates with init scripts. Can you maybe open a PR that we can implement it here, or may I borrow your idea for our repo? Thank you!