CoreOS forgets authorized_keys

  • Posted on November 13, 2014
  • fvhemertAsked by fvhemert

I have one working ssh key for CoreOS, created when creating the droplet. When I add a key via the web interface, it does not work, it is not added to authorized_keys . When I manually add a key to ~/.ssh/authorized_keys it works until a reboot, then the key is removed. How can I prevent this?

Edit: And how can I type an underscore without it making words italic?

Submit an answer

This textbox defaults to using Markdown to format your answer.

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

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

On CoreOS, ~/.ssh/authorized_keys is an auto generated file by the update-ssh-keys command. In order to add a new key without it getting clobbered on reboot, you can do something like:

echo 'ssh-rsa AAAAB3Nza.......  key@host' | update-ssh-keys -a core