Starting Local & Stuck on Local Image

Support
1

Hello,
I’ve had this app installed since migrating from Pressmatic. I’m worried about my situation. It’s been a few weeks since I’ve tried accessing my projects in Local. When I went to start it, I got the landing page with “Let’s Go!” button, possibly indicating it was installing for the first time? Yikes, I had several customer projects there.

After clicking the button, VirtualBox and Host Machine loaded, but Local Image is pulsating & perhaps it is in an infinite loop. I went into Virtual Box and cloned the ‘local-by-flywheel’ instance. Next I ran this in terminal: $ /Applications/Local\ by\ Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine rm local-by-flywheel, successfully removing Flywheel.

Seemingly reinstalling and it seemed to start better however it stuck in the same place.

Some recent tasks prior to this, I’ve updated Sierra to 10.12.4, Updated Virtualbox to latest version (5.1.18 r114002 (Qt5.6.2)), While it is not running now, I’d installed a boot2docker app for another project. Should I uninstall that?

Thanks

2

I have the same issue except I’m on El Capitan and I do not have boot2docker app.

Last line in the log is

Apr 5, 2017, 1:54 PM CDT - info: [main/set-docker-env] Getting Docker Machine env.
3

I found an Remove boot2docker app tutorial and did so. After that I’m trying to install Local By Flywheel and there’s been no improvement, sadly.

I’m going to try it all again.

4

I removed several Host-only Networks listed in Network Preferences on VirtualBox.

Here’s my latest Log entry:
Apr 6, 2017, 9:25 AM EDT - info: [main/docker-create-machine] Starting Docker Machine Creation... Apr 6, 2017, 9:25 AM EDT - info: [main/docker-create-machine] USING IP: 192.168.75.1/24 Apr 6, 2017, 9:25 AM EDT - info: [main/docker-create-machine] Removing existing Docker Machine Apr 6, 2017, 9:25 AM EDT - info: [main/docker-create-machine] null 'About to remove pressmatic\nWARNING: This action will delete both local reference and remote instance.\n' 'Error removing host "pressmatic": Host does not exist: "pressmatic"\nCan\'t remove "pressmatic"\n' Apr 6, 2017, 9:25 AM EDT - info: [main/docker-create-machine] Creating Docker Machine... --virtualbox-boot2docker-url=file:///Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/boot2docker.iso Apr 6, 2017, 9:25 AM EDT - info: [main/docker-create-machine] Creating machine with { '0': 'create', '1': '--driver=virtualbox', '2': '--virtualbox-hostonly-cidr', '3': '192.168.75.1/24', '4': '--virtualbox-boot2docker-url=file:///Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/boot2docker.iso', '5': 'local-by-flywheel' } Apr 6, 2017, 9:25 AM EDT - info: [main/docker-create-machine] Running pre-create checks... Apr 6, 2017, 9:25 AM EDT - info: [main/docker-create-machine] Creating machine... Apr 6, 2017, 9:25 AM EDT - info: [main/docker-create-machine] (local-by-flywheel) Downloading /Users/gmiller/.docker/machine/cache/boot2docker.iso from file:///Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/boot2docker.iso... Apr 6, 2017, 9:25 AM EDT - info: [main/docker-create-machine] (local-by-flywheel) Creating VirtualBox VM... Apr 6, 2017, 9:25 AM EDT - info: [main/docker-create-machine] (local-by-flywheel) Creating SSH key... Apr 6, 2017, 9:25 AM EDT - info: [main/docker-create-machine] (local-by-flywheel) Starting the VM... Apr 6, 2017, 9:25 AM EDT - info: [main/docker-create-machine] (local-by-flywheel) Check network to re-create if needed... Apr 6, 2017, 9:25 AM EDT - info: [main/docker-create-machine] (local-by-flywheel) Found a new host-only adapter: "vboxnet0" Apr 6, 2017, 9:25 AM EDT - info: [main/docker-create-machine] (local-by-flywheel) Waiting for an IP... Apr 6, 2017, 9:26 AM EDT - info: [main/docker-create-machine] Waiting for machine to be running, this may take a few minutes... Apr 6, 2017, 9:26 AM EDT - info: [main/docker-create-machine] Detecting operating system of created instance... Apr 6, 2017, 9:26 AM EDT - info: [main/docker-create-machine] Waiting for SSH to be available... Apr 6, 2017, 9:26 AM EDT - info: [main/docker-create-machine] Detecting the provisioner... Apr 6, 2017, 9:26 AM EDT - info: [main/docker-create-machine] Provisioning with boot2docker... Apr 6, 2017, 9:26 AM EDT - info: [main/docker-create-machine] Copying certs to the local machine directory... Apr 6, 2017, 9:26 AM EDT - info: [main/docker-create-machine] Copying certs to the remote machine... Apr 6, 2017, 9:26 AM EDT - info: [main/docker-create-machine] Setting Docker configuration on the remote daemon... Apr 6, 2017, 9:26 AM EDT - info: [main/docker-create-machine] Checking connection to Docker... Apr 6, 2017, 9:26 AM EDT - info: [main/docker-create-machine] Docker is up and running! Apr 6, 2017, 9:26 AM EDT - info: [main/docker-create-machine] To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine env local-by-flywheel Apr 6, 2017, 9:26 AM EDT - info: [main/docker-create-machine] Created Docker Machine. Apr 6, 2017, 9:26 AM EDT - info: [docker-import-image] Checking for Local Docker Image... Apr 6, 2017, 9:26 AM EDT - info: [main/set-docker-env] Getting Docker Machine env.

$ docker --version Docker version 17.03.1-ce, build c6d412e

5

I’ve now tried doing a complete uninstall and re-install. Stuck at the same place.

6

I found several other posts which seem to be about the same thing or had the same symptoms. In one post, Clay suggests providing details for a file from /Library/Application Support/Local by Flywheel/.

Some things in that folder include:

  • site-statuses.json - This has a list of hashes
  • sites.json - This has all my old sites listed, each hash appears in the json
  • router/routes and router/certs contain data from previous install
  • blueprints - a couple blueprints show up here
  • ssh-entry - several things there

I’m wondering if because these exist, are they interfering with the install since the VirtualBox files were removed. I’d love to get someone from Flywheel to give input. I have a bunch of stuff in Time Machine but it started to act flaky and have moved to a new drive this week. I’ll see if I can recover anything from that. It’s worth trying.

7

Here is what finally did it for me - I wasn’t getting any error about multiple network adapters using the same IP but it kept coming up when I did a search about VB issues so I went in and checked and low and behold, there were 9 of them. I removed all but one and then Local finally installed.

So Virtual Box > Preferences > Network > Host Only Adapters.

Worth a shot since it worked for me!

1 Like
8

Hello, while it is running, could you test check your active docker instances in the terminal?

$ docker-machine ls

which should return a table that looks like this

NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS local-by-flywheel * virtualbox Running tcp://192.168.85.100:2376 v1.13.0

I’m curious if under ACTIVE, it shows the * or if it appears as -.

Thanks for your comment on Host Only Adapters. I’d tried that in the past with no resolution, but I’ll check it again.

9

Mine shows a - (as opposed to a *)

local-by-flywheel - virtualbox Running tcp://192.168.75.100:2376

10

Would be nice to get some actual support from Flywheel. This is really sad.

11

Thank you for checking that Docker value. Docker is likely not the cause of the problem. VirtualBox is working fine. I believe the problem is caused by MySQL.

All I can say is I’ve lost 20 projects. I am migrating projects to MAMP Pro, although to be honest, I’ve never been a huge fan of that tool. I believe Local is a much better application, at least when it is working. :slight_smile:

Thanks for checking in. I will post progress comments here.

12

Greg,

I’m very sorry for the trouble you’ve had with Local.

There isn’t anything glaringly obvious in the log file you have provided.

Do you have an up to date log you can provide?

Also, your projects should still be safe inside the sites folder. Local automatically backs up the database to app/sql every time the site is stopped.

13

Clay, thanks so much for dropping by; I admire your efforts to support everyone.

I apologize for characterizing that I lost those sites. I know I have the files but I was unclear if I could migrate the data to MAMP instances. I was unhappy with my situation. According to what you are saying each site’s data is in a backup location. I enjoy using Local and hope the problem I am having can be improved.

The log:
local-by-flywheel.log (1.1 MB)

The last line is: Apr 11, 2017, 1:49 PM EDT - info: [main/set-docker-env] Getting Docker Machine env.

machine.json file
{ "name": "pressmatic", "image": "pressmatic" }

Does this setting in VirtualBox look suspicious?

local-by-flywheel_-_Display.png659×511 62.5 KB

14

Hi Greg,

I think your thought with machine.json is it! I would delete machine.json and then let Local install again. You may have to delete the VM from VirtualBox.

Thanks,
Clay

1 Like
15

What do you know? It worked!

Problem Solved.

1 Like