Ben Cressey

In general where I'd hesitate would be if the feature would require calling other, non-EBS APIs. However, it looks like the StartSnapshot API supports passing a list of tags, so...

Maybe either of these: ``` --tag foo --tag bar,baz --tag Key=foo Key=bar,Value=baz ``` With a preference for the first form, if commas aren't a valid character.

Since `coldsnap` is one of the projects supported by the Bottlerocket team at AWS, you're also welcome to show up at the [Bottlerocket community meeting](https://www.meetup.com/bottlerocket-community/events/) to chat about `coldsnap` usage...

If the container layer fails to unpack because the filesystem is out of space, I suppose that could leave zero-sized files around. I'm surprised that this wouldn't bubble up as...

> Decoupling the decision to reboot and actually rebooting via a marker file was motivated by the idea a bootstrap container might find other reasons to request a reboot before...

> There likewise could be a `/usr/bin/bootstrap-containers reboot-if-required`, checking e.g. a marker file that is local to a particular bootstrap container. Nice! I really like this idea.

@KevinCiz - from the admin container you can run `sudo sheltie` to drop into a shell on the host and access those paths. (This only works with `superpowered = true`...

`apiclient get` is another useful troubleshooting command that will dump all the configured settings, to see if something isn't being set on launch as expected.

I don't feel as strongly about "only one" but I definitely don't want to add `clap` to the binaries shipped in the OS image, and would prefer that the mix...

I sketched out a possible approach in https://github.com/bottlerocket-os/bottlerocket/issues/2218#issuecomment-1186045512 and https://github.com/bottlerocket-os/bottlerocket/issues/2218#issuecomment-1186084117. The proposal is to add a new kind of host container - config containers - that will be run whenever...