I am trying to install the Ruby Version Manager( RVM) on my CentOS 6.6 machine.
我正在尝试在CentOS 6.6机器上安装Ruby版本管理器(RVM)。
I followed the instructions on the home page at https://rvm.io/rvm/install
我遵循了https://rvm.io/rvm/install主页上的说明
When I run this command :
当我运行这个命令:
gpg --keyserver hkp://keys.gnupg.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3
I keep getting the error :
我一直在犯错误:
gpg: requesting key D39DC0E3 from hkp server keys.gnupg.net
gpgkeys: HTTP fetch error 6: Couldn't resolve host 'keys.gnupg.net'
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
Does anyone know how to resolve this?
有人知道怎么解决这个问题吗?
Thanks IS
由于是
6 个解决方案
#1
25
You can download the signature and import it manually.
您可以下载签名并手动导入它。
curl -#LO https://rvm.io/mpapis.asc
gpg --import mpapis.asc
And now install RVM. That should work
现在安装区。这应该工作
\curl -sSL https://get.rvm.io | bash
Note:
注意:
If you have a .gnupg
directory, remove it first.
如果您有.gnupg目录,请首先删除它。
rm -rf ~/.gnupg/
#2
2
The one at fault here is virtualbox
's dns proxy. The issue manifests itself only under vagrant
, because the latter enables it (dns proxy). By default it's disabled. So, one way to remedy it is to disable dns proxy (VBoxManage modifyvm ... --natdnsproxy off
). Or change 10.0.2.3
in /etc/resolv.conf
to your host's resolver IP address. And do gpg
again, while it didn't change. Or, do gpg --keyserver hkp://pool.sks-keyservers.net --recv-keys D39DC0E3
. Which succeeds for a reason I don't understand.
这里的问题是virtualbox的dns代理。这个问题只在流浪者状态下出现,因为后者支持它(dns代理)。在默认情况下是禁用的。因此,一种补救方法是禁用dns代理(VBoxManage modifyvm…)。——natdnsproxy掉)。或在/etc/resolv中更改10.0.2.3连接到主机的解析器IP地址。再做gpg,虽然它没有改变。或者,做gpg——keyserver hkp:/ pool.sk -keyservers.net——recv-keys D39DC0E3。它成功的原因我不明白。
#3
0
Try this
试试这个
gpg --keyserver 213.133.103.71 --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3
an IP instead of hkp://keys.gnupg.net
一个IP而不是hkp://keys.gnupg.net
#4
0
I recently came across this issue while trying to upgrade from docker to docker for Mac on one of our Ubuntu images for ruby.
最近我遇到了这个问题,我试图从docker升级到docker,让它在我们Ubuntu的一个Ubuntu映像上升级到ruby。
Here is my workaround:
这是我的解决方案:
gpg --keyserver $(getent hosts keys.gnupg.net | awk '{ print $1 }' | head -1) --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3
This resolved the issue and seemed to be the least hacky solution.
这解决了这个问题,似乎是最不陈腐的解决办法。
#5
0
It worked for me after I added google's DNS 8.8.8.8
in network settings.
当我在网络设置中添加了谷歌的DNS 8.8.8.8后,它对我起了作用。
#6
-1
The right workaround to this issue is:
解决这个问题的正确方法是:
gpg --keyserver $(ping keys.gnupg.net) --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3
#1
25
You can download the signature and import it manually.
您可以下载签名并手动导入它。
curl -#LO https://rvm.io/mpapis.asc
gpg --import mpapis.asc
And now install RVM. That should work
现在安装区。这应该工作
\curl -sSL https://get.rvm.io | bash
Note:
注意:
If you have a .gnupg
directory, remove it first.
如果您有.gnupg目录,请首先删除它。
rm -rf ~/.gnupg/
#2
2
The one at fault here is virtualbox
's dns proxy. The issue manifests itself only under vagrant
, because the latter enables it (dns proxy). By default it's disabled. So, one way to remedy it is to disable dns proxy (VBoxManage modifyvm ... --natdnsproxy off
). Or change 10.0.2.3
in /etc/resolv.conf
to your host's resolver IP address. And do gpg
again, while it didn't change. Or, do gpg --keyserver hkp://pool.sks-keyservers.net --recv-keys D39DC0E3
. Which succeeds for a reason I don't understand.
这里的问题是virtualbox的dns代理。这个问题只在流浪者状态下出现,因为后者支持它(dns代理)。在默认情况下是禁用的。因此,一种补救方法是禁用dns代理(VBoxManage modifyvm…)。——natdnsproxy掉)。或在/etc/resolv中更改10.0.2.3连接到主机的解析器IP地址。再做gpg,虽然它没有改变。或者,做gpg——keyserver hkp:/ pool.sk -keyservers.net——recv-keys D39DC0E3。它成功的原因我不明白。
#3
0
Try this
试试这个
gpg --keyserver 213.133.103.71 --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3
an IP instead of hkp://keys.gnupg.net
一个IP而不是hkp://keys.gnupg.net
#4
0
I recently came across this issue while trying to upgrade from docker to docker for Mac on one of our Ubuntu images for ruby.
最近我遇到了这个问题,我试图从docker升级到docker,让它在我们Ubuntu的一个Ubuntu映像上升级到ruby。
Here is my workaround:
这是我的解决方案:
gpg --keyserver $(getent hosts keys.gnupg.net | awk '{ print $1 }' | head -1) --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3
This resolved the issue and seemed to be the least hacky solution.
这解决了这个问题,似乎是最不陈腐的解决办法。
#5
0
It worked for me after I added google's DNS 8.8.8.8
in network settings.
当我在网络设置中添加了谷歌的DNS 8.8.8.8后,它对我起了作用。
#6
-1
The right workaround to this issue is:
解决这个问题的正确方法是:
gpg --keyserver $(ping keys.gnupg.net) --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3