whiskerz007 / proxmox_hassio_lxc

MIT License
208 stars 83 forks source link

Getting an "Unknown failure occurred." #28

Open NoBloodyABCorD opened 4 years ago

NoBloodyABCorD commented 4 years ago

I feel this might be related to my setup.. Proxmox is hosting its own gateway as a vm. Proxmox does have internet and updates just fine.

root@Vanguard:~# bash -c "$(wget -qLO - https://github.com/whiskerz007/proxmox_hassio_lxc/raw/master/create_container.sh)" [INFO] Using 'local-lvm' for storage location. [INFO] Container ID is 102. Updating LXC template list... Downloading LXC template... Creating LXC container... Starting LXC container... Setting up container OS... Updating container OS... W: Failed to fetch http://ftp.debian.org/debian/dists/buster/InRelease Temporary failure resolving 'ftp.debian.org' W: Failed to fetch http://ftp.debian.org/debian/dists/buster-updates/InRelease Temporary failure resolving 'ftp.debian.org' W: Failed to fetch http://security.debian.org/dists/buster/updates/InRelease Temporary failure resolving 'security.debian.org' W: Some index files failed to download. They have been ignored, or old ones used instead. Installing prerequisites... [ERROR:LXC] 100@39 Unknown failure occured. [ERROR] 100@163 Unknown failure occured. Logical volume "vm-102-disk-0" successfully removed

edit: not sure why I can't format the terminal output so sorry for that image

NoBloodyABCorD commented 4 years ago

OK it was actually the network bridge the vm was creating. After the "Setting up container OS..." appeared, I changed the bridge to the correct one in the webui and it successfully updated and finished installation

whiskerz007 commented 4 years ago

This has happen in the past with Proxmox DNS settings being the culprit. Check your DNS settings for Proxmox and see if it is set to a public DNS. The LXC, by default, uses Proxmox OS DNS for resolution and if it is set to 127.0.0.x this will definitely cause issues. The setting can be configured by going to Datacenter -> Node (pve) -> System -> DNS.