Closed peroksid closed 9 years ago
In my case, the VM "dev" folder and everything in it was created belonging to "root". I ran the installation under a different user with admin privileges. In VirtualBox it showed that VM was inaccessible. So I changed the owner to match the ID/group I used to install and that error went away. However it is still stuck at 99%.
Just to report that v0.5.27-intel-nic works for me. v0.5.27 and v0.6.00 repeatedly get error:
Testing TCP connection to: localhost:51397
Using SSH client type: external
About to run SSH command:
exit 0
&{/usr/bin/ssh [/usr/bin/ssh -o PasswordAuthentication=no -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -i /Users/a/.docker/machine/machines/dev/id_rsa -p 51397 docker@localhost exit 0] []
Same isse, deleted dev from VM, restarted KiteMatic, and then worked. :)
It's more an Alpha than a Beta, but I liked it! =D
@lordillusions Thanks. There are still a lot of work in stabilizing Kitematic. We are dependent on many projects so we are trying our best to make sure the issues get solved in a 'somewhat' timely fashion. :)
I have the same issue running Kitematic from source in a fresh Mac Mavericks VM.
Stuck at 99%, high CPU load of docker-machine
0.2.0 consuming a lot of memory.
Investigating with docker-machine ls
shows the "Bad port '0'" error from https://github.com/docker/machine/issues/479
$ ./docker-machine ls
Bad port '0'
ERRO[0000] error getting URL for host dev: exit status 255
NAME ACTIVE DRIVER STATE URL SWARM
dev virtualbox Running
vagrant at kitematic in ~/code/kitematic/resources on master-hypriot
With debug information:
$ ./docker-machine -D ls
DEBU[0000] executing: /usr/bin/VBoxManage showvminfo dev --machinereadable
DEBU[0000] STDOUT: name="dev"
groups="/"
ostype="Linux 2.6 / 3.x (64 bit)"
UUID="7d0c0576-f71c-4d6e-9c86-5d4306d130ed"
CfgFile="/Users/vagrant/.docker/machine/machines/dev/dev/dev.vbox"
SnapFldr="/Users/vagrant/.docker/machine/machines/dev/dev/Snapshots"
LogFldr="/Users/vagrant/.docker/machine/machines/dev/dev/Logs"
hardwareuuid="7d0c0576-f71c-4d6e-9c86-5d4306d130ed"
memory=2048
pagefusion="off"
vram=8
cpuexecutioncap=100
hpet="on"
chipset="piix3"
firmware="BIOS"
cpus=2
pae="on"
longmode="on"
synthcpu="off"
bootmenu="disabled"
boot1="dvd"
boot2="dvd"
boot3="disk"
boot4="none"
acpi="on"
ioapic="on"
biossystemtimeoffset=0
rtcuseutc="on"
hwvirtex="on"
nestedpaging="on"
largepages="on"
vtxvpid="on"
vtxux="on"
VMState="running"
VMStateChangeTime="2015-06-06T06:40:09.687000000"
monitorcount=1
accelerate3d="off"
accelerate2dvideo="off"
teleporterenabled="off"
teleporterport=0
teleporteraddress=""
teleporterpassword=""
tracing-enabled="off"
tracing-allow-vm-access="off"
tracing-config=""
autostart-enabled="off"
autostart-delay=0
defaultfrontend=""
storagecontrollername0="SATA"
storagecontrollertype0="IntelAhci"
storagecontrollerinstance0="0"
storagecontrollermaxportcount0="30"
storagecontrollerportcount0="30"
storagecontrollerbootable0="on"
"SATA-0-0"="/Users/vagrant/.docker/machine/machines/dev/boot2docker.iso"
"SATA-ImageUUID-0-0"="5b82e89d-4c6a-4e45-9a1e-dc95ab03143a"
"SATA-tempeject"="off"
"SATA-IsEjected"="off"
"SATA-1-0"="/Users/vagrant/.docker/machine/machines/dev/disk.vmdk"
"SATA-ImageUUID-1-0"="d00851e8-889a-4094-a47e-966437877eed"
"SATA-2-0"="none"
"SATA-3-0"="none"
"SATA-4-0"="none"
"SATA-5-0"="none"
"SATA-6-0"="none"
"SATA-7-0"="none"
"SATA-8-0"="none"
"SATA-9-0"="none"
"SATA-10-0"="none"
"SATA-11-0"="none"
"SATA-12-0"="none"
"SATA-13-0"="none"
"SATA-14-0"="none"
"SATA-15-0"="none"
"SATA-16-0"="none"
"SATA-17-0"="none"
"SATA-18-0"="none"
"SATA-19-0"="none"
"SATA-20-0"="none"
"SATA-21-0"="none"
"SATA-22-0"="none"
"SATA-23-0"="none"
"SATA-24-0"="none"
"SATA-25-0"="none"
"SATA-26-0"="none"
"SATA-27-0"="none"
"SATA-28-0"="none"
"SATA-29-0"="none"
natnet1="nat"
macaddress1="080027841BBF"
cableconnected1="on"
nic1="nat"
nictype1="virtio"
nicspeed1="0"
mtu="0"
sockSnd="64"
sockRcv="64"
tcpWndSnd="64"
tcpWndRcv="64"
Forwarding(0)="ssh,tcp,127.0.0.1,51086,,22"
hostonlyadapter2="vboxnet0"
macaddress2="08002758E9F5"
cableconnected2="on"
nic2="hostonly"
nictype2="virtio"
nicspeed2="0"
nic3="none"
nic4="none"
nic5="none"
nic6="none"
nic7="none"
nic8="none"
hidpointing="ps2mouse"
hidkeyboard="ps2kbd"
uart1="off"
uart2="off"
lpt1="off"
lpt2="off"
audio="none"
clipboard="disabled"
draganddrop="disabled"
SessionType="headless"
VideoMode="720,400,0"@0,0
vrde="off"
usb="off"
ehci="off"
SharedFolderNameMachineMapping1="Users"
SharedFolderPathMachineMapping1="/Users"
VRDEActiveConnection="off"
VRDEClients=0
vcpenabled="off"
vcpscreens=0
vcpfile="/Users/vagrant/.docker/machine/machines/dev/dev/dev.webm"
vcpwidth=1024
vcpheight=768
vcprate=512
vcpfps=25
GuestMemoryBalloon=0
GuestOSType="Linux26_64"
GuestAdditionsRunLevel=1
GuestAdditionsVersion="4.3.28 r100309"
GuestAdditionsFacility_VirtualBox Base Driver=50,1433572831303
GuestAdditionsFacility_Seamless Mode=0,1433572831302
GuestAdditionsFacility_Graphics Mode=0,1433572831302
DEBU[0000] STDERR:
DEBU[0000] executing: /usr/bin/VBoxManage showvminfo dev --machinereadable
DEBU[0000] STDOUT: name="dev"
groups="/"
ostype="Linux 2.6 / 3.x (64 bit)"
UUID="7d0c0576-f71c-4d6e-9c86-5d4306d130ed"
CfgFile="/Users/vagrant/.docker/machine/machines/dev/dev/dev.vbox"
SnapFldr="/Users/vagrant/.docker/machine/machines/dev/dev/Snapshots"
LogFldr="/Users/vagrant/.docker/machine/machines/dev/dev/Logs"
hardwareuuid="7d0c0576-f71c-4d6e-9c86-5d4306d130ed"
memory=2048
pagefusion="off"
vram=8
cpuexecutioncap=100
hpet="on"
chipset="piix3"
firmware="BIOS"
cpus=2
pae="on"
longmode="on"
synthcpu="off"
bootmenu="disabled"
boot1="dvd"
boot2="dvd"
boot3="disk"
boot4="none"
acpi="on"
ioapic="on"
biossystemtimeoffset=0
rtcuseutc="on"
hwvirtex="on"
nestedpaging="on"
largepages="on"
vtxvpid="on"
vtxux="on"
VMState="running"
VMStateChangeTime="2015-06-06T06:40:09.687000000"
monitorcount=1
accelerate3d="off"
accelerate2dvideo="off"
teleporterenabled="off"
teleporterport=0
teleporteraddress=""
teleporterpassword=""
tracing-enabled="off"
tracing-allow-vm-access="off"
tracing-config=""
autostart-enabled="off"
autostart-delay=0
defaultfrontend=""
storagecontrollername0="SATA"
storagecontrollertype0="IntelAhci"
storagecontrollerinstance0="0"
storagecontrollermaxportcount0="30"
storagecontrollerportcount0="30"
storagecontrollerbootable0="on"
"SATA-0-0"="/Users/vagrant/.docker/machine/machines/dev/boot2docker.iso"
"SATA-ImageUUID-0-0"="5b82e89d-4c6a-4e45-9a1e-dc95ab03143a"
"SATA-tempeject"="off"
"SATA-IsEjected"="off"
"SATA-1-0"="/Users/vagrant/.docker/machine/machines/dev/disk.vmdk"
"SATA-ImageUUID-1-0"="d00851e8-889a-4094-a47e-966437877eed"
"SATA-2-0"="none"
"SATA-3-0"="none"
"SATA-4-0"="none"
"SATA-5-0"="none"
"SATA-6-0"="none"
"SATA-7-0"="none"
"SATA-8-0"="none"
"SATA-9-0"="none"
"SATA-10-0"="none"
"SATA-11-0"="none"
"SATA-12-0"="none"
"SATA-13-0"="none"
"SATA-14-0"="none"
"SATA-15-0"="none"
"SATA-16-0"="none"
"SATA-17-0"="none"
"SATA-18-0"="none"
"SATA-19-0"="none"
"SATA-20-0"="none"
"SATA-21-0"="none"
"SATA-22-0"="none"
"SATA-23-0"="none"
"SATA-24-0"="none"
"SATA-25-0"="none"
"SATA-26-0"="none"
"SATA-27-0"="none"
"SATA-28-0"="none"
"SATA-29-0"="none"
natnet1="nat"
macaddress1="080027841BBF"
cableconnected1="on"
nic1="nat"
nictype1="virtio"
nicspeed1="0"
mtu="0"
sockSnd="64"
sockRcv="64"
tcpWndSnd="64"
tcpWndRcv="64"
Forwarding(0)="ssh,tcp,127.0.0.1,51086,,22"
hostonlyadapter2="vboxnet0"
macaddress2="08002758E9F5"
cableconnected2="on"
nic2="hostonly"
nictype2="virtio"
nicspeed2="0"
nic3="none"
nic4="none"
nic5="none"
nic6="none"
nic7="none"
nic8="none"
hidpointing="ps2mouse"
hidkeyboard="ps2kbd"
uart1="off"
uart2="off"
lpt1="off"
lpt2="off"
audio="none"
clipboard="disabled"
draganddrop="disabled"
SessionType="headless"
VideoMode="720,400,0"@0,0
vrde="off"
usb="off"
ehci="off"
SharedFolderNameMachineMapping1="Users"
SharedFolderPathMachineMapping1="/Users"
VRDEActiveConnection="off"
VRDEClients=0
vcpenabled="off"
vcpscreens=0
vcpfile="/Users/vagrant/.docker/machine/machines/dev/dev/dev.webm"
vcpwidth=1024
vcpheight=768
vcprate=512
vcpfps=25
GuestMemoryBalloon=0
GuestOSType="Linux26_64"
GuestAdditionsRunLevel=1
GuestAdditionsVersion="4.3.28 r100309"
GuestAdditionsFacility_VirtualBox Base Driver=50,1433572831303
GuestAdditionsFacility_Seamless Mode=0,1433572831302
GuestAdditionsFacility_Graphics Mode=0,1433572831302
DEBU[0000] STDERR:
DEBU[0000] executing: ssh -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o ConnectionAttempts=30 -o LogLevel=quiet -p 0 -i /Users/vagrant/.docker/machine/machines/dev/id_rsa docker@localhost ip addr show dev eth1
Bad port '0'
ERRO[0000] error getting URL for host dev: exit status 255
NAME ACTIVE DRIVER STATE URL SWARM
dev virtualbox Running
vagrant at kitematic in ~/code/kitematic/resources on master-hypriot
$
There seems to be a fix with https://github.com/docker/machine/pull/1242. I'll check it with that version.
Couldn't replicate the problem at the moment. I have seen that you are now using docker-machine
0.3.0-rc1, but also 0.2.0 worked.
To investigate first time user experience of Kitematic, I have created a Vagrantfile
and use a snapshot for a faster feedback loop. The Vagrantfile could be found at https://github.com/StefanScherer/kitematic-box
Still doesn't work for me after 1) deleting kitematic and virtua box 2) reinstalling with latest 3) deleting dev 4) turning off corporate vpn and firewall 5) deleting and reinstalling from scratch again
Hi, tagging on to this issue:
I've done all the above-mentioned 'fixes'. I can connect into the machine.
Looking further into the issue, it seems to be that Kitematic maxes out at ConnectionAttempts=3 ConnectTimeout=10
, which finishes too quickly for my box to complete the setting up. Hence it just hangs at 99%.
Any way to change those configurations?
I hit the 99% problem too, but my problem is not specific to Kitematic. It's the dang Cisco VPN on Mac OS X, which tends to 1) block traffic to machines it doesn't know about, and 2) not allow modifications to the routing table while it is running. So I could see the 'dev' machine from command line and VirtualBox, but Kitematic could not finish config.
Once I figured out the subnet and vboxnetX machine, this fixed me:
From Kitematic side, perhaps an error stating that it could not connect to the VM would be helpful.
I got similar issue that say
the VM is not responding or the connection may be blocked (VPN
or Proxy): Hostname/IP doesn't match certificate's altnames:
"IP: 192.168.99.100 is not in the cert's list: 192.168.99.102"
by that moment, my "dev" docker vm was started and running. I ran below command and fix the issue /Applications/Kitematic\ (Beta).app/Contents/Resources/resources/docker-machine regenerate-certs dev
So, looks like my problem was this:
~ » cat .docker/machine/machines/dev/config.json {
"DriverName":"virtualbox",
"Driver":{
"IPAddress":"",
"SSHUser":"docker",
"SSHPort":0,
"MachineName":"dev",
"CaCertPath":"/Users/phillip/.docker/machine/certs/ca.pem",
"PrivateKeyPath":"/Users/phillip/.docker/machine/certs/ca-key.pem",
"SwarmMaster":false,
"SwarmHost":"tcp://0.0.0.0:3376",
"SwarmDiscovery":"",
"CPU":1,
"Memory":2048,
"DiskSize":20000,
"Boot2DockerURL":"/Applications/Kitematic (Beta).app/Contents/Resources/resources/boot2docker.iso",
"Boot2DockerImportVM":"",
"HostOnlyCIDR":"192.168.99.1/24"
},
"StorePath":"/Users/phillip/.docker/machine/machines/dev",
"HostOptions":{
"Driver":"",
"Memory":0,
"Disk":0,
"EngineOptions":{
"ArbitraryFlags":[
],
"Dns":null,
"GraphDir":"",
"Ipv6":false,
"InsecureRegistry":[
],
"Labels":[
],
"LogLevel":"",
"StorageDriver":"",
"SelinuxEnabled":false,
"TlsCaCert":"",
"TlsCert":"",
"TlsKey":"",
"TlsVerify":true,
"RegistryMirror":[
],
"InstallURL":"https://get.docker.com"
},
"SwarmOptions":{
"IsSwarm":false,
"Address":"",
"Discovery":"",
"Master":false,
"Host":"tcp://0.0.0.0:3376",
"Image":"swarm:latest",
"Strategy":"spread",
"Heartbeat":0,
"Overcommit":0,
"TlsCaCert":"",
"TlsCert":"",
"TlsKey":"",
"TlsVerify":false,
"ArbitraryFlags":[
]
},
"AuthOptions":{
"StorePath":"",
"CaCertPath":"/Users/phillip/.docker/machine/certs/ca.pem",
"CaCertRemotePath":"",
"ServerCertPath":"/Users/phillip/.docker/machine/machines/dev/server.pem",
"ServerKeyPath":"/Users/phillip/.docker/machine/machines/dev/server-key.pem",
"ClientKeyPath":"/Users/phillip/.docker/machine/certs/key.pem",
"ServerCertRemotePath":"",
"ServerKeyRemotePath":"",
"PrivateKeyPath":"/Users/phillip/.docker/machine/certs/ca-key.pem",
"ClientCertPath":"/Users/phillip/.docker/machine/certs/cert.pem"
}
}
}
Note the values of "SSHPort" = 0
and "SwarmHost":"tcp://0.0.0.0:3376",
. It looks like this relates to docker/machine#1031? I then did the following:
dev
image from Virtualboxrm -rf ~/.docker/machine
~/.docker/machine
folder was recreated with the same bad values in config.json
Before I did all that, I tried to run /Applications/Kitematic (Beta).app/Contents/Resources/resources/docker-machine -D ls
and got this output:
STDERR:
Using SSH client type: external
About to run SSH command:
ip addr show dev eth1
&{/usr/bin/ssh [/usr/bin/ssh -o PasswordAuthentication=no -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -i /Users/phillip/.docker/machine/machines/dev/id_rsa -p 22 docker@localhost ip addr show dev eth1] [] <nil> <nil> <nil> [] <nil> <nil> <nil> <nil> false [] [] [] [] <nil>}
SSH cmd err, output: exit status 255:
error getting URL for host dev: exit status 255
NAME ACTIVE DRIVER STATE URL SWARM
dev virtualbox Running
Still haven't gotten this to work 100% yet; get stuck on 99% with KiteMatic
I am also having the same issues as listed above. I reinstalled everything and ran into the cert issue. regenerated the certs and got things started. However, after removing the hello-world container, the issues came back and even the regenerate cert will not work. It gets to this point and then times out: bash-3.2$ docker-machine regenerate-certs default Regenerate TLS machine certs? Warning: this is irreversible. (y/n): y Regenerating TLS certificates
YEAH! I follow @rkyrk and success
Run docker-machine regenerate-certs default
-> Quit Kitematic
-> Turn off virtual machine
-> Turn on Kitematic
-> Done
99% problem still Kinematic version is 0.7.6
try regenerate-certs: Error: Host does not exist: default
$ docker-machine regenerate-certs default
Regenerate TLS machine certs? Warning: this is irreversible. (y/n): y
Regenerating TLS certificates
Error: Host does not exist: default
Than, Error getting SSH command: exit status 255
$ docker-machine active
dev
$ docker-machine regenerate-certs dev
Regenerate TLS machine certs? Warning: this is irreversible. (y/n): y
Regenerating TLS certificates
Password:
Password:
Password:
Error getting SSH command: exit status 255
Than, Upgraded Kinematic version is 0.8.3
$ docker-machine regenerate-certs default
Regenerate TLS machine certs? Warning: this is irreversible. (y/n): y
Regenerating TLS certificates
Password:
Password:
Password:
Error getting SSH command: exit status 255
$ docker-machine -v
docker-machine version 0.3.1-rc1 (993f2db)
Thanks,
docker-machine regenerate-certs default
Fixed my issue.
:+1: https://github.com/kitematic/kitematic/issues/236#issuecomment-120172060. That was very helpful. Thanks @jtyberg.
Merging with #1029
Hi, I just installed the docker toolbox 1.8.2a on my Windows 8.1 laptop. As all of you, I've gor the same problem for kitematic. I followed this thread, and tried everything but it's still not working.
Is there any fix somewhere? When will we be able to do a fresh install with everything working?
Thanks,
@yarmenti
Can you check your virtualbox, and remove the "default" VM by choosing (delete all files), and then run the installer again?
If you are connected in a VPN environment or proxy, it will not work at the moment.
Please comment on #1029 to help us have the issues merged.
Ok, I'll continue on #1029.
I found that Docker Hub sign in sometimes blocks the app... I would get to 100% and then nothing... signing in, clicking "close" gets me back to the spinner... If I close Kitematic, open it again then skip the sign in, it would open up the UI with me being signed in already.
I had the same problem in Windows 10 after creating two containers from the same image with this error:
Unable to query docker version: Get https://192.168.99.100:2376/v1.15/version: x509: certificate is valid for 192.168.99.104, not 192.168.99.100
What I did is docker-machine regenerate-certs default
, and the problem was fixed.
I didn't want to destroy the docker-machine because I manually created with 100GB.
Started Kinematic (Beta), it stucks on 99% on "Step out of 2", Starting Docker VM. Mac OS 10.10.2 (14C1510)