gpt4 book ai didi

SSH 转发不适用于 vagrant

转载 作者:行者123 更新时间:2023-12-02 14:34:20 24 4
gpt4 key购买 nike

我按照 here 的描述设置了 Vagrant 1.8.1 的 ssh 参数

很快,我得到了主机 ssh 配置文件:

Host bitbucket.org
Hostname bitbucket.org
IdentityFile ~/.ssh/id_bitbucket
User zuba
ForwardAgent yes

在 Vagrant 文件中:
config.ssh.forward_agent = true

在主机上 ssh-add -L 显示 key ,而在 vagrant box 上它报告代理没有身份并且 git clone 由于身份验证失败而失败

如何解决这个问题?

更新 1:
vagrant ssh -c 'ssh-add -l'显示关键
> vagrant ssh-config
Host p4
HostName 127.0.0.1
User vagrant
Port 2222
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
PasswordAuthentication no
IdentityFile /home/zuba/.vagrant.d/insecure_private_key
IdentitiesOnly yes
LogLevel FATAL
ForwardAgent yes

更新 2:

发现没有答案的重复帖子 vagrant ssh agent forwarding only works for inline commands?

更新 3:

这是我的 Vagrant 文件:

Vagrant.configure("2") do |config|

boxes = {
"p4" => "10.2.2.15",
}

boxes.each do |box_name, box_ip|
config.vm.define box_name do |config|
config.vm.box = "trusty-64"
config.vm.box_url = "https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box"
config.vm.hostname = "p4"
config.vm.network :private_network, ip: box_ip
config.vm.network "forwarded_port", guest: 3000, host: 3000
config.vm.network "forwarded_port", guest: 3001, host: 3001
config.vm.network "forwarded_port", guest: 3002, host: 3002
config.vm.network "forwarded_port", guest: 3003, host: 3003
config.vm.network "forwarded_port", guest: 6379, host: 6379 # Redis

config.vm.provider "virtualbox" do |vb|
vb.gui = false
vb.name = "p4"

# Use VBoxManage to customize the VM. For example to change memory:
vb.customize ["modifyvm", :id, "--memory", "1024"]
end

config.vm.synced_folder "../..", "/home/vagrant/my_src"
config.ssh.forward_agent = true # to use host keys added to agent

# provisioning
config.vm.provision :shell, :inline => "sudo apt-get update"

config.vm.provision "chef_solo" do |chef|
chef.log_level = "info"
chef.environment = "development"
chef.environments_path = "environments"
chef.cookbooks_path = ["cookbooks", "site-cookbooks"]
chef.roles_path = "roles"
chef.data_bags_path = "data_bags"
chef.json.merge!(JSON.parse(IO.read("nodes/#{box_ip}.json")))
end

config.exec.commands '*', directory: '/home/vagrant'
config.exec.commands 'apt-get', prepend: 'sudo'
config.exec.commands %w[rails rspec rake], prepend: 'bundle exec'
end
end
end

最佳答案

终于找到了that post这帮助我弄清楚是什么阻止了 vagrant 使用代理 key 。

ssh-add一键通 GNU 屏幕 session , 同时做 vagrant ssh在另一个屏幕 session 中。这就是为什么 ssh-agent 对 Vagrant 来说有点“无法访问”的原因。

当我在同一个屏幕 session 中添加 key 和 ssh-ed vagrat 时,一切都开始工作了

关于SSH 转发不适用于 vagrant,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/35323101/

24 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com