Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I’m trying to use a cloud-config.yml file to automatically configure a few basic tasks when I provision a new droplet, currently though only some steps work, others partly work, and others fail completely and looking at /var/log/clioud-init.log and /var/log/cloud-init-output.log I’m not really sure why it’s failing.
#cloud-config
packages:
- zsh
- vim-enhanced
users:
- name: jsmith
groups: wheel
shell: /usr/bin/zsh
sudo: ['ALL=(ALL) NOPASSWD:ALL']
ssh_authorized_keys:
- (my ssh key)
chpasswd:
list: |
jsmith:(password sanitized)
expire: False
write_files:
- path: /home/jsmith/.my.cnf
owner: "jsmith:jsmith"
permissions: 0400
content: |
[client]
user=root
password=''
runcmd:
- [ sed, -i, -e, 's/#PermitRootLogin yes/PermitRootLogin no/g', /etc/ssh/sshd_config ]
- systemctl restart sshd
For the above script only the users section runs fully, so I have a user account created trying to use a shell that failed to get installed for it login shell, I can not tell if the chpasswd failed or not as I can’t login due to ZSH failing to get installed by cloud-init. The write_files command partly works, the only thing that fails is it fails to correctly chown the file after creation (probably due to how it’s quoted?). The runcmd hook the sed command does fail, but I’m not sure if the systemcl call failed (I could have checked it’s logs to see if it was restarted but kind of lower priority to the other things).
Anyone with more experience with working with cloud-config know what I’m doing wrong or what’s going on?
58a301358aa344a792e7b70f6a1ed5
Faisol Bello
Serhii Meleshchenko Miratechgroup
24230eeb31a542b58d79c0715000b8
biomechanico
eddiew
RhumSite
Daniel Olshansky
bb17b733a0984acfbc8d8b875c209d