Help with cloud init syntax for runcmd

  • Posted October 22, 2014

I’m just getting started with cloud-config etc for setting up a droplet, and I’m just running into a slight issue with running commands.

I’m trying to run some commands which have characters that upset the YAML parser, for instance:

  - \curl -sSL | bash -s stable

The cloud init logs are giving me an error for runcmd, I’m assuming because it’s incorrectly parsing characters like “:” etc.

What is the correct way to specify this kind of command? Can I just put quotes around part of it, or should I escape the special characters somehow?



Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

The documentation is a bit lacking, but from the comments on the example in the upstream docs you learn:

# runcmd contains a list of either lists or a string
# each item will be executed in order at rc.local like level with
# output to the console
# - if the item is a list, the items will be properly executed as if
#   passed to execve(3) (with the first arg as the command).
# - if the item is a string, it will be simply written to the file and
#   will be interpreted by 'sh'
# Note, that the list has to be proper yaml, so you have to escape
# any characters yaml would eat (':' can be problematic)

So wrapping everything in single quotes seems like it should do the trick:

 - '\curl -sSL | bash -s stable'

The resulting script can be found for debugging purposes in /var/lib/cloud/instance/scripts/runcmd