-
Notifications
You must be signed in to change notification settings - Fork 192
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
LXD create VM for Hassio #118
Comments
I managed to get Home Assistant service running buy using a bridged network instead. My only issue is that I can only run commands using |
Thnak you for the steps to import the VM image into LXD. I also think it's a nice way to run vms (using lxd instead of libvirt). The bridge is the way to go to connect into the host network. How is this after almost two years? Still have any issues? I'm planning on doing this in a few days with latest version. |
Hello! This is not an issue but I'm posting here to get in contact with you.
I have been using this script to get home assistant VM setup, as part of my Proxmox automated installation. I am now moving away from Proxmox, and rewriting my automated installation for Debian, to have a similar setup script between intel and pi chips.
So I am now using LXD v4 on Debian to run my containers and also VMs!
I am having quite a rough time to run Home Assistant Operating System image on an LXD VM. I would appreciate if you can assist me on this. I think this will be very helpful to the HA community as LXD VMs become more stabilized! This is what I did so far:
After installing LXD using Snap and initializing it:
tar -cvzf metadata.tar.gz metadata.yaml
lxc image import metadata.tar.gz haos_ova.qcow2 --alias hassio
lxc launch hassio ha --vm -c security.secureboot=false
At this point I can do
lxc console ha
to get into the HA OS VM's console. Two problems I have right now.I think the issue is that I don't have LXD-agent in the VM since the provided image from HA website is used.
I have setup a Macvlan network on my host to provide LAN network to my containers and VMs, by using this custom profile instead when creating an LXD container or VM:
The text was updated successfully, but these errors were encountered: