[SOLVED]Cannot update Core or HA (unknown error) - On ubuntu Docker

Configuration
21

Yup, 3 of them:
01-netcfg.yaml 01-netcfg.yaml.save 50-cloud-init.yaml

01-netcfg.uyaml:

network:
  version: 2
  renderer: networkd
  ethernets:
    enp5s0f2:
      dhcp4: no
      addresses:
        - correct IP /24
      gateway4: gatway IP
      nameservers:
          addresses: [8.8.8.8, 1.1.1.1]

50-cloud-init.yaml was empty so i edited with the same settings as @francisp suggested.

network:
    ethernets:
        enp5s0f2:
            dhcp4: false
            addresses: [hassio ip/24]
            gateway4: gateway ip[
            nameservers:
              addresses: [8.8.8.8,1.1.1.1]
    version: 2

Changed dhcp4: no to false, just in case

Rebooted, nothing :frowning:

22

Has somebody already an idea which component was altered so we now have bug appearing?

23

I donā€™t know if Iā€™m answering your question but, Iā€™m under the impression this started for me when i uninstalled pi-hole, which was depreciated.

24

I did not change something on my setup besides of updates. so no newly installed things or uninstalled things.
I always was using AdGuard - never pihole.

My impression is it either started out of the box because of a component changed which I am not yet aware of OR it started with the update to 0.110.3
Can some of that assumptions be proven? @frenck maybe?

25

So, it turns out there was some connectivity issues (wrong DNS settings) in the host pc.
Why they appeared i have no idea but hereā€™s how i fixed them and updated:

(fix and instructions to make it stick)

26

Had same problem.
This thread helped to see problems started with uninstalling AdGuard.
Needed to restart systemd-resolved.service and setup dns servers.
Work ok now.
THanks

27

Selbiges Problem beim Update auf ā€œcore-2021.4.4ā€.
FĆ¼r das Update muss ich in meiner FritzBox den DNS-Server von dem laufenden AdGuard-Plugin auf Standard wieder Ƥndern.
Anscheinend hat das Update ein Problem mit blockierten Domains.