想了解在certs/x509_certificate_list需要时编译linux内核时没有制定目标的规则停止的新动态吗？本文将为您提供详细的信息，此外，我们还将为您介绍关于Azureweb角色–指向

想了解在 certs/x509_certificate_list 需要时编译 linux 内核时没有制定目标的规则停止的新动态吗？本文将为您提供详细的信息，此外，我们还将为您介绍关于Azure web角色 – 指向单个端点的多个ssl certs、docker-machine regenerate-certs 问题、EasyWSL工具将 Linux Docker 映像转换为适用于 Linux 的、error setting certificate verify locations: CAfile: e:/Program Files/Git/mingw64/ssl/certs/ca-bundle的新知识。

• 在 certs/x509_certificate_list 需要时编译 linux 内核时没有制定目标的规则停止
• Azure web角色 – 指向单个端点的多个ssl certs
• docker-machine regenerate-certs 问题
• EasyWSL工具将 Linux Docker 映像转换为适用于 Linux 的
• error setting certificate verify locations: CAfile: e:/Program Files/Git/mingw64/ssl/certs/ca-bundle

在 certs/x509_certificate_list 需要时编译 linux 内核时没有制定目标的规则停止

如何解决在 certs/x509_certificate_list 需要时编译 linux 内核时没有制定目标的规则停止

我正在尝试编译内核（以前没有这样做过）我收到如下屏幕截图中的错误

我没有验证内核（没有验证签名）它从 kernel.org 下载的 Linux 5.10.33 版本。这个内核还有一个签名。

我想知道如何解决这个错误。

如果发生这种情况是因为我没有验证签名，那么想知道

-> 如何跳过签名检查并继续编译内核到最后并获得最终输出文件，以便我可以安装它（linux 5.10.33）

-> 如何验证签名并能够解决此错误并编译内核

Azure web角色 – 指向单个端点的多个ssl certs

<Certificates>
   <Certificate name="service.foo.net" storeLocation="LocalMachine" storeName="My" />
   <Certificate name="service.doo.net" storeLocation="LocalMachine" storeName="My" />
  </Certificates>
  <Endpoints>
   <InputEndpoint name="HttpsIn" protocol="https" port="443" certificate="service.foo.net" />
  </Endpoints>

docker-machine regenerate-certs 问题

系统环境：
win10 + virtualbox5.0.24
docker,docker-machine 版本

JYC103@Fanne MINGW64 ~
$ docker-machine.exe -version
docker-machine.exe version 0.7.0, build a650a40

JYC103@Fanne MINGW64 ~
$ docker version
Client:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 23:54:00 2016
 OS/Arch:      windows/amd64
An error occurred trying to connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/version: open //./pipe/docker_engine: The system cannot find the file specified.

现在 docker-machine 上有一台 docker 主机

$ docker-machine.exe ls
NAME            ACTIVE   DRIVER      STATE     URL                         SWARM   DOCKER    ERRORS
docker.20.127   -        none        Running   tcp://192.168.20.127:2375           Unknown   Unable to query docker version: Unable to read TLS config: open C:\Users\JYC103\.docker\machine\machines\docker.20.127\server.pem: The system cannot find the file specified.

直接 docker info 这台 docker 主机

$ docker -H 192.168.20.127:2375 info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 1.12.0
Storage Driver: devicemapper
 Pool Name: docker-253:1-101251423-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 11.73 MB
 Data Space Total: 107.4 GB
 Data Space Available: 14.84 GB
 Metadata Space Used: 581.6 kB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.147 GB
 Thin Pool Minimum Free Space: 10.74 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.107-RHEL7 (2016-06-09)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host bridge overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 3.10.0-123.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 987.2 MiB
Name: localhost.localdomain
ID: FMPB:NCHQ:ERTQ:YQMK:WUSA:QA2T:FCQO:TL7L:IHOH:3Z3Z:EXTV:3YMY
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Insecure Registries:
 127.0.0.0/8

问题开始了现在要 docker-machine env 查看一下 docke.20.127 主机的变量，出现以下提示

$ docker-machine.exe env docker.20.127
Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.20.127:2375": open C:\Users\JYC103\.docker\machine\machines\docker.20.127\server.pem: The system cannot find the file specified.
You can attempt to regenerate them using ''docker-machine regenerate-certs [name]''.
Be advised that this will trigger a Docker daemon restart which will stop running containers.

server.pem 不存在，按照它的提示创建一个

$ docker-machine.exe regenerate-certs docker.20.127
Regenerate TLS machine certs?  Warning: this is irreversible. (y/n): y
Regenerating TLS certificates
Waiting for SSH to be available...
Too many retries waiting for SSH to be available.  Last error: Maximum number of retries (60) exceeded

但是等了几分钟后，没创建成功，打开 debug 调试

$ docker-machine.exe -D regenerate-certs docker.20.127
Docker Machine Version:  0.7.0, build a650a40
Regenerate TLS machine certs?  Warning: this is irreversible. (y/n): y
Regenerating TLS certificates
Found binary path at C:\Users\JYC103\bin\docker-machine.exe
Launching plugin server for driver none
Plugin server listening at address 127.0.0.1:58959
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
command=configureAuth machine=docker.20.127
Waiting for SSH to be available...
Getting to WaitForSSH function...
(docker.20.127) Calling .GetSSHHostname
(docker.20.127) Calling .GetSSHPort
(docker.20.127) Calling .GetSSHKeyPath
(docker.20.127) Calling .GetSSHUsername
Using SSH client type: external
&{[-F /dev/null -o BatchMode=yes -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none @ -p 0] C:\Program Files\Git\usr\bin\ssh.exe <nil>}
About to run SSH command:
exit 0
SSH cmd err, output: exit status 255: usage: ssh [-1246AaCfGgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec]
           [-D [bind_address:]port] [-E log_file] [-e escape_char]
           [-F configfile] [-I pkcs11] [-i identity_file]
           [-L address] [-l login_name] [-m mac_spec]
           [-O ctl_cmd] [-o option] [-p port]
           [-Q cipher | cipher-auth | mac | kex | key]
           [-R address] [-S ctl_path] [-W host:port]
           [-w local_tun[:remote_tun]] [user@]hostname [command]

Error getting ssh command ''exit 0'' : Something went wrong running an SSH command!
command : exit 0
err     : exit status 255
output  : usage: ssh [-1246AaCfGgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec]
           [-D [bind_address:]port] [-E log_file] [-e escape_char]
           [-F configfile] [-I pkcs11] [-i identity_file]
           [-L address] [-l login_name] [-m mac_spec]
           [-O ctl_cmd] [-o option] [-p port]
           [-Q cipher | cipher-auth | mac | kex | key]
           [-R address] [-S ctl_path] [-W host:port]
           [-w local_tun[:remote_tun]] [user@]hostname [command]

报 ssh 链接错误。这问题要如何解决，要如何才能生成 server.pem 这个文件的？

EasyWSL工具将 Linux Docker 映像转换为适用于 Linux 的

适用于 Linux 的 Windows 子系统允许管理员直接从 Windows 访问基于 Linux 的工具，但并非每个 Linux 发行版都可以通过 Microsoft Store 获得。

现在有一个名为 EasyWSL 的新工具可以将几乎任何 Linux Docker 映像转换为 WSL 发行版。

EasyWSL 由网络安全公司 Red Code Labs 创建。

“我觉得我们可以通过 WSL 以某种方式将更多的 Linux 灵魂带入 Windows，这比微软在他们的商店中提供的更多，” Red Code Labs 解释道。

EasyWSL 在从 Microsoft Store 获取图像方面也具有一些优势，因为这些图像通常由 3rd 方提供，因此可能已被更改。

“基本上，一开始尝试使用 Arch 和 Gentoo 及其存储库是一个好主意，但后来我意识到，为什么不以某种方式从 Docker Hub 获取图像，以扩大可能性。”

WSL 用户现在可以直接从原始维护者那里下载 Docker 镜像，并且知道构建没有以任何方式改变。

EasyWSL 是一个开源工具。

error setting certificate verify locations: CAfile: e:/Program Files/Git/mingw64/ssl/certs/ca-bundle