Kitematic freezes at 99% in setup

[davidthewatson]

I waited half an hour on this window. It froze at 99%. I have virtualbox installed.

https://www.dropbox.com/s/ypxdos36boi4w8u/Screenshot%202015-04-16%2019.16.28.png?dl=0

[DRuffer]

C:\Users\Dennis\AppData\Local\Kitematic\app-0.7.6\resources\resources>docker-mac hine restart kitematic Starting VM... Restarted machines may have new IP addresses. You may need to re-run the docker -machine env command.

C:\Users\Dennis\AppData\Local\Kitematic\app-0.7.6\resources\resources>ping 192.1 68.99.100

Pinging 192.168.99.100 with 32 bytes of data: Request timed out. Request timed out.

Ping statistics for 192.168.99.100: Packets: Sent = 2, Received = 0, Lost = 2 (100% loss), Control-C

DaR

From: FrenchBen Sent: ‎Thursday‎, ‎July‎ ‎23‎, ‎2015 ‎7‎:‎25‎ ‎AM To: kitematic/kitematic Cc: Dennis Ruffer

@DRuffer Could you take a screenshot of step 5. to show the vboxnet setup - Also you may need to kill the original Vbox DHCP service to get it to grab the changes. Can you also try to ping the VM once it's restarted? docker-machine restart kitematic ping 192.168.99.100

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

[FrenchBen]

Looks like the VirtualBox DHCP isn't assigning the IP properly, which is causing that ping to fail.

[praveen12bnitt]

I am having the exact same issue with docker-machine, boot2docker and virtualbox. So it might not be a issue with kitematic. As @FrenchBen pointed out, it is a issue with VirtualBox DHCP.. Not sure where to get help.. I am searching and will update you if i find a solution.

[doxxx]

I upgraded to Kitematic 0.7.6 (on Windows 7 with VirtualBox 5 already installed) and my "hung at 99%" problem went away.

[rwatts3]

I can concur , that was my solution as well.

On Sat, Jul 25, 2015 at 11:38 AM, Gordon Tyler notifications@github.com wrote:

I upgraded to Kitematic 0.7.6 (on Windows 7 with VirtualBox 5 already installed) and my "hung at 99%" problem went away.

— Reply to this email directly or view it on GitHub https://github.com/kitematic/kitematic/issues/386#issuecomment-124870960 .

Ryan Watts E.ryandwatts@gmail.com C.520-442-8962 F.520-437-0914 IN. https://www.linkedin.com/in/ryandwatts

[DRuffer]

Where as, I started with KitematicSetup-0.7.6-Windows-Alpha.exe, it's not as simple as that, but certainly a sign that progress is being made, and gives me assurance that this can be figured out.

DaR

From: Ryan Watts Sent: ‎Saturday‎, ‎July‎ ‎25‎, ‎2015 ‎4‎:‎40‎ ‎PM To: kitematic/kitematic Cc: Dennis Ruffer

I can concur , that was my solution as well.

On Sat, Jul 25, 2015 at 11:38 AM, Gordon Tyler notifications@github.com wrote:

I upgraded to Kitematic 0.7.6 (on Windows 7 with VirtualBox 5 already installed) and my "hung at 99%" problem went away.

— Reply to this email directly or view it on GitHub https://github.com/kitematic/kitematic/issues/386#issuecomment-124870960 .

Ryan Watts E.ryandwatts@gmail.com C.520-442-8962 F.520-437-0914 IN. https://www.linkedin.com/in/ryandwatts

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

[doxxx]

So I came back to this today and Kitematic timed out trying to contact the Docker Engine, even though VirtualBox was showing the VM as running. This is the same VM instance that I tested the last time I posted here.

Some things that may be related:

1. I put my PC to sleep when I'm not using it.
2. Every time I've woken it up, over the last few days, Windows popped up a warning that another device on my network is using the same IP address. The Event Viewer shows the following error in the System log:

Log Name:      System
Source:        Tcpip
Date:          7/27/2015 6:55:07 PM
Event ID:      4199
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Aizen
Description:
The system detected an address conflict for IP address 192.168.99.1 with the system having network hardware address 08-00-27-EB-2F-40. Network operations on this system may be disrupted as a result.

I think 192.168.99.0 is the network that docker-machine likes to use for the VirtualBox VM that it creates?

I'm going to try downgrading to VirtualBox 4.3. There might be a problem with VB 5's restoring of the virtual NICs when the host resumes from sleep.

[doxxx]

After downgrading to VirtualBox 4.3 and rebooting, starting Kitematic triggers a warning from Windows that another computer on my network is trying to use the same IP address, as the Kitematic VM is being started.

The Windows event log shows a similar error as above. Same IP address, different MAC address. My VirtualBox network settings already have a "VirtualBox Host-Only Network #2" defined using that IP address. Is it possible that Kitematic or docker-machine is trying to define a new network (device) with the same settings that is clashing with the existing one?

[doxxx]

Deleting the network in VirtualBox and trying to start Kitematic results in the recreation of the network. Something interesting that I noticed is that while the VM was starting, I got two UAC popups from Windows asking if "VirtualBox Interface" should be allowed to "make changes to this computer".

[praveen12bnitt]

Can u please share the commands u used to delete the virtual network in VirtualBox On Jul 27, 2015 7:56 PM, "Gordon Tyler" notifications@github.com wrote:

Deleting the network in VirtualBox and trying to start Kitematic results in the recreation of the network. Something interesting that I noticed is that while the VM was starting, I got two UAC popups from Windows asking if "VirtualBox Interface" should be allowed to "make changes to this computer".

— Reply to this email directly or view it on GitHub https://github.com/kitematic/kitematic/issues/386#issuecomment-125381471 .

[pnunn]

Having the same issues with Kitematic 0.7.6, VB 5.0 and Mac. Tried turning off the networking on the boot2docker-vm before installing Kitematic and its machine but still stuck at 99%.

[thunderchildau]

Hey all, I've been smashing my head against a wall for a day or two on this and managed to track this down to my Antivirus getting in the way, Environment is windows 8.1, vb 5.0, kitematic windows alpha disabled Kaspersy, rebooted and kitematic installed. I know that Kaspersky does crazy networking security and didn't think about this until now.

[doxxx]

@praveen12bnitt I don't use the CLI to delete the networks. I go through the VirtualBox GUI: File->Preferences->Network->Host-only Networks, select each network and click the delete button.

[doxxx]

FWIW, Kitematic v0.7.6 with VirtualBox 4.3.26 on my work machine (as opposed to my home machine where I'm having all the trouble) is working fine. I have docker-machine 0.3.0 manually installled but I don't know if Kitematic is using it. It's on my system PATH.

I have a suspicion that this might be a problem with docker-machine, and not Kitematic. When I get home this evening I'll try to create a VM using docker-machien directly.

[FrenchBen]

@thunderchildau Thanks for the input, tight antivirus/security settings would def get in the way!

[praveen12bnitt]

Thanks @doxxx . I dont think its Kitematic issue. Its either a docker-machine issue, which creates the networks , or issue with Virutalbox.

I have see this behavior in Virtualbox 4.x and Virtualbox 5.x. If my laptop wakes up from Hibernate or sleep mode, i get a error saying that another device on my network is using the same IP address.

I had to reboot my laptop to get docker-machine working again. I will create a ticket in docker-machine and see if someone can help.

[FrenchBen]

@praveen12bnitt It's more than likely a VirtualBox DHCP issue, since it's the daemon that manages all of your networking on the VM. See the wiki on usual networking issues: https://github.com/kitematic/kitematic/wiki/Common-Issues-and-Fixes#kitematic-vm-stuck-at-99

[sandromello]

I think the problem may be related to the validation of SSH with the docker host, docker-machine stop validating after 3 tentatives, running docker-machine -D start dev will show the the command used for connecting with the docker host:

/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/<youruser>/.docker/machine/machines/dev/id_rsa -p 51136 docker@localhost

If the docker-machine fails the SSH validation, Kitematic will not work.

The trick I think is to start the dev machine quick, restart the machine and I think it will be more fast than stopping/starting

docker-machine -D restart dev
# After successful restart (detach from tty)
docker-machine regenerate-certs dev

Then start Kitematic

[66beta]

same issue on my Mac ( 0.7.4 & 0.7.6 ) works on Windows 7

[Gi60s]

Just adding my two cents to the potential solutions. I'm running Windows 7. I uninstalled VirtualBox, restarted my computer, and let Kitematic do the install of VirtualBox for me. It now works.

[FrenchBen]

thanks for the input @GoneIn20Seconds - Hope this helps other users.

[autoferrit]

On windows 10 with virtual box 5 (letting kitematic download VB), I fixed my issue by enabling virtualization in BIOS. In windows 8/10 you can get there by clicking he power menu, holding [SHIFT] then hitting restart. Keeping [SHIFT] held until the screen changes. Then go into advanced settings and then change EUFI settings (were not changing those settings, were just getting into BIOS).

Once in BIOS just enable virtualization, then save and restart. Then it just worked.

[inakiabt]

I've fixed this on OSX thanks to https://github.com/docker/machine/issues/1591#issuecomment-126169020

[powdahound]

Disabling SSH multiplexing worked for me too. Thanks for referencing that here, @inakiabt.

[inakiabt]

Also, I excluded localhost like this:

Host * !localhost
    controlmaster auto
    controlpersist 2h
    controlpath ~/tmp/ssh_mux_%h_%p_%r
Host *
    forwardagent yes
    serveralivecountmax 20
    serveraliveinterval 120

[DRuffer]

It looks like KitematicSetup-0.8.3-Windows-Alpha has fixed my issue, even on a fresh Win10 update. I still had to go in and remove the VM from VirtualBox after it created it the 1st time, but then, for the 1st time, I've got a list of Recommended containers. I can even run my original containers that I created way back when I started down this path. Yea!

Way to go everyone who busted their butts to get over these issues!

Now, to get into into the Docker Toolbox! ;)

DaR

On Mon, Jul 20, 2015 at 9:24 AM, FrenchBen notifications@github.com wrote:

@doxxx https://github.com/doxxx The latest Kitematic release is 0.7.6, which has a few key updates - Please update and let us know if that fixes your issue: https://github.com/kitematic/kitematic/releases

— Reply to this email directly or view it on GitHub https://github.com/kitematic/kitematic/issues/386#issuecomment-122938560 .

[FrenchBen]

Glad to hear the latest build fixed your issues - Thanks for the feedback @DRuffer.

[tony-dot-sh]

Like @Gi60s said:

Just adding my two cents to the potential solutions. I'm running Windows 7. I uninstalled VirtualBox, restarted my computer, and let Kitematic do the install of VirtualBox for me. It now works.

This worked perfect for me. You also don't have to worry about losing any VirtualBox VMs.

[lukabirsa]

As in: docker/machine#1591

Recreating the docker machine with --native-ssh fixed it:

docker-machine rm default
docker-machine --native-ssh create -d virtualbox default

[junxy]

@luizkowalski :+1: is working. thanks.

[mchiang0610]

Merging with #1029

[omarabid]

I had the same problem and adding the localhost line as per @timothyjlaurent comment fixed it.

[JesterEE]

@luizkowalski :+1: Working. Thanks!

[cfontes]

For me it was installing Virtualbox 5+ and it got solved, I had 4.3 installed before.

[u12206050]

When running the commands on Windows 10 stated by lukabirsa, I get the following error: Error creating machine: Error in driver during machine creation: exit status 1.

Like many others I have uninstalled VMBox, DockerToolkit, and manually removed .FOLDERS, system64 files, and the VMBox registry entries, restarted, installed DockerToolbox-1.9.1e, ran Kitematic and go a massive long error, sometime after being prompted twice for VMBox adapters to be added. It was after this that I tried the command line.

Have added localhost to hosts file. Visualization is enabled in bios. Have tried to add the 192.168.99 net adapter via command line but that command doesn't seem to work.

Any help would be appreciated.

[karlkilden]

Removed machine in virtualbox after install worked for me

[raok1997]

I have this problem on windows 7 and tried multiple options, like changing hosts file, reinstalling kitematic, vm box mgr, but nothing worked. Thanks @doxxx , your solution worked. I just deleted the host only networks from VM virtual box manager and started kitematic and it worked.

FYI: Deleting and creating VM would lose all the docker apps and I didn't prefer that.