redcalcium

From the posted log, it appears to try to download ghcr.io/home-assistant/generic-x86-64-homeassistant:2024.4.4 docker image and failed due to http 500 server error .

Can you post how you were trying to install home assistant? E.g are you using docker compose?

Why not using ghcr.io/home-assistant/home-assistant:2024.4.4?

My favorite is streaming apps geoblocking contents and blocking access from all known vpn networks, then wondering why piracy on the rise again.

You made one critical error in this perpetual energy machine plan: linux users don’t go outside.

Wait until you see this:

https://brokensecrets.com/2010/12/20/9-volt-batteries-contain-6-aaaa-batteries/

Unihertz rarely mentioned in discussion about small phones. I wonder why.

Unlike hdd, I never experienced graceful disk failures on ssd. Instead, they just randomly decided to die at the most inconvenient time. Raid 1 saved my hide a couple times now from those ssd failures.

In that case, perhaps replacing -o sftp_server="/usr/bin/sudo /usr/lib/openssh/sftp-server" with -o sftp_server="/usr/bin/sudo -u <syncthing_user> /usr/lib/openssh/sftp-server" is a good compromise?

So the workaround is running the SFTP process as root?

Why not run the SFTP server as a docker container as well (e.g. with https://hub.docker.com/r/atmoz/sftp/ )? You can mount the same volume in the SFTP container, and have it listen on some random port. Just make sure to configure the SFTP container to use the same uid:gid as the one used in the syncthing container to avoid file permission issues.

The easiest setup I tried so far is to simply put your docker container’s volume on an external path, e.g. /mnt/hdd1/some-directory, instead of putting it in the standard docker location (/var/lib/docker/volume). You’ll have full control over ACL on those custom paths.