Linux 无法在Windows下运行Laravel Homestead（grep错误）

我应该提前指出，我基本上不懂Linux——我是一个Windows用户，我想尝试一下Hack语言，这似乎是启动和运行的最快方式

我紧随其后，甚至尝试启动配置的映像

当我运行homestead up或homestead provision时，它会失败，并显示相同的错误消息：

Rasmus Schultz@SIDEWINDER-7240 ~ $ homestead provision ==> default: Running provisioner: file... ==> default: Running provisioner: shell... default: Running: inline script ==> default: grep: unrecognized option '---- BEGIN SSH2 PUBLIC KEY ---- ==> default: Comment: "RasmusHomestead" ==> default: AAAAB3NzaC1yc2EAAAABJQAAAQEAhJ4eUnXFP7dCX98KtqNoZI9WwkE0+EBfuggt ...snip... ==> default: bVlGxJAHJd6u0vW9fssohiaUuo+8i48zHn8Ciqs5XVAn79m/PQ== ==> default: ---- END SSH2 PUBLIC KEY ---- ==> default: ' ==> default: Usage: grep [OPTION]... PATTERN [FILE]... ==> default: Try 'grep --help' for more information. ==> default: ---- BEGIN SSH2 PUBLIC KEY ---- Comment: "RasmusHomestead" AAAAB3NzaC1yc2EAAAABJQAAAQEAhJ4eUnXFP7dCX98KtqNoZI9WwkE0+EBfuggt ...snip... bVlGxJAHJd6u0vW9fssohiaUuo+8i48zHn8Ciqs5XVAn79m/PQ== ---- END SSH2 PUBLIC KEY ---- ==> default: Running provisioner: shell... default: Running: inline script ==> default: /tmp/vagrant-shell: line 1: /home/vagrant/.ssh/$2: ambiguous redirect The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong. 这个grep错误看起来像是一个内部问题，当它被设置时发生在盒子内部-好像发出的grep命令是无效的

有什么好处

更新：

好的，第一个问题已经解决了-它希望使用不同的密钥格式，但这并没有修复不明确的重定向错误消息。。。假设我必须重新准备？我关了流浪汉又重新开始，运气不好

$ homestead provision ==> default: Running provisioner: file... ==> default: Running provisioner: shell... default: Running: inline script ==> default: Running provisioner: shell... default: Running: inline script ==> default: /tmp/vagrant-shell: line 1: /home/vagrant/.ssh/$2: ambiguous redirect The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong.

---

grep错误是因为它不喜欢用于公钥的默认putty格式。您需要将其重新保存为OpenSSH密钥

这可以通过在Putty key Generator中重新打开私钥文件，然后将顶部标记的公钥中的公钥复制/粘贴到OpenSSH authorized_keys文件中，并将其粘贴到新的或现有的密钥文件中来实现

---

如果选择a将其另存为新文件，则需要调整homestead配置文件中的路径。

生成SSH密钥时，您是像视频一样使用SSH密钥，还是使用Putty的密钥或其他应用程序？我已经有了以前使用Putty生成的密钥对。这不对吗？它在其他任何地方都可以工作。它不喜欢密钥的特定格式，而是想要OpenSSH格式。我以前遇到过这个问题，我在puttygen中使用了导出OpenSSH密钥选项。它看起来与我刚才使用ssh-keygen生成的密钥完全不同，但是这次我确实成功地启动了这个盒子，它现在响应ping，但在端口80上没有响应，并且它没有修复不明确的重定向错误。威尔在上面更新和发布…是的，在看到我的评论之前我不得不这么做，但关键格式仍然不是Homestead所期望的-它似乎不喜欢换行符。我生成了新的密钥，它工作正常，但我仍然收到相同的错误消息，请参阅上面的更新帖子。 --- ip: "192.168.10.10" memory: 2048 cpus: 1 provider: virtualbox authorize: C:\Users\Rasmus Schultz\.ssh\RasmusHomestead.pub keys: - C:\Users\Rasmus Schultz\.ssh\RasmusHomestead folders: - map: C:\workspace to: /home/vagrant/Code sites: - map: test.dev to: /home/vagrant/Code/test hhvm: true databases: - homestead variables: - key: APP_ENV value: local $ homestead provision ==> default: Running provisioner: file... ==> default: Running provisioner: shell... default: Running: inline script ==> default: Running provisioner: shell... default: Running: inline script ==> default: /tmp/vagrant-shell: line 1: /home/vagrant/.ssh/$2: ambiguous redirect The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong.