constellation/cli/internal/libvirt
Daniel Weiße 625dc26644
cli: unify cloudcmd create and upgrade code (#2513)
* Unify cloudcmd create and upgrade code
* Make libvirt runner code a bit more idempotent

---------

Signed-off-by: Daniel Weiße <dw@edgeless.systems>
2023-10-31 12:46:40 +01:00
..
etc cli: convert libvirt container image to Bazel 2023-04-18 15:35:15 +02:00
nvram cli: convert libvirt container image to Bazel 2023-04-18 15:35:15 +02:00
BUILD.bazel cli: convert libvirt container image to Bazel 2023-04-18 15:35:15 +02:00
libvirt.go cli: unify cloudcmd create and upgrade code (#2513) 2023-10-31 12:46:40 +01:00
libvirtd.conf cli: convert libvirt container image to Bazel 2023-04-18 15:35:15 +02:00
qemu.conf cli: convert libvirt container image to Bazel 2023-04-18 15:35:15 +02:00
README.md bazel: remove apko and Dockerfile where Bazel is used to build container images 2023-04-18 15:35:15 +02:00
start.sh cli: convert libvirt container image to Bazel 2023-04-18 15:35:15 +02:00

Containerized libvirt

To avoid dependency issues with the libvirt setup of the host, we provide a containerized libvirt instance. If no libvirt connection string is provided in the Constellation config file during create, this container is deployed to provide a libvirt daemon for orchestrating Constellation nodes in QEMU.

The container will listen for libvirt connections on localhost:16599. Connecting to the libvirt daemon running in the container and manage the deployment using virsh run the following:

virsh -c "qemu+tcp://localhost:16599/system"

Docker image

Build the image:

bazel build //cli/internal/libvirt:constellation_libvirt
bazel build //bazel/release:libvirt_sum
bazel build //bazel/release:libvirt_tar
bazel run //bazel/release:libvirt_push

A container of the image is automatically started by the CLI. You can also run the image manually using the following command:

docker run -it --rm \
    --network host \
    --privileged true \
    ghcr.io/edgelesssys/constellation/libvirt:latest