Unable to create: The object already exists

[kristopher-d]

Expected behavior

Docker starts

Actual behavior

Docker Fails to start

Information

Diagnostic 628E11F1-55C2-42EF-B589-CB9259407C2C/2017-01-23_10-02-03 uploaded

Windows 10 Pro
Version 1607
Build 14393.693

Steps to reproduce the behavior

Attempt to start Docker for Win.

[gh0st]

Same problem.

[dgageot]

@kristopher-d You are currently using version 1.12.6 on Stable channel. Can you update to the latest version and tell us if it's better?

[dgageot]

Sorry, in fact you updated to 1.13. Let me check again...

[dgageot]

@kristopher-d Is it possible for you to Reset to Factory defaults?

[dgageot]

@kristopher-d any chance you could try?

[gh0st]

@dgageot for me everything is greyed out in the settings menu.

[simonferquel]

Thanks for the report. The issue should have been fixed and this should make it in next beta (beta 41).
Please make sure to update to beta41 as soon as you get prompted for it.

[JonCubed]

I'm getting this error with beta 42

diagnostic id: 41560D0B-E5AF-41B4-94BD-0C90C899004C/2017-02-11_22-59-15

OS: Windows 10 Pro
Build: 14393

[JonCubed]

@simonferquel @rneugeba @dgageot any chance you have any suggestions on how to fix this?

[dgageot]

Sorry @JonCubed we don't have a fix yet. We'll keep you posted when we have.

[jasonbivins]

@JonCubed

We're out of Beta now - can you try in one of the newer builds?

[JonCubed]

@jasonbivins I eventually fix this via a combination of uninstalling, deleting docker folders, running clean up scripts and reinstalling. Currently running on stable with no issues

[gh0st]

I’ll give it a try Monday morning. Chad Hollman

…

On Dec 10, 2017, at 16:16, Jonathan Kuleff ***@***.***> wrote: @jasonbivins I eventually fix this via a combination of uninstalling, deleting docker folders, running clean up scripts and reinstalling. Currently running on stable with no issues — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[docker-robott]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked