Stuck at 99%

[peroksid]

Started Kinematic (Beta), it stucks on 99% on "Step out of 2", Starting Docker VM. Mac OS 10.10.2 (14C1510)

[peroksid]

Kinematic version is 0.5.10

[otaran]

:+1:

[DieterReuter]

I had the same issue. Installing v0.5.11 the very first time, but after some minutes waiting it was ok. Now it's running. Maybe there's any timeout controlling the VirtualBox VM.

[otaran]

I get following error after waiting for awhile (0.5.10): Error: connect ETIMEDOUT 192.168.99.101:2376

[peroksid]

VirtualBox GUI shows "dev" VM in running state. Kinematic still shows 99% (more than 1 hour since I launched Kinematic). I have boot2docker installed already (previously) but I haven't started it this time. Maybe this could cause something.

[dfinninger]

:+1: Hung at 99%. Virtualbox shows "dev" VM running and the preview has the Boot2Docker login all fine. I force quit Kitematic, then reopened it. Then reopened the app and everything came up fine.

Looks like this may just be a bug in the install process where Kitematic isn't properly notified that everything came up a-ok.

[mattkanwisher]

Same here stuck at 99%, the boot2docker is up in my virtual box, but it can't connect to 192.168.1.100 on the virtual box

[cfljam]

Im stuck at "loading images" . Force quit + restart didnt help.

[jzmudzinski]

It seems to be issue with Yosemite. I guess this is the source of the error:

WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.3 instead of 10.10.3. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.

[otaran]

I am running Mavericks (10.9.5), so I don't think this is the issue with Yosemite.

[jmorganca]

Thanks for reporting this - the integration with docker machine isn't quite perfect yet, sorry about that. We're hard at work on it. Some gotchas we've seen:

• Corporate VPN blocking access to 192.168.x.x
• Make sure you have VirtualBox 4.3.x installed (Kitematic will use your existing VBox or install the latest)

Usually the best way is to restart (i.e. remove the vm and start Kitematic again).

[gegere]

@jeffdm this worked great as a solution!

[otaran]

After OS reboot everything is working!

[benoitbesnard]

@jeffdm It's OK for me !

Don't forget to remove the "dev" VM from Virtual Box.

[cfljam]

Worked for me too

Sent from my shoe

---

From: Benoît Besnardmailto:notifications@github.com Sent: ‎13/‎03/‎2015 5:17 a.m. To: kitematic/kitematicmailto:kitematic@noreply.github.com Cc: John McCallummailto:John.McCallum@plantandfood.co.nz Subject: Re: [kitematic] Stuck at 99% (#236)

@jeffdmhttps://github.com/jeffdm It's OK for me !

Don't forget to remove the "dev" VM from Virtual Box.

— Reply to this email directly or view it on GitHubhttps://github.com/kitematic/kitematic/issues/236#issuecomment-78901681.

The contents of this e-mail are confidential and may be subject to legal privilege. If you are not the intended recipient you must not use, disseminate, distribute or reproduce all or any part of this e-mail or attachments. If you have received this e-mail in error, please notify the sender and delete all material pertaining to this e-mail. Any opinion or views expressed in this e-mail are those of the individual sender and may not represent those of The New Zealand Institute for Plant and Food Research Limited.

[toriaezunama]

I had the same problem and the fix worked for me too

[stuartcw]

I have the same problem Virtual Box 4.3.26 and Kitematic (Beta) Version 0.5.10.

I have:

• Reinstalled Virtual Box
• Reinstalled Kitematic
• Removed dev VMs from Virtual Box and tried starting Kitematic again.

Does any have any other ideas?

My Mac's IP address details are:

inet 192.168.2.103 netmask 0xffffff00 broadcast 192.168.2.255

Does this make any difference? It is not clashing with the Virtual Box IP Address of:

inet 192.168.99.1 netmask 0xffffff00 broadcast 192.168.99.255

[diegorojas-dev]

I had same problem and finally removing "dev" VM solved issue. Thanks.

[wangwenchao]

I remove the dev and reinstall the Kitematic twice ,it works :)

[argan]

I reinstalled VIrtualBox(4.3.26), Kitematic(0.5.13) , and remove dev from VirtualBox ,but it doesn't work.

[jmorganca]

@argan if you run:

• docker-machine ssh dev
• docker ps

This will check that the VM is up and Docker is running inside. Does this work?

Thanks for the note

[argan]

I can "docker-machine ssh dev" into the runing VM, and "docker ps" works ,no container running,but kitematic still stuck at 99%

[goseki]

@argan try deleting dev AND remove it DELETING files .. THEN rerun Kitematic .. I was like you it sat on 99% for a time but I could see dev had booted and unlike other times where boot2docker had not properly installed/configured this time everything was configured and Kitematic GUI happily loaded hello-world

[argan]

Delete 'dev' VM first, start Kitematic,it stuck at 99%,and in VIrtualBox GUI,'dev' VM shows 'running',then quit Kitematic and restart it , it works .

[jmorganca]

@argan thanks for the info!

Deleting the VM seems to solve the problem, though it's not a great solution. Some machine related fixes should come in docker-machine 0.2.0 and then we'll deep dive from there!

[argan]

@jeffdm Also I delete boot2docker.app first,maybe boot2docker and kitematic are fighting in my computer,:)

[ruprict]

Same problem :crying_cat_face: I have:

• Removed boot2docker entirely
• Rebooted
• Removed the dev vm several times and restarted the Kitematic setup
• Quit Kitematic, restarted VM, open Kitematic.
• Did the docker-machine rm approach from Known Issues

All to no avail. VM 4.3.26 and Kitematic 0.5.13, docker-machine 1.0

The dev VM seems to start (albeit, slowly) and get to a prompt, but the process never gets passed INFO[0009] Waiting for VM to start... It just sits there...forever.

Looks like what I am seeing is related to this issue

[jmorganca]

@argan I don't think so :smiley: Though it seems like having two VMs sometimes causes issues. Looking into this.

@ruprict sorry to hear that! If you run docker-machine ssh dev, are you able to ssh into the VM once it's started? Does it show any kind of error? Is it the port '0' error? I'll keep an eye on the docker-machine issue you linked to

[ruprict]

@jeffdm Nope, I cannot...get the Bad port '0' message. :sad_panda:

[jmorganca]

I see. Thanks @ruprict. Sorry about that

[pixeldrew]

I fixed this by removing the dev machine AND all of the virtual networks in settings. It seems that docker-machine doesn't play nice if you've had other host only adapters added (mine were added by vagrant)

[jmorganca]

@pixeldrew thanks!!

Interesting, the host adapters seem to be related

cc @ehazlett @nathanleclaire

[nathanleclaire]

I fixed this by removing the dev machine AND all of the virtual networks in settings. It seems that docker-machine doesn't play nice if you've had other host only adapters added (mine were added by vagrant)

I'm starting to suspect that some of the networking woes are related to this issue as multiple users have brought it up now.

[dev-guy]

FYI in case someone does this, I had the "99% problem" after I stupidly removed the port forwarding for ssh. VirtualBox dev->Settings->Network->Adapter 1->Port Forwarding

[mchiang0610]

We are testing out a pre-release that should fix this problem! Mind giving it a try?

https://github.com/kitematic/kitematic/releases/download/v0.5.27-intel-nic/Kitematic-0.5.27-intel-nic.zip

Let us know if you are still running into the issue after.

[goseki]

OK .. the first run produced the
  attached result ..

  BUT .. choose Delete VM and retry .. and boom!

  Works just fine .. loaded up an Nginx container which works
  perfect.

  So whatever you're doing in that Delete VM .. is the answer.

  Cheers

  On 21/05/15 6:03 pm, Michael Chiang wrote:

  We are testing out a pre-release that should fix this problem!
    Mind giving it a try?
  https://github.com/kitematic/kitematic/releases/download/v0.5.27-intel-nic/Kitematic-0.5.27-intel-nic.zip
  Let us know if you are still running into the issue after.
  —
    Reply to this email directly or view
      it on GitHub.

[mchiang0610]

@goseki sorry, your result doesn't seem to be included.

cc @ehazlett @nathanleclaire ; seems like the issue isn't fully fixed yet. We will continue to update you guys on this.

[goseki]

ok .. here is the text from the setup
  error

  We're Sorry!

  There seems to have been an unexpected error with Kitematic:

  Cannot connect to the Docker Engine. Either
    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.101"

    Retry Setup ..... Delete VM and
    Retry Setup  <- THIS WORKS!

  On 21/05/15 6:49 pm, Michael Chiang wrote:

  @goseki sorry, your result doesn't
    seem to be included. 
  cc @ehazlett
    @nathanleclaire
    ; seems like the issue isn't fully fixed yet. 
  —
    Reply to this email directly or view
      it on GitHub.

[dougio]

@mchiang0610 I have tried 0.5.27 on my computer, still doesn't work. I have a boot2docker installed before I use kitematic. So when I was trying 0.5.27, there were two virtual machines in my virtualbox -- one was "boot2docker", the other one was "dev" (created by kitematic).

Finally, I removed both of them, restart virtualbox and kitematic, it successful started. There is only "dev" virtual machine left now.

Maybe the boot2docker cannot work with kitematic on same computer?

[mchiang0610]

@goseki Thanks! So it seems like re-creating Docker Machine instance worked.

@mhoudg Do you mind providing logs to help with this?

cd  your directory

./Kitematic\ \(Beta\).app/Contents/MacOS/Kitematic\ \(Beta\) 

[goseki]

@michaelchiang  yes this was the
  technique I used to get B2D installed previously .. 
  the Dev VM seems at fault somehow .. some have suggested the
  virtual network controllers might be at fault .. certainly that
  MIGHT be supported by the error message I got .. 99.100 vs 99.101

  could it be something as simple as a mis-indexed variable?
  whatever gets assigned to the virtual controller's IP address?

  On 21/05/15 7:28 pm, Michael Chiang wrote:

  @goseki Thanks! So it seems like
    re-creating Docker Machine instance worked. 
  @mhoudg Do you mind providing logs to
    help with this? 
  ./Kitematic\ \(Beta\).app/Contents/MacOS/Kitematic\ \(Beta\) 

  —
    Reply to this email directly or view
      it on GitHub.

[dougio]

@mchiang0610 I would like to send you the file, but that path looks like a binary file, are you sure that's what you want? And how can I send you a file on github? I can't see your email

[mchiang0610]

@mhoudg Oh, that command would run Kitematic with logs showing. I would like the logs.

[mchiang0610]

@mhoudg Did you try the v0.5.27-intel-nic one? The v0.5.27 official release doesn't have the fix. The pre-release: https://github.com/kitematic/kitematic/releases/tag/v0.5.27-intel-nic

[dougio]

@mchiang0610 I'm using the official release edition. Haven't tried pre-release edition. And after I have removed "boot2docker-vm" and "dev", Kitematic not stuck any more. I have tried to remove "dev", start a "boot2docker-vm", and start Kitematic again, still not stuck.

I don't if the log still helps:

➜  MacOS  ./Kitematic\ \(Beta\)
[74743:0521/163543:INFO:renderer_main.cc(200)] Renderer process started
[74741:0521/163544:INFO:CONSOLE(109)] "Download the React DevTools for a better development experience: https://fb.me/react-devtools", source: /Applications/Kitematic (Beta).app/Contents/Resources/app/node_modules/react/lib/React.js (109)
Checking for update...
[74741:0521/163547:INFO:CONSOLE(48)] "Warning: Don't set .props.width of the React component <RetinaImage />. Instead, specify the correct value when initially creating the element or use React.cloneElement to make a new element with updated props. The element was created by Containers.", source: /Applications/Kitematic (Beta).app/Contents/Resources/app/node_modules/react/lib/warning.js (48)
[74741:0521/163547:INFO:CONSOLE(48)] "Warning: Don't set .props.height of the React component <RetinaImage />. Instead, specify the correct value when initially creating the element or use React.cloneElement to make a new element with updated props. The element was created by Containers.", source: /Applications/Kitematic (Beta).app/Contents/Resources/app/node_modules/react/lib/warning.js (48)
[74741:0521/163547:INFO:CONSOLE(48)] "Warning: Don't set .props.width of the React component <RetinaImage />. Instead, specify the correct value when initially creating the element or use React.cloneElement to make a new element with updated props. The element was created by Header.", source: /Applications/Kitematic (Beta).app/Contents/Resources/app/node_modules/react/lib/warning.js (48)
[74741:0521/163547:INFO:CONSOLE(48)] "Warning: Don't set .props.height of the React component <RetinaImage />. Instead, specify the correct value when initially creating the element or use React.cloneElement to make a new element with updated props. The element was created by Header.", source: /Applications/Kitematic (Beta).app/Contents/Resources/app/node_modules/react/lib/warning.js (48)
Update not available.
[74741:0521/163626:INFO:CONSOLE(104)] "[object Object]", source: /Applications/Kitematic (Beta).app/Contents/Resources/app/build/components/NewContainerSearch.react.js (104)

[mchiang0610]

@mhoudg The official release version doesn't have the patch yet because we are still testing the patch. This one should fix it. https://github.com/kitematic/kitematic/releases/tag/v0.5.27-intel-nic

[epavlenko]

@mchiang0610, with Kitematic-0.5.27-intel-nic on 99% I get the following in log file and it's stuck again:

[3439:0521/134146:INFO:CONSOLE(62)] "Uncaught RangeError: Invalid string length", source: /Users/eugene/Downloads/Kinematic/Kitematic (Beta).app/Contents/Resources/app/node_modules/exec/exec.js (62) [3439:0521/134146:INFO:CONSOLE(62)] "Uncaught RangeError: Invalid string length", source: /Users/eugene/Downloads/Kinematic/Kitematic (Beta).app/Contents/Resources/app/node_modules/exec/exec.js (62) [3439:0521/134146:INFO:CONSOLE(62)] "Uncaught RangeError: Invalid string length", source: /Users/eugene/Downloads/Kinematic/Kitematic (Beta).app/Contents/Resources/app/node_modules/exec/exec.js (62) ...

[dev-guy]

@mchiang0610 Same problem. I will delete dev and see if it happens again. I have another vm running in virtual box. I think the problem has to do with which ip address 'dev' gets upon install versus reboot.

[dev-guy]

@mchiang0610 Bad news. After creating a new 'dev' and rebooting, same problem. Reboot is the killer for me.

[nathanleclaire]

  Cannot connect to the Docker Engine. Either
    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.101"

This type of issue is why the docker-machine regenerate-certs command was created, although if I recall correctly it should do this automatically on start if the certs are invalid.