Closed sed-i closed 2 years ago
Hi @sed-i, this sounds like a candidate for a Workflow, care to take a stab at it?
@Saviq, launching a workflow would re-run the commands every time, correct? Is there a way to take the result of a workflow and turn it into an image? Just to save time on snap install etc.
@sed-i currently we don't support custom images, but that's something we wanted to fix as well. What needs to be taken into account, though, is refreshing the image from time to time - and who will be responsible for that.
FWIW I've documented how to make Multipass-compatible images here:
https://discourse.ubuntu.com/t/building-multipass-images-with-packer/12361
@Saviq How can I test locally my draft #5 ?
@sed-i you can override the systemd service like so:
# /etc/systemd/system/snap.multipass.multipassd.service.d/override.conf
[Service]
Environment="MULTIPASS_WORKFLOWS_URL=https://github.com/sed-i/multipass-workflows/archive/refs/heads/charm-dev.zip"
Is there a way to see stdout/stderr of the commands in the runcmd section?
I am using multipass launch -vvvv
and all I see is "Waiting for initialization to complete".
Is there a way to see stdout/stderr of the commands in the runcmd section?
When you see "Waiting...", you can interrupt that and multipass shell …
, and inside see /var/log/cloud-init*
.
What are you trying to do? It would be nice to be able to launch (disposable) instances of juju and related tools needed for charm development. Launching an instance and installing all the tools takes quite some time.
What's your proposed solution? Have an official "juju-dev" image with microk8s and charmcraft. MicroK8s should ideally be set up per https://juju.is/docs/sdk/dev-setup
Additional context NTA.