-
Notifications
You must be signed in to change notification settings - Fork 83
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
Failed to initialize Container #51
Comments
After trying to commend the line as mentioned here: [INFO] Using 'BackupNAS' for template storage. |
Updating the OSVersion from 10 to 11 fixed that problem aswell! |
And faced a new problem: [INFO] Using 'BackupNAS' for template storage. searching for a solution, hold on. |
When i read this correctly, its Char 8 at line 130. I dont see a problem there, someone got an Idea? |
Hi...I've run into similar issues. Did you find a resolution for the last one? It appears this version hasn't been updated in several years. I'm currently searching to see if anyone picked up the development for this somewhere else (I don't see any forked threads of this one). I'd really like to run HA in an LXC since the resource use is so much lower. I already moved an XMRIG miner from a vm to lxc and saw a MASSIVE drop in the resource use (specifically RAM), but doubled it's production. It's be nice if I could do the same with my HA VM. |
You can delete this line because this directory is already persistent. But then you get a new error because the Base_URL is not existing anymore. After fixing this I got an error at Networkmanager Install because he wants an default connection conf wich is not used by HA anymore.. it's my 25th try to get this installed.. |
Failed to start hassio-supervisor.service: Unit hassio-supervisor.service has a bad unit file setting. im at the end of my knowledge.. i switched to HA Dockerized in LXC Container.. |
I'm facing the same in Proxmox VE 7.3-4.
|
bash -c "$(wget -qLO - https://github.com/whiskerz007/proxmox_hassio_lxc/raw/master/create_container.sh)"
[INFO] Using 'BackupNAS' for template storage.
[INFO] Using 'LUN0' for container storage.
Upating LXC template list...
Downloading LXC template...
Creating LXC container...
[INFO] LXC container '104' was successfully created.
Starting LXC container...
run_buffer: 321 Script exited with status 1
lxc_init: 847 Failed to run lxc.hook.pre-start for container "104"
__lxc_start: 2008 Failed to initialize container "104"
startup for container '104' failed
[ERROR] 255@100 Unknown failure occured.
Logical volume "vm-104-disk-0" successfully removed
Can someone help?
Latest Proxmox:
proxmox-ve: 7.2-1 (running kernel: 5.15.35-3-pve)
pve-manager: 7.2-5 (running version: 7.2-5/12f1e639)
pve-kernel-5.15: 7.2-5
pve-kernel-helper: 7.2-5
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.35-3-pve: 5.15.35-6
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 16.2.9-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-2
libpve-storage-perl: 7.2-5
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.3-1
proxmox-backup-file-restore: 2.2.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-10
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1
The text was updated successfully, but these errors were encountered: