Connection lost
Trying to reconnect…
Server didn't respond
Recovering…
cloud-init operations
v0.1.3cloud-init introspection + boot diagnostics + stage re-runs. Use when an EC2/GCE/Azure VM finishes booting but the workload didn't come up the way it should: check overall status, blame slow modules, dump user-data / cloud-config / vendor-data as the instance actually saw them, tail the cloud-init logs, and (with operator approval) re-run individual modules or the full init pipeline.
Install
emisar pack install
validates the pack and verifies its content hash before copying it into /etc/emisar/packs.
The --hash
below pins the
install to the exact bytes on this page — a tampered copy is rejected. After
install, reload the runner; it re-reads the catalog and advertises every action.
content hash: sha256:ab60a913fe7c4bae1fdbc169f99e97562f64b689d73cb6369c8546b423fcb2f8
sudo emisar pack install cloud-init \ --hash sha256:ab60a913fe7c4bae1fdbc169f99e97562f64b689d73cb6369c8546b423fcb2f8 \ --dest /etc/emisar/packs # Reload so the runner re-reads the catalog: sudo systemctl reload emisar
Actions 23 total
View on GitHub-
cloud-init analyze blame
-
cloud-init analyze dump
-
cloud-init analyze show
-
cloud-init clean
-
cloud-init clean --logs
-
cat /var/lib/cloud/instance/cloud-config.txt
-
cloud-init collect-logs
-
cloud-init init
-
cloud-init init --local
-
cat /var/lib/cloud/data/instance-id
-
journalctl -u cloud-init -n <lines>
-
tail /var/log/cloud-init.log
-
cloud-init modules --mode=config
-
cloud-init modules --mode=final
-
tail /var/log/cloud-init-output.log
-
cloud-init query <key>
-
cloud-init schema --system
-
cloud-init single --name=<module>
-
cloud-init status
-
cloud-init status --long [--wait]
-
cat /var/lib/cloud/instance/user-data.txt
-
cat /var/lib/cloud/instance/vendor-data.txt
-
cloud-init --version