You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating a new vagrant box, vagrant up doesn't complete because the ssh key cannot be updated. This is a result of ~vagrant/.ssh/authorized_keys being owned by root:root
Software Version
Vagrant 2.4.1 on macOS 14.4.1
Replication Case
vagrant init bento/oracle-9.3-arm64
vagrant up
Stacktrace
```
```
Possible Solution
If ~vagrant/.ssh and ~vagrant/.ssh/authorized_keys are owned by vagrant:vagrant, this shouldn't be an issue.
The text was updated successfully, but these errors were encountered:
have you tested the arm version of bento/oracle-9 or bento/oracle-9.4? The bento/ *-arm64 boxes are deprecated now that vagrant and kitchen-vagrant support the -arch flag when spinning up nodes.
Using just bento/oracle-9 (even bento-oracle-9.3) worked as expected. I did not realize that the -arm64 boxes were deprecated. I'll close the issue, thanks for the update and information.
Describe the problem
When creating a new vagrant box, vagrant up doesn't complete because the ssh key cannot be updated. This is a result of ~vagrant/.ssh/authorized_keys being owned by root:root
Software Version
Vagrant 2.4.1 on macOS 14.4.1
Replication Case
vagrant init bento/oracle-9.3-arm64
vagrant up
Stacktrace
Possible Solution
If ~vagrant/.ssh and ~vagrant/.ssh/authorized_keys are owned by vagrant:vagrant, this shouldn't be an issue.
The text was updated successfully, but these errors were encountered: