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 creating an image using Packer and during provisioning I make sure that “PasswordAuthentication” is set to no. I verified that it is by printing the config during the provisioning process.
Now when I start a droplet from the created image I don’t supply any SSH keys (because those were already added as part of the provisioning). It seems that because of this the config of my custom image is altered to allow root login via the password that is sent to me via email.
When I inspect the /etc/ssh/sshd_config file I can find an entry
PasswordAuthentication yes
Is it correct that DigitalOcean is modifying my image after creation or am I doing something wrong? This is the command I used to create the droplet. Image ID is the actual Image ID.
doctl compute droplet create test --image "31405797" --region "ams3" --size "2gb" --wait
2528527458a540fba5c38cc921bb27
jhonnydepp12
Peter Alison
Arnold Hendriks
384d3f11289345379905a243f7b817
Laveenk16
Laveenk16
e8ab71f9e5914ffba3313f6ac33bb3
1c3ae38719bc49de9abf588e704583
lincoln
76ac182105344670910aa7c62ff2a3
c3d53dcb398b418288ff41b565183d