cloud-container adds the SSH_KEY env var into ~/.ssh/authorized_keys without a new line. In most flists, we do echo $SSH_KEY >> ~/.ssh/authorized_keys. Which causes the key ssh-rsa something to appear in the file as ssh-rsa somethingssh-rsa something which is invalid and prevents ssh access. When SSH_KEY is with the email after it, it appears as ssh-rsa something emailssh-rsa something email and it's recognized correctly.
But why does the cloud-container does this? it seems something the image should be handling. And if it does it would be convenient to add a new line so that existing images doesn't break.
cloud-container adds the
SSH_KEY
env var into~/.ssh/authorized_keys
without a new line. In most flists, we doecho $SSH_KEY >> ~/.ssh/authorized_keys
. Which causes the keyssh-rsa something
to appear in the file asssh-rsa somethingssh-rsa something
which is invalid and prevents ssh access. WhenSSH_KEY
is with the email after it, it appears asssh-rsa something emailssh-rsa something email
and it's recognized correctly.But why does the cloud-container does this? it seems something the image should be handling. And if it does it would be convenient to add a new line so that existing images doesn't break.