Hostname/IP doesn't match certificate's altnames

背景

一直用Docker Toolbox on VirtualBox在Windows上开发,创建的boot2docker镜像IP地址是192.168.99.100。
这两天因为工作需要,想装一个minikube。安装的时候没有启动Docker Toolbox,结果minikube也会创建一个VirtualBox虚拟机,然后还把192.168.99.100的IP地址给占了。
果然,打开Kitematic,启动到99%的时候,提示
Hostname/IP doesn't match certificate's altnames. IP: 192.168.99.101 is not in the cert's list: 192.168.99.100
打开VirtualBox一看,果然Docker Toolbox创建的名为default的VM的IP变成了192.168.99.101,192.168.99.100被minikube占用了。

现象类似于以下几个链接中所报的问题:
https://github.com/docker/kitematic/issues/519
https://github.com/docker/kitematic/issues/236

解决方案

  1. 打开Docker Quickstart Terminal
  2. docker-machine regenerate-certs
  3. 重启Kitematic,或者在报错页面上点击RETRY SETUP
    成功!

版本

  • Kitematic版本:
    v0.35.4
  • Docker版本:
    Client:
    Version: 18.03.0-ce
    API version: 1.37
    Go version: go1.9.4
    Git commit: 0520e24302
    Built: Fri Mar 23 08:31:36 2018
    OS/Arch: windows/amd64
    Experimental: false
    Orchestrator: swarm
    Server: Docker Engine - Community
    Engine:
    Version: 18.09.0
    API version: 1.39 (minimum version 1.12)
    Go version: go1.10.4
    Git commit: 4d60db4
    Built: Wed Nov 7 00:52:55 2018
    OS/Arch: linux/amd64
    Experimental: false

  • VirtualBox 版本
    5.2.8 r121009

转载于:https://www.cnblogs.com/midnightcat/p/kitematic-docker-toolbox-hostname-IP-doesnt-match-certificates-altnames.html

你可能感兴趣的:(Hostname/IP doesn't match certificate's altnames)