Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting an "Unknown failure occurred." #28

Open
NoBloodyABCorD opened this issue May 24, 2020 · 2 comments
Open

Getting an "Unknown failure occurred." #28

NoBloodyABCorD opened this issue May 24, 2020 · 2 comments

Comments

@NoBloodyABCorD
Copy link

NoBloodyABCorD commented May 24, 2020

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
Copy link
Author

NoBloodyABCorD commented May 24, 2020

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
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants