Guest8897 | Hello world | 18:46 |
---|---|---|
Guest8897 | How do I reset the cloud-init first boot tracker? I've built a custom AMI with Packer, and now when I deploy that AMI in AWS, the userdata I provide is ignored. I start that userdata file with `#! /bin/bash`. However I've noticed that If I prefix that with another line containing `#cloud-boothook` it will run my userdata on every boot. Which makes | 18:48 |
Guest8897 | sense, but it's not what I need. | 18:48 |
Guest8897 | I'm still digging through the docs to understand how cloud-init works, but so far I haven't found the answer to my question | 18:49 |
holmanb | Guest8897: Hello and welcome to the project! A couple of notes: I see a space between the "!" and "/" in your shebang line. If you copied that direct you'll probably want to fix that. Also, if you run `cloud-init clean --logs --reboot` it will remove artifacts and reboot with (and cloud-init will run as if it's the first time with the config). | 19:14 |
holmanb | s/with// | 19:16 |
henk | on https://cloudinit.readthedocs.io/en/latest/topics/modules.html#users-and-groups what does »Module frequency: per instance« mean? I understand "once-per-instance" and "always" but not what "per instance" could mean. is that explained anywhere in the docs? | 20:51 |
falcojr | henk: it means once-per-instance and an unfortunate inconsistency in our docs. It should be fixed in the next 2 weeks or so | 20:57 |
henk | falcojr: ah, I was hoping so, thanks | 21:09 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!