This page introduces you to gRPC and protocol buffers. gRPC can use protocol buffers as both its Interface Definition Language (IDL) and as its underlying message interchange format.
wget https://github.com/etcd-io/etcd/releases/download/v3.4.13/etcd-v3.4.13-linux-amd64.tar.gz tar -xvf etcd-v3.4.13-linux-amd64.tar.gz &&\ cd etcd-v3.4.13-linux-amd64 &&\ sudocp -a etcd etcdctl /usr/bin/
[root@MiWiFi-R4CM-srv apisix-2.10.3]# LUAROCKS_SERVER=https://luarocks.cn make deps /bin/bash: luarocks: command not found WARN: You're not using LuaRocks 3.x, please add the following items to your LuaRocks config file: variables ={ OPENSSL_LIBDIR=/usr/local/openresty/openssl111/lib OPENSSL_INCDIR=/usr/local/openresty/openssl111/include } luarocks install rockspec/apisix-master-0.rockspec --tree=deps --only-deps --local --server https://luarocks.cn /bin/bash: luarocks: command not found make: *** [deps] Error 127 [root@MiWiFi-R4CM-srv apisix-2.10.3]# ^C
[root@MiWiFi-R4CM-srv apisix-2.10.3]# LUAROCKS_SERVER=https://luarocks.cn make deps
爆出问题
分析问题：
[root@MiWiFi-R4CM-srv apisix-2.10.3]# LUAROCKS_SERVER=https://luarocks.cn make deps ………………………………………………………………………………………………………………………………………………………………………… lua-resty-dns-client 5.2.0-1 depends on luaxxhash >=1.0(not installed) Installing https://luarocks.cn/luaxxhash-1.0.0-1.rockspec Error: Failed installing dependency: https://luarocks.cn/lua-resty-dns-client-5.2.0-1.src.rock - Failed installing dependency: https://luarocks.cn/luaxxhash-1.0.0-1.rockspec - 'git' program not found. Make sure Git is installed and is available in your PATH(or you may want to edit the 'variables.GIT' value infile'/root/.luarocks/config-5.1.lua') make: *** [deps] Error 1 [root@MiWiFi-R4CM-srv apisix-2.10.3]# yum install -y git
很明显就是没有安装配置好git嘛
lua-resty-dns-client 5.2.0-1 depends on lua >=5.1, <5.4(5.1-1 provided by VM) lua-resty-dns-client 5.2.0-1 depends on penlight ~>1(1.12.0-1 installed) lua-resty-dns-client 5.2.0-1 depends on lrandom (20180729-1 installed) lua-resty-dns-client 5.2.0-1 depends on lua-resty-timer ~>1(1.1.0-1 installed) lua-resty-dns-client 5.2.0-1 depends on binaryheap >=0.4(0.4-1 installed) lua-resty-dns-client 5.2.0-1 depends on luaxxhash >=1.0(not installed) Installing https://luarocks.cn/luaxxhash-1.0.0-1.rockspec Cloning into 'luaxxhash'... error: RPC failed;result=35, HTTP code =0 fatal: The remote end hung up unexpectedly Error: Failed installing dependency: https://luarocks.cn/lua-resty-dns-client-5.2.0-1.src.rock - Failed installing dependency: https://luarocks.cn/luaxxhash-1.0.0-1.rockspec - Failed cloning git repository. make: *** [deps] Error 1 [root@MiWiFi-R4CM-srv apisix-2.10.3]# ls apisix bin CHANGELOG.md CODE_OF_CONDUCT.md CODE_STYLE.md conf CONTRIBUTING.md deps LICENSE Makefile NOTICE powered-by.md README.md rockspec v3.8.0.tar.gz v3.8.0.tar.gz.1 [root@MiWiFi-R4CM-srv apisix-2.10.3]# [root@MiWiFi-R4CM-srv apisix-2.10.3]# cd .. [root@MiWiFi-R4CM-srv api7]# ls apache-apisix-2.10.3-src.tgz apisix-2.10.3 [root@MiWiFi-R4CM-srv api7]# git clone git@github.com:Chever-John/JohnChever-Blog.git Cloning into 'JohnChever-Blog'... The authenticity of host'github.com (20.205.243.166)' can't be established. ECDSA key fingerprint is SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM. ECDSA key fingerprint is MD5:7b:99:81:1e:4c:91:a5:0d:5a:2e:2e:80:13:3f:24:ca. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'github.com,20.205.243.166' (ECDSA) to the list of known hosts. Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. [root@MiWiFi-R4CM-srv api7]# git clone git@github.com:Chever-John/JohnChever-Blog.git Cloning into 'JohnChever-Blog'... Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. [root@MiWiFi-R4CM-srv api7]# git config --global user.name "CheverJohn" [root@MiWiFi-R4CM-srv api7]# git config --global user.email "cheverjonathan@gmail.com" [root@MiWiFi-R4CM-srv api7]# git config --list user.name=CheverJohn user.email=cheverjonathan@gmail.com [root@MiWiFi-R4CM-srv api7]# ssh-keygen -t rsa -C "cheverjonathan@gmail.com" Generating public/private rsa key pair. Enter file in which to save the key (/root/.ssh/id_rsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /root/.ssh/id_rsa. Your public key has been saved in /root/.ssh/id_rsa.pub. The key fingerprint is: SHA256:XVvMrYv9c92MVJm8CMUmZA44WgYv+atEOydMkpWc0I8 cheverjonathan@gmail.com The key's randomart image is: +---[RSA 2048]----+ |.......o. | | o.== +. * .| | B*.. .== +| | oEo. . o o =.| | o o .S . o o..| |=.. +.o | | * o ..ooo| |.= .o=| |. +| +----[SHA256]-----+ [root@MiWiFi-R4CM-srv api7]# cat /root/.ssh cat: /root/.ssh: Is a directory [root@MiWiFi-R4CM-srv api7]# ls apache-apisix-2.10.3-src.tgz apisix-2.10.3 [root@MiWiFi-R4CM-srv api7]# cd /root/.ssh [root@MiWiFi-R4CM-srv .ssh]# ls id_rsa id_rsa.pub known_hosts [root@MiWiFi-R4CM-srv .ssh]# cat id_rsa.pub 接下来显示就是生成的ssh密钥了，将其复制到github上的ssh里即可
When you install Workstation Pro on a Windows or Linux host system, a bridged network (VMnet0) is set up for you. Bridged networking connects a virtual machine to a network by using the network adapter on the host system. If the host system is on a network, bridged networking is often the easiest way to give the virtual machine access to that network.
With bridged networking, the virtual network adapter in the virtual machine connects to a physical network adapter in the host system. The host network adapter enables the virtual machine to connect to the LAN that the host system uses. Bridged networking works with both wired and wireless host network adapters.
Bridged networking configures the virtual machine as a unique identity on the network, separate from and unrelated to the host system. The virtual machine is a full participant in the network. It has access to other machines on the network, and other machines on the network can contact it as if it were a physical computer on the network.
You can view and change the settings for bridged networking on the host system, determine which network adapters to use for bridged networking, and map specific host network adapters to specific virtual switches.
A virtual machine must have its own identity on a bridged network. For example, on a TCPIP network, the virtual machine needs its own IP address. Your network administrator can tell you whether IP addresses are available for virtual machines and which networking settings to use in the guest operating system.
When you install Workstation Pro on a Windows or Linux host system, a bridged network (VMnet0) is set up for you. If you install Workstation Pro on a host system that has multiple network adapters, you can configure multiple bridged networks.
By default, VMnet0 is set to use auto-bridging mode and is configured to bridge to all active network adapters on the host system. You can use the virtual network editor to change VMnet0 to bridge to one specific host network adapter, or restrict the host network adapters that VMnet0 auto-bridges to. The changes you make affect all virtual machines that use bridged networking on the host system.[了解更多内容]
When you install Workstation Pro on a Windows or Linux host system, a NAT network (VMnet8) is set up for you. When you use the New Virtual Machine wizard to create a typical virtual machine, the wizard configures the virtual machine to use the default NAT network.
With NAT, a virtual machine does not have its own IP address on the external network. Instead, a separate private network is set up on the host system. In the default configuration, virtual machines get an address on this private network from the virtual DHCP server.
The virtual machine and the host system share a single network identity that is not visible on the external network. NAT works by translating the IP addresses of virtual machines in the private network to the IP address of the host system. When a virtual machine sends a request to access a network resource, it appears to the network resource as if the request is coming from the host system.
The host system has a virtual network adapter on the NAT network. This adapter enables the host system and virtual machines to communicate with each other. The NAT device passes network data between one or more virtual machines and the external network, identifies incoming data packets intended for each virtual machine, and sends them to the correct destination.
If you use NAT networking in a Windows virtual machine running on a Windows host system, you can use NetLogon to log in to a Windows domain from the virtual machine and access file shares that the WINS server knows.[了解更多内容]
If a virtual machine that uses NAT attempts to connect to a server that requires the client to use a source port below 1024, the NAT device must forward the request from a port below 1024. For security reasons, some servers accept connections only from source ports below 1024.[了解更多内容]
When you install Workstation Pro on a Windows or Linux host system, a host-only network (VMnet1) is set up for you. Host-only networking is useful if you need to set up an isolated virtual network. In a host-only network, the virtual machine and the host virtual network adapter are connected to a private Ethernet network. The network is completely contained within the host system.
The network connection between the virtual machine and the host system is provided by a virtual network adapter that is visible on the host operating system. The virtual DHCP server provides IP addresses on the host-only network.
In the default configuration, a virtual machine in a host-only network cannot connect to the Internet. If you install the proper routing or proxy software on the host system, you can establish a connection between the host virtual network adapter and a physical network adapter on the host system to connect the virtual machine to a Token Ring or other non-Ethernet network.
On a Windows host computer, you can use host-only networking in combination with the Internet Connection Sharing feature in Windows to allow a virtual machine to use the dial-up networking adapter or other connection to the Internet on the host system. See Microsoft documentation for information on configuring Internet Connection Sharing.
When you install Workstation Pro on a Windows or Linux host system, a host-only network (VMnet1) is set up for you. You might want to configure multiple host-only networks to manage network traffic between virtual machines in specific ways. [了解更多内容]
You can configure host-only networking for an existing virtual machine. You can connect a virtual network adapter to the default host-only network (VMnet1) or to a custom host-only network. If a virtual machine has two virtual network adapters, you can connect it to two host-only networks. [了解更多内容]
If you are setting up a complex test network that uses virtual machines, you might want to have two independent host-only networks with a router between them. [了解更多内容]
Each host-only network should be confined to the host system on which it is set up. Packets that virtual machines send on this network should not leak out to a physical network attached to the host system. Packet leakage can occur only if a machine actively forwards packets.[了解更多内容]
A host-only network has a network interface associated with it (vmnet1) that is marked up when the host operating system is booted. Routing server processes that operate on the host operating system automatically discover the host-only network and propagate information on how to reach the network, unless you explicitly configure them not to do so.[了解更多内容]
The virtual DHCP server in Workstation Pro cannot update a DNS server by using a Dynamic Domain Name Service (DDNS). For this reason, you should use DHCP to supply IP addresses as well as other information, such as the identity of a host running a name server and the nearest router or gateway. [了解更多内容]
“工作站专业版”中的虚拟DHCP服务器无法通过DDNS (Dynamic Domain Name Service)更新DNS服务器。由于这个原因，您应该使用DHCP来提供IP地址以及其他信息，例如运行名称服务器的主机的标识以及最近的路由器或网关。
