But I’ve been getting this error:

[supervisor.docker.interface] Can't install ghcr.io/home-assistant/generic-x86-64-homeassistant:2024.4.4: 500 Server Error for http+docker://localhost/v1.44/images/create?tag=2024.4.4&fromImage=ghcr.io%2Fhome-assistant%2Fgeneric-x86-64-homeassistant&platform=linux%2Famd64: Internal Server Error ("Get "https://ghcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)") [supervisor.homeassistant.core] Error on Home Assistant installation. Retrying in 30sec

I’ve tried changing DNS, but it didn’t help and I seem to get no other helpful results from searching. If anyone has any suggestions I’d appreciate it as this seems to be something my home could benefit from but it’s just not loading beyond the CLI

      • @beeng@discuss.tchncs.de
        link
        fedilink
        English
        4
        edit-2
        2 months ago

        You actually want to do it from your host machine, not the haos machine, since the container you are looking for seems to be the haos itself, so it’s your host that is trying to download it, if i understand correctly.

        Otherwise why is your haos needing the generic home assistant container? AFAIK it shouldn’t download itself to update itself.

        Maybe that’s the issue? You’re trying to download from inside the haos instead of outside? (host)

        • @captainlezbian@lemmy.worldOP
          link
          fedilink
          English
          12 months ago

          Ok, is there a different haos I should download to put on my machine? Idk how to use docker and the machine is formatted aside from following the haos on x86 instructions from the website

          • @beeng@discuss.tchncs.de
            link
            fedilink
            English
            12 months ago

            If you’re a beginner, just look into haos virtual machine image, and a guide to go with… Might be easiest. You can snapshot your progress along the way to ensure copies

            • @captainlezbian@lemmy.worldOP
              link
              fedilink
              English
              12 months ago

              Fucking hell I tried installing Debian and it didn’t even see the boot media…

              Now to see if home assistant running in the background of my small kubuntu will work…

            • @captainlezbian@lemmy.worldOP
              link
              fedilink
              English
              12 months ago

              Ok, it looks like I’m setting up Debian today and seeing if I can get a virtual machine in the background. I wanted this to be an easy way to dip my toes into self hosting…

  • @Powdermilkman@lemmy.world
    link
    fedilink
    English
    42 months ago

    Ok, so you wrote the hass os image to your internal SSD using kubuntu booted from a flash drive. Then when you booted hass os from the SSD you’re getting networking errors not being able to download the docker image from ghcr.io.

    Can you visit ghcr.io from other devices on your network?

    Can you ping ghcr.io from the hass os installation?

    If you can’t ping ghcr.io can you ping google.com?

    If you can’t ping either then your network interface might have not been set up correctly and or hass os is missing drivers for you network interface.

    Are you connecting over Ethernet or wifi?

    • @captainlezbian@lemmy.worldOP
      link
      fedilink
      English
      3
      edit-2
      2 months ago

      Thank you.

      My desktop can access ghcr.io (assuming it’s supposed to return GitHub).

      I don’t know how to ping from cli on haos. (It autofills the ha command)

      I’m connecting over Ethernet using the same cable and connections that did work when kubuntu was on it

  • @redcalcium
    link
    English
    22 months ago

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

    • @captainlezbian@lemmy.worldOP
      link
      fedilink
      English
      32 months ago

      Ok I’m going to sound like an idiot but this is my first doing of anything with any servers, so I apologize if I’m missing something obvious. What command should I use with it? I typed it in alone just in case and got an unknown command

      • @redcalcium
        link
        English
        32 months ago

        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?

        • @Successful_Try543@feddit.de
          link
          fedilink
          English
          2
          edit-2
          2 months ago

          The title states:

          Attempting to use Home Assistant OS

          So OP uses the preconfigured “ready to go” solution with the supervisor doing the setup and upgrades. Which somehow is not succesfull in doing so.

          • @redcalcium
            link
            English
            2
            edit-2
            2 months ago

            Never thought that home assistant os would actually use docker under the hood. I thought it’s running home assistant directly with supervisor method.

        • @captainlezbian@lemmy.worldOP
          link
          fedilink
          English
          22 months ago

          No i followed the x86 instructions from the website, so I was using an Ubuntu (ok I deviated to kubuntu because I wanted a drive with it anyways) flash drive to run disks to put the os on the internal ssd from the link found here

          • @redcalcium
            link
            English
            1
            edit-2
            2 months ago

            Is this the tutorial you followed? https://www.home-assistant.io/installation/generic-x86-64

            On which step did you encounter the error? The step where the home assistant os already written to the target disk and you’re told to restart the system with usb stick unplugged?

            http error 500 when downloading the container image might be a temporary error on github docker repo side. Try restarting the device and see if the error persist.