2.0.2 "Pressmatic data does not exist"

I’m becoming more and more hesitant on relying on Local to develop locally. It’s very frustrating when updates bash your local development environment, putting all development on hold and projects at risk.

Here’s what’s going on.

I recently updated to v.2.0.2, received a 500 error, went to Virtual Box to reset (as suggested in another forum post), now it looks like I have both a local-by-flywheel VB and pressmatic VB (?). I’m getting the Local app to open for a few seconds — then immediately close with the following errors (log below).

lLog (255 Bytes)

Can you help me target the issue here?

Update:
Added screenshots of my VirtualBox:


Update 2:
I have the app loading now, but I’m getting a “container is missing” error for all my sites.

Update 3:
After a macOS restart, we’re back to square one. I can’t get past the “Starting Local Machine” screen - if the app stays open.
log.log (6.5 KB)

Update 4:
Here’s an updated shot of my Virtual Box. Sometimes the app stays open. I still get the “Container is missing” error on all my sites. This last time I added a site to see if it would work - though I’m getting a ‘502 Bad Gateway’ error, even upon a Local Machine restart via the Help Menu.

I’m just filling in the details and keeping this up to date so we’re on the same page.

Reinstall Local 2.0.1 by overwriting Local 2.0.2.
Local 2.0.1 works.
Local 2.0.2 does not work.
Ignore the update requests until Local 2.0.3 is out.

Thanks @marianco for the follow up. I’ve done that and have the “Container is missing” notification on every site. I also set up a fresh site (to see if it works) and I get a 502 Bad Gateway error on that.

Hey Rich,

Deleting the VirtualBox VM will remove all of the Docker containers.

Please let me know if 2.0.3 helps: Local by Flywheel 2.0.3 (macOS Only)

Hi Clay,

I’m downloading 2.0.3 currently. What do you mean with the VirtualBox VM? I don’t believe I deleted anything there? Will 2.0.3 resolve the missing container issues on all my sites?

1 Like

As long as you didn’t delete the VM your containers should be fine.

You’ll need to edit that JSON file you changed in ~/Library/Application Support/Local by Flywheel to have it look for pressmatic again instead of local-by-flywheel

Ok. You’re referring to machine.json? I added the references to ‘pressmatic’ again, though now the app opens, then quits other quickly.

Hey Rich,

Can you go to ~/Library/Application Support/Local by Flywheel and remove error-reporting.json if you enabled it in the past?

This should resolve the issue of Local quitting immediately.

Thanks Clay, removing that file did resolve the quitting issue. This is what I get currently now (while it’s on “Checking System”). Should I go ahead and apply the 2.0.3 update?

Yup! I’d go ahead and apply the update.

Alrighty. I applied the update. Still hangin’ out on the Checking System view:

I then reset the Local Machine via Help:

Update:

I’m on 2.0.3 now. If I remove the machine.json file, then I can get past the “Checking System” view, although none of my site containers are resolving — and the test site I created is resulting in a 502 Bad Gateway.

Is there any way to resolve the containers that are showing up “missing” — or do I now need to rebuild and migrate all of those sites? I’m mostly concerned about all my projects that are not functioning currently.

Hey Rich,

Just wanted to let you know I’ve been looking into this issue.

1 Like

Considering the biggest concern is your existing sites, I just wanted to remind you to keep the machine set to pressmatic when trying this.

After you switch that back to pressmatic, go ahead and delete dockerode-options.json in ~/Library/Application Support/Local by Flywheel.

Once you delete dockerode-options.json, open up VirtualBox.app and right-click on pressmatic and go to “Reset”. After you see it restarting (preferably with the ASCII whale in the preview), you can re-open Local.