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

limactl start should wait until all provision scripts complete (and report errors on failure) #209

Open
AkihiroSuda opened this issue Sep 5, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@AkihiroSuda
Copy link
Member

Currently we have to inject probes script in addition to provision like this:

lima/examples/k3s.yaml

Lines 30 to 47 in be68278

provision:
- mode: system
script: |
#!/bin/sh
curl -sfL https://get.k3s.io | sh -
probes:
- script: |
#!/bin/bash
set -eux -o pipefail
if ! timeout 30s bash -c "until test -f /etc/rancher/k3s/k3s.yaml; do sleep 3; done"; then
echo >&2 "k3s is not running yet"
exit 1
fi
hint: |
The k3s kubeconfig file has not yet been created.
Run "limactl shell k3s sudo journalctl -u k3s" to check the log.
If that is still empty, check the bottom of the log at "/var/log/cloud-init-output.log".

limactl start should wait until all provision scripts complete (and report errors on failure) by default

@AkihiroSuda AkihiroSuda added the enhancement New feature or request label Sep 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant