#"OverflowError: timeout too large" on initial installation of stable image via Docker Compose
1 messages · Page 1 of 1 (latest)
I am going to weed out insanity (read: my computer is bad). I'm signing up for the free tier of Oracle Cloud to get a VM to try the same thing.
While it won't solve my problem, it could at least narrow down problem to the host and not the image.
@peak stone Wanted to reply here to avoid gunking up the top-level channel
The directory permissions are root:root, as I'm currently running this in a Debian LXC where only the root user is available. The /data/home-assistant directory, though, correctly inherits whatever permissions are listed in the environment.PUID:PGID (if any is specified).
As for the command, just a classic docker compose -d with configuration saved in a docker-compose.yml with nothing else in the directory.
Just out of curiosity, try a docker compose pull && docker compose up -d and see if that helps at all. Might want to kill the current image as well first.
sure thing! I may have to dip soon for a prior commitment but I've got enough time for a fresh pull & try. I'll do it with the exact config from the website to minimize moving pieces.
Yeah, I’m mobile ATM myself. But if that doesn’t work, ping me here later. I’ve got a couple of other ideas.
Yeah, same deal with the OverflowError. Super weird — when I have a chance later today I'll try again on the Oracle VM.
Tbh, a straight Debian/Ubuntu image is the way to go if you can.
That's what I had yesterday — HASS is a big enough part of my day-to-day that I've been cycling through operating systems trying to get this to work again.
It's strange because I've successfully run HASS on this hardware before — this whole foray into trying a fresh install has been trying to figure out why my original installation on stable started crashing with the same error.
I run it in a bare bones Debian 12 system with docker compose.
Yeah, yesterday was trying this on fresh installs of Debian12 and Ubuntu24 trying to get it to work — same error, no dice
The other thing to try might be pulling 2024-07-02 and see if that works. Could be something weird in 07-03.