[04:57] <nakilon> hello, I use the built-in cloud-init in GCP Chromium server; I've managed to make the server irresponsive, probably by binding the docker socket inside a docker container launched via docker-compose that was launched with that socket binded also...
[04:58] <nakilon> so the dick went spinning like mad and ssh didn't work anymore, even serial console was hanging so I rebooted it now, but my init script failed -- I see in logs that it exited with 1 but there is nothing useful in it, probably because I need to add -x to the shebang
[05:00] <nakilon> anyway I did the 'sudo cloud-init clean', 'sudo cloud-init init' and now logs don't show any error or python backtrace but it does not looks like anything ran -- is adding shebang now and rerunning these two commands a way to debug the thing?
[05:04] <nakilon> looks like commands rewrote the /var/lib/cloud/scripts/per-boot/all.sh but didn't run it
[05:05] <nakilon> I forgot how to do this all, I've configured it on 1st of Aug
[05:21] <nakilon> docs mention "Each cloud-config module has a module FREQUENCY configured: PER_INSTANCE, PER_BOOT, PER_ONCE or PER_ALWAYS. " but I don't see any docs about PER_ALWAYS  
[05:26] <nakilon> also docs say "$ sudo cloud-init single --name cc_ssh --frequency always" but I don't understand what should I put instead of cc_ssh for my need
[05:33] <nakilon> oh, probably cc_scripts_per_boot
[20:10] <raccct> hi - is it possible to fully configure a LAMP webserver via cloud-init?