profile
viewpoint

mat007/turtle 35

C++ mock object library for Boost

mat007/go-msi 7

MSI package creation tool

mat007/brique 3

Build tool for Go projects.

jeanlaurent/stupid 1

A stupid tool to help write more portable Makefile.

mat007/pony 1

Go library for building desktop applications by combining Javascript, a web browser and native GUI components.

jdrouet/marionette 0

🛠 tool to build a monorepo like if it was a multi repo project

mat007/ace-builds 0

Packaged version of Ace code editor

mat007/app 0

Make your Docker Compose applications reusable, and share them on Docker Hub

mat007/cli 0

The Docker CLI

issue commentmat007/turtle

Roadmap for C++14

Yes I think both are fine: C++14 and one PR.

Thanks for doing this!

Flamefire

comment created time in a day

Pull request review commentdocker/docker.github.io

Publish the latest updates from master

 For more information, see: #### Proxies  Docker Desktop detects HTTP/HTTPS Proxy Settings from macOS and automatically-propagates these to Docker and to your containers. For example, if you set your+propagates these to Docker. For example, if you set your proxy settings to `http://proxy.example.com`, Docker uses this proxy when pulling containers. -When you start a container, your proxy settings propagate into the containers.-For example:+Your proxy settings, however, will not be propagated into the containers you start.+If you wish to set the proxy settings for your containers, you need to define+environment variables for them, just like you would do on Linux, for example:

Or did we not do so on Docker Desktop?

Maybe we did at some point (before my time), but it’s not the case anymore as I can’t find anything in the code base.

We should probably link to that section to explain how to set these proxies automatically for docker run and docker build

Ah good point!

usha-mandya

comment created time in 4 days

PR opened docker/docker.github.io

Update index.md

<!--Thanks for your contribution. See CONTRIBUTING for this project's contribution guidelines. Remove these comments as you go.

DO NOT edit files and directories listed in _data/not_edited_here.yaml.
These are maintained in upstream repos and changes here will be lost.

Help us merge your changes more quickly by adding details and setting metadata
(such as labels, milestones, and reviewers) over at the right-hand side.-->

Proposed changes

The proxies set in the Docker Desktop settings are actually not propagated in the containers automatically. The rationale being that we want the same UX on Windows/Mac and as on Linux.

Related issues (optional)

#10890

<!--Refer to related PRs or issues: #1234, or 'Fixes #1234' or 'Closes #1234'. Or link to full URLs to issues or pull requests in other Github projects -->

+7 -10

0 comment

1 changed file

pr created time in 4 days

push eventmat007/docker.github.io

Mathieu Champlon

commit sha e3793bbed4fb5e85b32ac0c8dbb5eaf7d6d97967

Update index.md The proxies set in the Docker Desktop settings are actually not propagated in the containers automatically. The rationale being that we want the same UX on Windows/Mac and as on Linux. Related to https://github.com/docker/docker.github.io/pull/10890

view details

push time in 4 days

push eventmat007/docker.github.io

Mathieu Champlon

commit sha c08bf337d36095204c7dfa31a9d43d4e70b61089

Correct proxies documentation for Docker Desktop (mac) The proxies set in the Docker Desktop settings are actually not propagated in the containers automatically. The rationale being that we want the same UX on Windows/Mac and as on Linux. Related to https://github.com/docker/docker.github.io/pull/10890

view details

push time in 4 days

issue closeddocker/for-win

Docker Version --format no longer support shorthand '-f' (channel:ee version:2.3.2.0 46268)

the following command return error.

docker version -f "{{.Server.Os}}"

Error: unknown shorthand flag: 'f' in -f

But this is fine.

docker version --format "{{.Server.Os}}" windows

image

closed time in 5 days

hsiungw

issue closeddocker/kitematic

jellyfin

Expected behavior

Actual behavior

Information about the Issue

Steps to reproduce the behavior

  1. ...
  2. ...
  • [ ]

  • [ ]

closed time in 9 days

mehmetnoor

Pull request review commentdocker/docker.github.io

Add Desktop 2.3.2.0 release notes

 This page contains information about Docker Desktop Edge releases. Edge releases For information about Stable releases, see the [Stable release notes](release-notes.md). For Docker Desktop system requirements, see [What to know before you install](install.md#what-to-know-before-you-install). +## Docker Desktop Community 2.3.2.0+2020-06-25++> [Download](https://desktop.docker.com/mac/edge/BUILDnumber/Docker.dmg)

Build number is going to be 46268.

usha-mandya

comment created time in 10 days

issue closedmat007/turtle

New Release ??

Last release (1.3.1) is one years old (7 Mar 2019). Any plan to do a new one ? Many commit since the last one.

*** Release early, release often ***

closed time in 16 days

ledocc

issue commentmat007/turtle

New Release ??

Done! Thanks.

ledocc

comment created time in 16 days

created tagmat007/turtle

tagv1.3.2

C++ mock object library for Boost

created time in 16 days

release mat007/turtle

v1.3.2

released time in 16 days

push eventmat007/turtle

Mathieu Champlon

commit sha bbe01e6d9d21ff7075aba782434185a8339d44dd

Updated changelog for 1.3.2

view details

push time in 16 days

fork mat007/rebase

GitHub Action to automatically rebase PRs

fork in 18 days

fork mat007/github-releases-notifier

Receive Slack notifications for new releases of your favorite software on GitHub.

fork in 20 days

issue commentmat007/turtle

New Release ??

Yes, good point, I need to find a bit of time to look back into how to do it 😬

ledocc

comment created time in 20 days

issue commentdocker/for-win

files randomly not found in volume mounted from Win10 host to Linux container

It’s a bit hard to investigate without neither reproduction steps nor a diagnostics bundle (Troubleshoot window from the systray menu).

mdledoux

comment created time in 24 days

issue closeddocker/for-win

failed during hnsCallRawResponse: hnsCall failed in Win32: An adapter was not found. (0x803b0006)

<!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [ x ] I have tried with the latest version of my channel (Stable or Edge)
  • [ x ] I have uploaded Diagnostics
  • Diagnostics ID: A60B047F-98F8-483D-9A5A-006030FCCD02/20200610023046

Expected behavior

Been able to run the service

Actual behavior

The service wont run and the task will send log the following error: failed during hnsCallRawResponse: hnsCall failed in Win32: An adapter was not found. (0x803b0006)

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible? Yes
  • Is the problem new? I am not sure, since this is the first time that I try to use docker services (windows containers)
  • Did the problem appear with an update? Same as above
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version:10.0.19041 Build 19041
  • Docker Desktop Version: I tried using the 2.3.1.0 (edge) and 2.3.03(stable). Same outcome.
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: I am using it on my local PC. Tried turning on/off WSL2 and same results

Steps to reproduce the behavior

  1. ... docker swarm init --advertise-addr 192.168.0.92
  2. ... docker create network -d overlay my-overlay
  3. ... docker run -d -p 8000:80 --name my-running-site mcr.microsoft.com/windows/servercore/iis . I am able to have iis running on port 8000 without any issues.
  4. ... docker service create --name web --endpoint-mode dnsrr --publish mode=host,target=8000 --network my-overlay --constraint 'node.labels.os==windows' mcr.microsoft.com/windows/servercore/iis
  5. ... docker service ps web --no-trunc wsdxwby7g2va0gvsfo3ghdfen web.1 mcr.microsoft.com/windows/servercore/iis:latest@sha256:efca6c1d6af873ef75997a8331d6b1e0677cab38f14002de9ca820940b75785f roller Ready Rejected 2 seconds ago "failed during hnsCallRawResponse: hnsCall failed in Win32: An adapter was not found. (0x803b0006)" pp6ocb9zmtx5ei3riie8a97s0 \_ web.1 mcr.microsoft.com/windows/servercore/iis:latest@sha256:efca6c1d6af873ef75997a8331d6b1e0677cab38f14002de9ca820940b75785f roller Shutdown Rejected 7 seconds ago "failed during hnsCallRawResponse: hnsCall failed in Win32: An adapter was not found. (0x803b0006)" zp1pnwqwcq1s85enaz4qm7ilt \_ web.1 mcr.microsoft.com/windows/servercore/iis:latest@sha256:efca6c1d6af873ef75997a8331d6b1e0677cab38f14002de9ca820940b75785f roller Shutdown Rejected 12 seconds ago "failed during hnsCallRawResponse: hns

closed time in 24 days

KhimairaCrypto

issue commentdocker/for-win

failed during hnsCallRawResponse: hnsCall failed in Win32: An adapter was not found. (0x803b0006)

This does not look like an issue with the Docker Desktop application itself but with the upstream docker windows container implementation so I'm closing this issue. Could you please open an issue on https://github.com/moby/moby instead as that is the more appropriate place? Sorry, I would move it myself, but I can't because it's in a different org (it's moby not docker).

KhimairaCrypto

comment created time in 24 days

issue commentdocker/for-win

Docker commands are very slow on Windows

Maybe related to https://github.com/docker/cli/issues/2420 It’s just been fixed in docker/cli so not yet available in Desktop though.

jasonmcboyd

comment created time in 24 days

issue commentdocker/for-win

Unable to mount directory using pwd or bash path

@rfay I think we fixed this while addressing another issue a few days ago, it seems to be working properly with our latest master build:

$ docker run -v "//c/Users/mathi:/junkhome"  --rm busybox sh -c "df /junkhome"
Filesystem           1K-blocks      Used Available Use% Mounted on
drvfs                485856252 403488712  82367540  83% /junkhome

I can share a link to download a build if you want.

othercorey

comment created time in a month

issue closeddocker/for-win

Unable to mount host folder after update to latest version

I am using this technique (see wiki) to "create" drive D: on my single-volume Windows 10 NB. It means there exists disk D: on my computer, but it is actually pointing to C:\DISK_D. After upgrade to the latest Docker Desktop Community 2.3.0.3 (not sure from what version) I am no longer able to mount host folders from disk D: while there is no problem to mount folders from disk C:

Not sure if this is related, but docker run -it --rm -v /host_mnt/:/xyz alpine:3.11 ls -la /xyz shows only folder c to me.

closed time in a month

mshgh

issue commentdocker/for-win

Unable to mount host folder after update to latest version

Thanks, closing this one.

mshgh

comment created time in a month

issue commentdocker/for-win

[Windows container] Cannot open cli from dashboard

Thanks for the report, I have created an internal ticket to fix the issue.

stefanoPrimo

comment created time in a month

issue commentdocker/for-win

Docker desktop for windows 2.3.0.3 breaks MariaDB alter table again

Running compose with the compose file you provided seems to be working fine for me, do I need to do something else to trigger the issue?

Daemach

comment created time in a month

issue commentdocker/for-win

docker command line mount points dont resolve relative paths correctly

Closing as this has now been released on both channels, thanks!

chadmccune

comment created time in a month

issue closeddocker/for-win

docker command line mount points dont resolve relative paths correctly

https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [X ] I have tried with the latest version of my channel (Stable or Edge)
  • [ ] I have uploaded Diagnostics
  • Diagnostics ID:

Expected behavior

When passing a mount path like c:\somedirectory\someotherdirectory\..\upone\tohere previous versions followed the ..\ correctly. Docker Desktop update 2.20.3 (42716) installed today no longer has this behavior

Actual behavior

It now fails with: "Error response from daemon: file does not exist."

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?: yes
  • Is the problem new?: yes
  • Did the problem appear with an update?: yes
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version: 1903 (18362.535)
  • Docker Desktop Version: 2.2.0.3 (42716)
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM:no

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. mkdir \mysub
  2. mkdir \mysub\sub1
  3. mkdir \mysub\sub2
  4. docker run -it --mount=type=bind,source=c:\mysub\sub2..\sub1,target=/sub1 ubuntu bash

I use this functionality in some powershell scripts that mount to a subfolder above where the script is ran so i'll do something like $myroot = $PSScriptRoot $mountpath = "$($myroot)..\myfolder" and then use $mountpath in my command line.

I've worked around the issue by adding another line to my script, but it requires me to change all my scripts.

$mountpath = Resolve-Path $mountpath

closed time in a month

chadmccune

issue commentdocker/for-win

Shared Drives does not appear in settings for Linux Containers Mode

So when we say a linux container is running on a Win 2004 it is actually working on WSL2? Then it would mean that we have drive access by default.

Yes.

Is it possible for me to check from within the container if I can read/write to a windows directory?

I guess you can try and touch a file?

It was my understanding that a Linux container on a Win host would have an option (Share Drive) so that the linux container can access the windows directory... Perhaps you can clarify or point me in the right direction?

You need to mount a folder when running the container, see for instance https://docs.docker.com/storage/bind-mounts/

baaridunnasr

comment created time in a month

issue closeddocker/for-win

Docker Issue while installing in Windows 10 pro

<!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation -->

<!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [ ] I have tried with the latest version of my channel (Stable or Edge)
  • [ ] I have uploaded Diagnostics
  • Diagnostics ID:

Expected behavior

Actual behavior

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?
  • Is the problem new?
  • Did the problem appear with an update?
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version:
  • Docker Desktop Version:
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM:

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. ...
  2. ...

closed time in a month

Sibhi8690

issue commentdocker/for-win

Docker Issue while installing in Windows 10 pro

We're closing this issue because it doesn't contain enough information for us to investigate the problem. If you'd like us to investigate further, could you please open a fresh issue with a more detailed description of the problem and a diagnostic id, following the steps at https://docs.docker.com/docker-for-windows/troubleshoot?

Sibhi8690

comment created time in a month

issue commentdocker/for-win

files randomly not found in volume mounted from Win10 host to Linux container

@manojkdi how can I reproduce this? If you had a simple docker run command or a Dockerfile that shows the problem that would greatly help. Thanks!

mdledoux

comment created time in a month

issue commentdocker/for-win

Unable to mount host folder after update to latest version

This looks like the same as #5792?

mshgh

comment created time in a month

issue closeddocker/for-win

Docker Desktop crashes when switching to Linux Container

In docker Desktop (running on a Windows 10 1903 VM), when i switch to Linux Container, It crashes.

  • Diagnostics ID: E6CB342D-D95D-43C2-98F8-D381E58CE177/20200605162203

Expected behavior

When switching to Linux Container, it should work.

Actual behavior

It crashes

  • Windows Version: Window 10 1903

  • Docker Desktop Version: 2.3.0.3 (45519)

  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: Yes, running Docker desktop on a windows VM.

Steps to reproduce the behavior

This is a brand new install. On a newly provisioned VM, I installed docker desktop and switched to linux container. That's it.

closed time in a month

garunachalam-btig

issue commentdocker/for-win

Docker Desktop crashes when switching to Linux Container

Docker Desktop is not supported in a virtualised environment. It might work or it might not, but it's out of our control, it depends on whether the outer virtual machine supports nested virtualisation. For more information see https://docs.docker.com/docker-for-windows/troubleshoot/#running-docker-desktop-in-nested-virtualization-scenarios.

garunachalam-btig

comment created time in a month

issue closeddocker/for-win

Docker deamon is not running, unable to start

Running docker version returns: error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.40/version: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.

Running the command from both windows console and powershelll with elevated permissions. <!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation -->

<!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [ ] I have tried with the latest version of my channel (Stable or Edge)
  • [ ] I have uploaded Diagnostics
  • Diagnostics ID:

Expected behavior

Actual behavior

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?
  • Is the problem new?
  • Did the problem appear with an update?
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version:
  • Docker Desktop Version:
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM:

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. ...
  2. ...

closed time in a month

jesusoterove

issue commentdocker/for-win

Docker deamon is not running, unable to start

We're closing this issue because it doesn't contain enough information for us to investigate the problem. If you'd like us to investigate further, could you please open a fresh issue with a more detailed description of the problem and a diagnostic id, following the steps at https://docs.docker.com/docker-for-windows/troubleshoot?

jesusoterove

comment created time in a month

issue closeddocker/for-win

Random moment error

<!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation -->

<!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [ ] I have tried with the latest version of my channel (Stable or Edge)
  • [ ] I have uploaded Diagnostics
  • Diagnostics ID:

Expected behavior

No crash

Actual behavior

Chash

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?
  • Is the problem new?
  • Did the problem appear with an update?
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version:
  • Docker Desktop Version:
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM:

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. ...
  2. ...

closed time in a month

Ar2r

issue commentdocker/for-win

Random moment error

We're closing this issue because it doesn't contain enough information for us to investigate the problem. If you'd like us to investigate further, could you please open a fresh issue with a more detailed description of the problem and a diagnostic id, following the steps at https://docs.docker.com/docker-for-windows/troubleshoot?

Ar2r

comment created time in a month

issue closeddocker/for-win

Docker.Core.HttpBadResponseException: Unhandled exception: Sequence contains no elements

<!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation -->

<!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [x] I have tried with the latest version of my channel (Stable or Edge)
  • [x] I have uploaded Diagnostics
  • Diagnostics ID: 78E091C0-5347-49E1-9046-ABBB94C848F5/20200605054204

Actual behavior

Docker.Core.HttpBadResponseException: Unhandled exception: Sequence contains no elements at Docker.Core.Logging.ClientExceptionInterceptor.<InterceptResponseAsync>d__0.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Core\Logging\ClientExceptionInterceptor.cs:line 17 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Docker.Core.Logging.LoggingMessageHandler.<SendAsync>d__4.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Core\Logging\LoggingMessageHandler.cs:line 37 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Net.Http.HttpClient.<FinishSendAsyncBuffered>d__58.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Docker.Core.BackendAPI.BackendAPIClient.<CreateHyperVVMAsync>d__10.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Core\BackendAPI\BackendAPIClient.cs:line 93 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Docker.Engines.LinuxHyperVEngine.<DoStartAsync>d__12.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Desktop\Engines\LinuxHyperVEngine.cs:line 57 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Docker.ApiServices.StateMachines.TaskExtensions.<WrapAsyncInCancellationException>d__0.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\TaskExtensions.cs:line 29 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__5.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 67 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__5.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 36 Original stacktrace: at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source) at Docker.Backend.HyperVInfrastructure.<CreateDefaultVMAsync>d__12.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV\HyperVInfrastructure.cs:line 117 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Docker.Backend.HyperVInfrastructure.<CreateOrConfigureDockerVMAsync>d__10.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV\HyperVInfrastructure.cs:line 97 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Docker.Backend.HyperV.<CreateOrConfigureAsync>d__8.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV\HyperV.cs:line 131 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Docker.Backend.HttpAPI.HyperVAPIController.<CreateVMAsync>d__7.MoveNext() in C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Backend\HttpAPI\HyperVAPIController.cs:line 35 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Threading.Tasks.TaskHelpersExtensions.<CastToObject>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ApiControllerActionInvoker.<InvokeActionAsyncCore>d__1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__5.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Dispatcher.HttpControllerDispatcher.<SendAsync>d__15.MoveNext()

Information

<!-- Please, help us understand the problem. For instance:

  • Is the problem new? yes
  • Did the problem appear with an update? no
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version: 1803 (OS Build 17134.648)
  • Docker Desktop Version: Docker version 19.03.8

closed time in a month

andremangara

issue closeddocker/for-win

WSL2 kills file performance

Just got the May 2020 Windows update that includes support for WSL2. Said yes to Docker migration to WSL2 backend and found that the new approach really kills file performance. My file-operation-heavy workload went from 2 minutes to completion to 20 minutes.

It is wonderful to have the lowered CPU/Mem usage of WSL2 but this file performance is unusable.

closed time in a month

kellytrinh

issue commentdocker/for-win

WSL2 kills file performance

Duplicate of #6742

kellytrinh

comment created time in a month

issue commentdocker/for-win

DockerDesktopVM' failed to start

If you open the Hyper-V Manager and manually start the DockerDesktopVM, does it start? If yes, does Docker Desktop run correctly afterwards?

image

mjn28

comment created time in a month

issue commentdocker/for-win

Shared Drives does not appear in settings for Linux Containers Mode

There is no need for configuring file sharing with the WSL 2 backend as the system takes care of permissions. What is the problem you are having exactly?

baaridunnasr

comment created time in a month

push eventdocker/kitematic

dependabot[bot]

commit sha 746a31781561ebe91c880d1c2a15927c35e164c3

Bump websocket-extensions from 0.1.3 to 0.1.4 Bumps [websocket-extensions](https://github.com/faye/websocket-extensions-node) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/faye/websocket-extensions-node/releases) - [Changelog](https://github.com/faye/websocket-extensions-node/blob/master/CHANGELOG.md) - [Commits](https://github.com/faye/websocket-extensions-node/compare/0.1.3...0.1.4) Signed-off-by: dependabot[bot] <support@github.com>

view details

Mathieu Champlon

commit sha eb3ee4628931549bf0c965bf3a19ce071dfa7bc6

Merge pull request #5677 from docker/dependabot/npm_and_yarn/websocket-extensions-0.1.4 Bump websocket-extensions from 0.1.3 to 0.1.4

view details

push time in a month

PR merged docker/kitematic

Bump websocket-extensions from 0.1.3 to 0.1.4 dependencies

Bumps websocket-extensions from 0.1.3 to 0.1.4. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/faye/websocket-extensions-node/blob/master/CHANGELOG.md">websocket-extensions's changelog</a>.</em></p> <blockquote> <h3>0.1.4 / 2020-06-02</h3> <ul> <li>Remove a ReDoS vulnerability in the header parser (CVE-2020-7662, reported by Robert McLaughlin)</li> <li>Change license from MIT to Apache 2.0</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/faye/websocket-extensions-node/commit/8efd0cd6e35faf9bb9cb08759be1e27082177d43"><code>8efd0cd</code></a> Bump version to 0.1.4</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/3dad4ad44a8c5f74d4f8f4efd3f9d6e0b5df3051"><code>3dad4ad</code></a> Remove ReDoS vulnerability in the Sec-WebSocket-Extensions header parser</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/4a76c75efb1c5d6a2f60550e9501757458d19533"><code>4a76c75</code></a> Add Node versions 13 and 14 on Travis</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/44a677a9c0631daed0b0f4a4b68c095b624183b8"><code>44a677a</code></a> Formatting change: {...} should have spaces inside the braces</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/f6c50aba0c20ff45b0f87cea33babec1217ec3f5"><code>f6c50ab</code></a> Let npm reformat package.json</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/2d211f3705d52d9efb4f01daf5a253adf828592e"><code>2d211f3</code></a> Change markdown formatting of docs.</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/0b620834cc1e1f2eace1d55ab17f71d90d88271d"><code>0b62083</code></a> Update Travis target versions.</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/729a4653073fa8dd020561113513bfa2e2119415"><code>729a465</code></a> Switch license to Apache 2.0.</li> <li>See full diff in <a href="https://github.com/faye/websocket-extensions-node/compare/0.1.3...0.1.4">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+3 -3

0 comment

1 changed file

dependabot[bot]

pr closed time in a month

issue commentdocker/for-win

Unable to mount directory using pwd or bash path

Did it get lost in WSL2 mode?

I don’t think we rewrite the paths in WSL 2 mode, @simonferquel ?

othercorey

comment created time in a month

issue commentdocker/for-win

Slow command execution while on slow internet

There is a range a suspicious causes described in #2131 as well.

mikesir87

comment created time in a month

issue closeddocker/for-win

Not able to open docker

<!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation -->

<!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [x] I have tried with the latest version of my channel (Stable or Edge)
  • [x] I have uploaded Diagnostics
  • Diagnostics ID:

Expected behavior

Actual behavior

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?
  • Is the problem new?
  • Did the problem appear with an update?
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version:
  • Docker Desktop Version:
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM:

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. ...
  2. ...

closed time in a month

masingh123

issue commentdocker/for-win

Not able to open docker

We're closing this issue because it doesn't contain enough information for us to investigate the problem. If you'd like us to investigate further, could you please open a fresh issue with a more detailed description of the problem and a diagnostic id, following the steps at https://docs.docker.com/docker-for-windows/troubleshoot?

masingh123

comment created time in a month

issue closeddocker/for-win

Docker desktop fails to run

I have an issue to run docker from my windows 10 professional since the new update. I uninstalled and reinstalled many times but i'm still facing this issue. You will find below, the log of fail: Version: 2.3.0.3 (45519) Channel: stable Sha1: 0356a6f23f086a8134d83ee38d99ffe55a121f02 Started on: 2020/06/04 22:39:33.376 Resources: C:\Program Files\Docker\Docker\resources OS: Windows 10 Pro Edition: Professional Id: 1809 Build: 17763 BuildLabName: 17763.1.amd64fre.rs5_release.180914-1434 File: C:\Users\rmalembe\AppData\Local\Docker\log.txt CommandLine: "C:\Program Files\Docker\Docker\Docker Desktop.exe" You can send feedback, including this log file, at https://github.com/docker/for-win/issues [22:39:33.753][GUI ][Info ] Starting... [22:39:33.827][ComponentVersions ][Info ] Edition community [22:39:33.835][ComponentVersions ][Info ] Edition community [22:39:34.393][AppMigrator ][Info ] Current version: 6. Latest version: 6 [22:39:34.433][TrackingSettings ][Info ] Crash report and usage statistics are enabled [22:39:34.441][SegmentApi ][Info ] Usage statistic: Identify [22:39:35.010][SegmentApi ][Info ] Usage statistic: appLaunched [22:39:44.445][ApplicationTemplatesTracking][Info ] Cannot list templates [22:39:44.446][SegmentApi ][Info ] Usage statistic: eventTemplatesInfo [22:39:44.448][SegmentApi ][Info ] Usage statistic: heartbeat [22:39:44.576][LoggingMessageHandler][Info ] [e7b4fe62] <BackendAPIClient start> GET http://backend/version [22:39:45.543][LoggingMessageHandler][Info ] [e7b4fe62] <BackendAPIClient end> GET http://backend/version -> 200 OK (took 965ms) [22:39:45.677][LoggingMessageHandler][Info ] [8b7a0c46] <BackendAPIClient start> GET http://backend/hyperv/vhdx-size?path=C:%5CProgramData%5CDockerDesktop%5Cvm-data%5CDockerDesktop.vhdx [22:39:45.849][LoggingMessageHandler][Info ] [8b7a0c46] <BackendAPIClient end> GET http://backend/hyperv/vhdx-size?path=C:%5CProgramData%5CDockerDesktop%5Cvm-data%5CDockerDesktop.vhdx -> 200 OK (took 172ms) [22:39:45.862][LoggingMessageHandler][Info ] [693aad0c] <BackendAPIClient start> POST http://backend/migrate/app [22:39:45.868][LoggingMessageHandler][Info ] [693aad0c] <BackendAPIClient end> POST http://backend/migrate/app -> 204 NoContent (took 6ms) [22:39:45.877][Engines ][Debug ] Starting [22:39:45.907][LoggingMessageHandler][Info ] [b5bff228] <BackendAPIClient start> POST http://backend/versionpack/enable [22:39:45.912][NpsStore ][Error ] Cannot read NPS ID: Le fichier 'C:\Users\rmalembe\AppData\Roaming\Docker.npsid' est introuvable. [22:39:46.154][LoggingMessageHandler][Info ] [b5bff228] <BackendAPIClient end> POST http://backend/versionpack/enable -> 204 NoContent (took 247ms) [22:39:47.135][NPS ][Info ] NPS User id created [22:39:47.335][GoBackendProcess ][Info ] Starting C:\Program Files\Docker\Docker\resources\com.docker.backend.exe -addr unix:\.\pipe\dockerBackendApiServer [22:39:47.881][GoBackendProcess ][Info ] Started [22:39:47.886][MutagenProcess ][Info ] Starting C:\ProgramData\Docker\cli-plugins\docker-mutagen.exe mutagen daemon run [22:39:47.915][MutagenProcess ][Info ] Started [22:39:47.929][EngineStateMachine][Debug ] sending state Docker.ApiServices.StateMachines.StartTransition to state change sink [22:39:47.930][EngineStateMachine][Debug ] State Docker.ApiServices.StateMachines.StartTransition sent to state change sink [22:39:47.937][EngineStateListener][Debug ] received state Docker.ApiServices.StateMachines.StartTransition from LinuxHyperV [22:39:47.948][EngineStateNotificationRecorder][Debug ] Registered state {"State":"starting","Mode":"linux","date":1591303187} [22:39:47.949][SystrayNotifications][Info ] Docker is starting [22:39:49.456][MutagenProcess ][Info ] [forwarding] Looking for existing sessions [22:39:49.456][MutagenProcess ][Info ] [forwarding] Session manager initialized [22:39:49.456][MutagenProcess ][Info ] [sync] Looking for existing sessions [22:39:49.456][MutagenProcess ][Info ] [sync] Session manager initialized [22:39:50.974][LoggingMessageHandler][Info ] [1271f2ce] <BackendAPIClient start> POST http://backend/dns/refresh-hosts [22:39:51.429][LoggingMessageHandler][Info ] [1271f2ce] <BackendAPIClient end> POST http://backend/dns/refresh-hosts -> 204 NoContent (took 454ms) [22:39:51.433][LinuxHyperVEngine ][Info ] Stopping watching for host power events [22:39:51.437][LoggingMessageHandler][Info ] [f927e18a] <BackendAPIClient start> POST http://backend/hyperv/stop [22:39:51.557][LoggingMessageHandler][Info ] [f927e18a] <BackendAPIClient end> POST http://backend/hyperv/stop -> 204 NoContent (took 119ms) [22:39:51.594][VpnKitBridge ][Info ] Starting C:\Program Files\Docker\Docker\resources\vpnkit-bridge.exe --addr listen://00000000-0000-0000-0000-000000000000/000007CF-FACB-11E6-BD58-64006A7986D3 host [22:39:51.919][VpnKitBridge ][Info ] Started [22:39:51.991][LoggingMessageHandler][Info ] [659f5cc3] <Server start> GET http://unix/versions [22:39:52.188][LoggingMessageHandler][Info ] [659f5cc3] <Server end> GET http://unix/versions -> 200 OK (took 196ms) [22:39:52.940][VpnKitBridge ][Info ] listening on listen://00000000-0000-0000-0000-000000000000/000007CF-FACB-11E6-BD58-64006A7986D3... [22:39:52.940][VpnKitBridge ][Info ] waiting for connection on listen://00000000-0000-0000-0000-000000000000/000007CF-FACB-11E6-BD58-64006A7986D3... [22:39:53.942][IsoConfig ][Info ] Generating CA Cert Bundle [22:39:53.998][IsoConfig ][Info ] CA Cert Bundle Generated [22:39:54.008][GoBackendProcess ][Info ] ⇨ http server started on \.\pipe\dockerVpnKitControl [22:39:54.072][GoBackendProcess ][Info ] started port-forwarding control server on \\.\pipe\dockerVpnKitControl [22:39:54.074][GoBackendProcess ][Info ] listening on unix:\\.\pipe\dockerVpnkitData for data connection [22:39:54.081][GoBackendProcess ][Info ] enabling filesystem caching [22:39:54.081][GoBackendProcess ][Info ] filesystem exports are: (2) [22:39:54.086][GoBackendProcess ][Info ] volume control server listening on \\.\pipe\dockerVolume [22:39:54.090][GoBackendProcess ][Info ] filesystem server listening on 00000000-0000-0000-0000-000000000000:00001003-facb-11e6-bd58-64006a7986d3 [22:39:54.090][GoBackendProcess ][Info ] file ownership will be determined by the calling user ("fake owner" mode) [22:39:54.090][GoBackendProcess ][Info ] using mfsymlinks [22:39:54.104][GoBackendProcess ][Info ] ⇨ http server started on \.\pipe\dockerBackendApiServerForGuest [22:39:54.114][GoBackendProcess ][Info ] ⇨ http server started on \.\pipe\dockerBackendApiServer [22:39:54.983][LoggingMessageHandler][Info ] [114d0fa3] <BackendAPIClient start> POST http://backend/hyperv/create [22:39:55.217][LoggingMessageHandler][Info ] [114d0fa3] <BackendAPIClient end> POST http://backend/hyperv/create -> 500 InternalServerError (took 234ms) [22:39:55.233][LinuxHyperVEngine ][Info ] Stopping watching for host power events [22:39:55.233][LoggingMessageHandler][Info ] [df9be478] <BackendAPIClient start> POST http://backend/hyperv/stop [22:39:55.248][LoggingMessageHandler][Info ] [df9be478] <BackendAPIClient end> POST http://backend/hyperv/stop -> 204 NoContent (took 15ms) [22:39:55.260][VpnKitBridge ][Info ] Killing existing vpnkit-bridge with PID 13724 [22:39:55.289][LoggingMessageHandler][Info ] [fe18baa8] <BackendAPIClient start> POST http://backend/windowsfeatures/check [22:39:57.189][LoggingMessageHandler][Info ] [fe18baa8] <BackendAPIClient end> POST http://backend/windowsfeatures/check -> 200 OK (took 1900ms) [22:39:57.198][LoggingMessageHandler][Info ] [e2b78685] <BackendAPIClient start> GET http://backend/hyperv/check-virtualization [22:39:57.234][LoggingMessageHandler][Info ] [e2b78685] <BackendAPIClient end> GET http://backend/hyperv/check-virtualization -> 204 NoContent (took 36ms) [22:39:57.235][LoggingMessageHandler][Info ] [2d8b4d97] <BackendAPIClient start> POST http://backend/dns/refresh-hosts [22:39:57.286][LoggingMessageHandler][Info ] [2d8b4d97] <BackendAPIClient end> POST http://backend/dns/refresh-hosts -> 204 NoContent (took 51ms) [22:39:57.286][LinuxHyperVEngine ][Info ] Stopping watching for host power events [22:39:57.286][LoggingMessageHandler][Info ] [2b87595b] <BackendAPIClient start> POST http://backend/hyperv/stop [22:39:57.302][LoggingMessageHandler][Info ] [2b87595b] <BackendAPIClient end> POST http://backend/hyperv/stop -> 204 NoContent (took 15ms) [22:39:57.317][VpnKitBridge ][Info ] Starting C:\Program Files\Docker\Docker\resources\vpnkit-bridge.exe --addr listen://00000000-0000-0000-0000-000000000000/000007CF-FACB-11E6-BD58-64006A7986D3 host [22:39:57.334][VpnKitBridge ][Info ] Started [22:39:57.334][IsoConfig ][Info ] Generating CA Cert Bundle [22:39:57.370][IsoConfig ][Info ] CA Cert Bundle Generated [22:39:57.533][VpnKitBridge ][Info ] listening on listen://00000000-0000-0000-0000-000000000000/000007CF-FACB-11E6-BD58-64006A7986D3... [22:39:57.535][VpnKitBridge ][Info ] waiting for connection on listen://00000000-0000-0000-0000-000000000000/000007CF-FACB-11E6-BD58-64006A7986D3... [22:39:59.902][LoggingMessageHandler][Info ] [c86db2c9] <BackendAPIClient start> POST http://backend/hyperv/create [22:39:59.953][LoggingMessageHandler][Info ] [c86db2c9] <BackendAPIClient end> POST http://backend/hyperv/create -> 500 InternalServerError (took 50ms) [22:39:59.953][LinuxHyperVEngine ][Info ] Stopping watching for host power events [22:39:59.953][LoggingMessageHandler][Info ] [c09eb4af] <BackendAPIClient start> POST http://backend/hyperv/stop [22:39:59.972][LoggingMessageHandler][Info ] [c09eb4af] <BackendAPIClient end> POST http://backend/hyperv/stop -> 204 NoContent (took 18ms) [22:39:59.979][VpnKitBridge ][Info ] Killing existing vpnkit-bridge with PID 12800 [22:39:59.993][EngineStateMachine][Debug ] sending state Docker.ApiServices.StateMachines.FailedToStartState to state change sink [22:39:59.993][EngineStateMachine][Debug ] State Docker.ApiServices.StateMachines.FailedToStartState sent to state change sink [22:39:59.993][EngineStateListener][Debug ] received state Docker.ApiServices.StateMachines.FailedToStartState from LinuxHyperV [22:39:59.993][EngineStateNotificationRecorder][Debug ] Registered state {"State":"failed to start","Mode":"linux","date":1591303199} [22:39:59.994][SystrayNotifications][Error ] Unhandled exception: La séquence ne contient aucun élément. [22:40:00.050][GUI ][Info ] Sending Bugsnag report 2c04e7e8-2f6f-4470-9db9-fd70ddf8d2ad... [22:40:00.184][GUI ][Info ] Bugsnag report 2c04e7e8-2f6f-4470-9db9-fd70ddf8d2ad sent [22:40:00.185][SegmentApi ][Info ] Usage statistic: eventCrash [22:40:00.190][Diagnostics ][Warning] Starting to gather diagnostics as User : 'C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe' gather. [22:40:00.386][Engines ][Error ] Start failed with Unhandled exception: La séquence ne contient aucun élément. à Docker.Core.Logging.ClientExceptionInterceptor.<InterceptResponseAsync>d__0.MoveNext() dans C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Core\Logging\ClientExceptionInterceptor.cs:ligne 17 --- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée --- à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) à Docker.Core.Logging.LoggingMessageHandler.<SendAsync>d__4.MoveNext() dans C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Core\Logging\LoggingMessageHandler.cs:ligne 37 --- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée --- à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) à System.Net.Http.HttpClient.<FinishSendAsyncBuffered>d__58.MoveNext() --- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée --- à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) à Docker.Core.BackendAPI.BackendAPIClient.<CreateHyperVVMAsync>d__10.MoveNext() dans C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Core\BackendAPI\BackendAPIClient.cs:ligne 93 --- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée --- à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) à Docker.Engines.LinuxHyperVEngine.<DoStartAsync>d__12.MoveNext() dans C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Desktop\Engines\LinuxHyperVEngine.cs:ligne 57 --- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée --- à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) à Docker.ApiServices.StateMachines.TaskExtensions.<WrapAsyncInCancellationException>d__0.MoveNext() dans C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\TaskExtensions.cs:ligne 29 --- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée --- à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) à Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__5.MoveNext() dans C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:ligne 67 --- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée --- à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() à Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__5.MoveNext() dans C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:ligne 36 --- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée --- à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) à Docker.ApiServices.StateMachines.EngineStateMachine.<StartAsync>d__14.MoveNext() dans C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\EngineStateMachine.cs:ligne 72 --- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée --- à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) à Docker.Engines.Engines.<StartAsync>d__24.MoveNext() dans C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Desktop\Engines\Engines.cs:ligne 109) [22:40:00.778][GoBackendProcess ][Info ] external: GET /events 200 "Go-http-client/1.1" "
[22:40:00.779][GoBackendProcess ][Info ] external: GET /forwards/list 200 "Go-http-client/1.1" "
[22:40:00.780][GoBackendProcess ][Info ] mutagen sync list --output json [22:40:00.990][GoBackendProcess ][Info ] mutagen C:\ProgramData\Docker\cli-plugins\docker-mutagen.exe mutagen sync list --output json: null\n [22:40:00.991][GoBackendProcess ][Info ] external: GET /sync 200 "Go-http-client/1.1" "\

closed time in a month

malembetirick

issue commentdocker/for-win

Docker desktop fails to run

Duplicate of #6007

malembetirick

comment created time in a month

issue closeddocker/for-win

can not start docker desktop ver 2.2.0.3(42716)

System.InvalidOperationException: Sequence contains no matching element at System.Linq.Enumerable.First[TSource](IEnumerable1 source, Func2 predicate) at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters) at Docker.WPF.BackendClient.Version() at Docker.WPF.BackendClient.CheckVersion() at Docker.WPF.BackendClient.CheckService(String action) at Docker.WPF.BackendClient.SendMessage(String action, Object[] parameters) at Docker.ApiServices.TaskQueuing.TaskQueue.<>c__DisplayClass18_0.<.ctor>b__1()

closed time in a month

quyennguyenvan

issue commentdocker/for-win

can not start docker desktop ver 2.2.0.3(42716)

Duplicate of #6007

quyennguyenvan

comment created time in a month

issue closeddocker/for-win

Can we run docker on a VM with Windows10 and WSL1? (nested virtualization - host is a VM & ubuntu VM is created through hyper-v for docker)

log.txt <!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation -->

<!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [ ] I have tried with the latest version of my channel (Stable or Edge) - stable
  • [ ] I have uploaded Diagnostics
  • Diagnostics ID: CF13FEC2-6CD2-428A-9157-B6C8AE565B29/20200604114726

Expected behavior

Actual behavior

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible? - Yes
  • Is the problem new? Yes
  • Did the problem appear with an update? NO
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version: Windows 10 Enterprise , VM , build : 10.0.17763.1217
  • Docker Desktop Version:2.3.0.3
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: Yes, Windows vitual machine

Steps to reproduce the behavior

<!-- Couldn't succeeed in starting at all. A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. ...
  2. ...

closed time in a month

pingasa

issue commentdocker/for-win

Can we run docker on a VM with Windows10 and WSL1? (nested virtualization - host is a VM & ubuntu VM is created through hyper-v for docker)

Docker Desktop is not supported in a virtualised environment. It might work or it might not, but it's out of our control, it depends on whether the outer virtual machine supports nested virtualisation. For more information see https://docs.docker.com/docker-for-windows/troubleshoot/#running-docker-desktop-in-nested-virtualization-scenarios.

pingasa

comment created time in a month

issue closeddocker/for-win

lots of dns query of docker-for-desktop or docker-desktop always end in NXDOMAIN

<!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation -->

<!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [x] I have tried with the latest version of my channel (Stable or Edge)
  • [ ] I have uploaded Diagnostics
  • Diagnostics ID:

Expected behavior

Docker desktop with default options should be able to resolve dns name docker-desktop (latest versions) or (older versions) docker-for-desktop that it is trying to resolve repeatedly in the background.

We would like to know what docker-desktop/docker-for-desktop is intended to be, the kubernetes cluster created by Docker Desktop or the node of the kubernetes cluster. If it is intended as the node, how to find out its external ip.

Docker Desktop installation is already updating the /etc/hosts file on the host, and it would be best to add an entry also for docker-desktop/docker-for-desktop.

At least there should be an option to control the qurery frequency.

Actual behavior

Docker desktop installations with Kubernetes enabled generates upto 100,000 dns queries on docker-for-desktoip per day that all end up on the root dns server generating NXDOMAIN error. Latest Docker Desktop seems to be querying docker-desktop. The individual windows hosts see no ill effect, but the company dns server gets the queries from all Docker Desktop hosts and is under stress to keep up.

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?
  • Is the problem new?
  • Did the problem appear with an update?
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version: windows 10
  • Docker Desktop Version: latest and versions released in the past year, e.g., 2.0.0.3
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: no

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. install Docker Desktop, new or older versions, default configuration, then enable kubernetes
  2. check the default domain root dns server for queries on docker-for-desktop.default domains or docker-desktop.default domains that end up in NXDOMAIN, default domains are the ones configured on the installation host. Such queries are especially resource intensive to process, because it is not cached, and goes all the way to the root DNS server for the <default domain> every time, which works hard before giving up with NXDOMAIN error.

closed time in a month

wu105

issue commentdocker/for-win

lots of dns query of docker-for-desktop or docker-desktop always end in NXDOMAIN

I believe this is actually a duplicate of #5089

wu105

comment created time in a month

issue closeddocker/for-win

crashed

<!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation -->

<!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [x] I have tried with the latest version of my channel (Stable or Edge)
  • [x] I have uploaded Diagnostics
  • Diagnostics ID:

Expected behavior

Actual behavior

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?
  • Is the problem new?
  • Did the problem appear with an update?
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version:
  • Docker Desktop Version:
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM:

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. ...
  2. ...

closed time in a month

archalke

issue commentdocker/for-win

crashed

We're closing this issue because it doesn't contain enough information for us to investigate the problem. If you'd like us to investigate further, could you please open a fresh issue with a more detailed description of the problem and a diagnostic id, following the steps at https://docs.docker.com/docker-for-windows/troubleshoot?

archalke

comment created time in a month

issue commentdocker/for-win

Docker Desktop version Settings > Resources not displaying Advanced tab

@marceloavf if you’re using the WSL 2 backend (that’s the default now if your Windows version supports it), as is the case here because you have a «WSL Integration» sub-section in your screenshot, you don’t need to manually tweak the resources allocated to the VM (because there is no VM).

bilalchraibi

comment created time in a month

issue closeddocker/for-win

Changing the Disk Image Location

<!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation -->

<!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [ ] I have tried with the latest version of my channel (Stable or Edge)
  • [ ] I have uploaded Diagnostics
  • Diagnostics ID:

Expected behavior

Actual behavior

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?
  • Is the problem new?
  • Did the problem appear with an update?
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version:
  • Docker Desktop Version:
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM:

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. ...
  2. ...

closed time in a month

walter-weinmann

issue commentdocker/for-win

Changing the Disk Image Location

We're closing this issue because it doesn't contain enough information for us to investigate the problem. If you'd like us to investigate further, could you please open a fresh issue with a more detailed description of the problem and a diagnostic id, following the steps at https://docs.docker.com/docker-for-windows/troubleshoot?

walter-weinmann

comment created time in a month

issue commentdocker/for-win

Docker container port not accessible on Windows 10

Your logs are full of ICMP: destination unreachable from 192.168.65.3, do you happen to have blocked it? Could you try maybe after deactivating your firewall, just for testing if it works?

Karlheinzniebuhr

comment created time in a month

issue closeddocker/for-win

Unable to install Docker desktop on Windows 10 version 1909

I am trying to install Docker for windows and getting the following error towards the end of installation:

I am using Windows 10 Enterprise version 1909 OS build 18363.836 System type: 64-bit operating system, x64 based processor install-log.txt

Docker Desktop 2.3.0.3 Installation failed

Failed to start service: The service did not respond to the start or control request in a timely fashion at CommunityInstaller.Service.Service.<StartAsync>d__4.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at CommunityInstaller.Service.Manager.<AddServiceAsync>d__7.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at CommunityInstaller.ServiceAction.<DoAsync>d__36.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at CommunityInstaller.InstallWorkflow.<HandleD4WPackageAsync>d__29.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at CommunityInstaller.InstallWorkflow.<ProcessAsync>d__24.MoveNext()

closed time in a month

rameshkumarg

issue commentdocker/for-win

Unable to install Docker desktop on Windows 10 version 1909

Most likely a duplicate of #6091

rameshkumarg

comment created time in a month

issue commentdocker/for-win

Docker desktop for windows 2.3.0.3 breaks MariaDB alter table again

Could you tell us a bit more about how you run this? A compose file maybe?

Daemach

comment created time in a month

IssuesEvent

PR merged mat007/turtle

Remove boost deprecations 2

Fixes:

boost/test/floating_point_comparison.hpp:14:124: note: #pragma message: This header is deprecated. Use This header is deprecated. Please use <boost/test/tools/floating_point_comparison.hpp> instead. instead. boost/detail/sp_typeinfo.hpp:23:54: note: #pragma message: This header is deprecated. Use <boost/core/typeinfo.hpp> instead.

+18 -5

2 comments

2 changed files

ledocc

pr closed time in a month

PR closed mat007/turtle

Remove boost deprecations

Fixes:

boost/test/floating_point_comparison.hpp:14:124: note: #pragma message: This header is deprecated. Use This header is deprecated. Please use <boost/test/tools/floating_point_comparison.hpp> instead. instead. boost/detail/sp_typeinfo.hpp:23:54: note: #pragma message: This header is deprecated. Use <boost/core/typeinfo.hpp> instead.

+21 -4

3 comments

3 changed files

Dirk007

pr closed time in a month

push eventmat007/turtle

Dirk Faust

commit sha 45450aa6431bf75df9a1869d1be2943ec646b9f8

Remove boost deprecations Fixes: boost/test/floating_point_comparison.hpp:14:124: note: #pragma message: This header is deprecated. Use This header is deprecated. Please use <boost/test/tools/floating_point_comparison.hpp> instead. instead. boost/detail/sp_typeinfo.hpp:23:54: note: #pragma message: This header is deprecated. Use <boost/core/typeinfo.hpp> instead.

view details

Mathieu Champlon

commit sha 9dcdcf9061b929a03f188531ea5cbd530b6234ab

Merge pull request #86 from ledocc/remove_boost_deprecations Remove boost deprecations 2

view details

push time in a month

pull request commentmat007/turtle

Remove boost deprecations

Merged similar #86 addressing the same issue. Thanks!

Dirk007

comment created time in a month

issue commentdocker/for-win

Cannot enable Hyper-V service - Docker Desktop on Windows

The problem is more likely to come from Hyper-V, hence my suggestion to uninstall it, reboot, then install it again.

image

nahooshmandlik

comment created time in a month

issue closeddocker/for-win

Choosing WSL 2 backend instead of Hyper-V without Hyper-V installed

Hi! I just updated Docker and I want to use WSL 2. But after the update I clicked on 'Not now' when it prompted me whether I want to use WSL 2. Now I can't do anything, cuz settings with enabling WSL 2 are in Docker Desktop, but when I open Docker Desktop I just get the error.

image

Is there a way I can enable WSL 2 through CLI or some configuration file? I don't want to install Hyper-V just for that.

closed time in a month

Albert221

issue commentdocker/for-win

Choosing WSL 2 backend instead of Hyper-V without Hyper-V installed

You can change the "wslEngineEnabled" setting in %APPDATA%\Docker\settings.json.

Albert221

comment created time in a month

issue closeddocker/for-win

Docker Desktop Crashing Error

<!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation -->

<!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [ ] I have tried with the latest version of my channel (Stable or Edge)
  • [ ] I have uploaded Diagnostics
  • Diagnostics ID:

Expected behavior

Actual behavior

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?
  • Is the problem new?
  • Did the problem appear with an update?
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version:
  • Docker Desktop Version:
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM:

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. ...
  2. ...

closed time in a month

SteveNguyen1190

issue commentdocker/for-win

Docker Desktop Crashing Error

We're closing this issue because it doesn't contain enough information for us to investigate the problem. If you'd like us to investigate further, could you please open a fresh issue with a more detailed description of the problem and a diagnostic id, following the steps at https://docs.docker.com/docker-for-windows/troubleshoot?

SteveNguyen1190

comment created time in a month

issue commentdocker/for-win

Very high CPU and disk usage when host wakes from sleep

@paaland you may want to comment on #6947 or maybe open a different issue as I’m not sure #6947 is with WSL 2. Also you may want to check https://github.com/microsoft/WSL/issues/4166?

sgryt

comment created time in a month

issue closeddocker/for-win

Very high CPU and disk usage when host wakes from sleep

<!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation -->

<!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [x] I have tried with the latest version of my channel (Stable or Edge)
  • [x] I have uploaded Diagnostics
  • Diagnostics ID: CCF324D6-4AE6-4E76-A9AF-A4FBB6FF2B33/20200506063703

Expected behavior

Close-to-idle CPU's and disk on host after waking from sleep

Actual behavior

Very high CPU and disk usage on host after waking from sleep.

Information

Please, help us understand the problem. For instance:

  • Is it reproducible? It seems to happen each time the host wakes from prolonged sleep (in the state where I have to supply my Bitlocker password before the host OS resumes)

  • Is the problem new? Yes, I have only seen it happen after I installed and started using Docker for Windows

  • Did the problem appear with an update? No

  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. Not sure how I could provide this without shipping the laptop to you ?

  • Windows Version: Windows 10 Pro version 1909, 64bit

  • Docker Desktop Version: 2.2.0.5 (43884)

  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: Yes, in a Hyper-V guest (with nested virtualization enabled). The guest OS is the same as the host OS (Windows 10 Pro version 1909, 64bit).

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. Install Docker Desktop for Windows in a Hyper-V guest image using the OS versions mentioned above.
  2. Use a laptop for the host
  3. Configure the guest with 16GB RAM and 4 cores (on a host with 64GB RAM and 8 cores)
  4. Put the laptop to sleep
  5. Wake it up again.
  6. The vmmem.exe process on the host now consumes 50% CPU until such time that I manage to connect to the Hyper-V guest and restart Docker Desktop. This takes about 10 minutes in my case, because the CPU's in the guest VM are max'ed out.
  7. Very high disk usage on the host is also observed

closed time in a month

sgryt

issue commentdocker/for-win

Very high CPU and disk usage when host wakes from sleep

Docker Desktop is not supported in a virtualised environment. It might work or it might not, but it's out of our control, it depends on whether the outer virtual machine supports nested virtualisation. For more information see https://docs.docker.com/docker-for-windows/troubleshoot/#running-docker-desktop-in-nested-virtualization-scenarios.

sgryt

comment created time in a month

issue commentdocker/for-win

High CPU usage while Docker Desktop is running on windows

@mat007 not sure it's the same issue

You’re right, that other ticket has Docker Desktop running in a virtualized environment.

HenrikPoulsen

comment created time in a month

issue commentdocker/for-win

High CPU usage while Docker Desktop is running on windows

Is this with the WSL 2 backend? If yes maybe it’s https://github.com/microsoft/WSL/issues/4166?

HenrikPoulsen

comment created time in a month

issue closeddocker/for-win

k8s system containers visible in WSL2 bash (but not windows powershell)

<!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation -->

<!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [x] I have tried with the latest version of my channel (Stable or Edge)

Expected behavior

Doing docker ps in WSL2 (Ubuntu-18.04) with the option "Show system containers (advanced)" in the Kubernetes section in settings is off. Expected to not see any k8s system containers.

Actual behavior

All k8s system containers are visible in the output of docker ps.

Information

It seems the setting "Show system containers (advanced)" does not affect the behavior in WSL2, it only affects behavior in Windows (powershell/cmd).

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?
  • Is the problem new?
  • Did the problem appear with an update?
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version: 10
  • Docker Desktop Version: 2.3.0.3
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. Set "Show system containers (advanced)" to off.
  2. Start WSL2 terminal.
  3. Enter docker ps.
  4. Fins k8s system containers in output.

closed time in a month

jonaskello

issue commentdocker/for-win

k8s system containers visible in WSL2 bash (but not windows powershell)

Thanks for the report, closing as a duplicate of #6725

jonaskello

comment created time in a month

issue commentdocker/for-win

Cannot enable Hyper-V service - Docker Desktop on Windows

@nahooshmandlik have you tried removing Hyper-V, rebooting, then adding it back (or re-installing Docker Desktop which will do it for you)?

nahooshmandlik

comment created time in a month

issue commentdocker/for-win

Docker container port not accessible on Windows 10

Can you explain a bit more what you do?

Karlheinzniebuhr

comment created time in a month

issue commentdocker/for-win

I got this error, when clicking "open in vscode" in docker dashboard

Yes, this bug has been fixed, see

Fixed opening an application in VS Code from a WSL 2 running app

in https://docs.docker.com/docker-for-windows/release-notes/#bug-fixes-and-minor-changes

iam-notabot

comment created time in a month

issue closeddocker/for-win

Unable to Start Docker with Linux Containers on Windows 10

<!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation -->

<!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [ ] I have tried with the latest version of my channel (Stable or Edge)
  • [ ] I have uploaded Diagnostics
  • Diagnostics ID:

Expected behavior

Actual behavior

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?
  • Is the problem new?
  • Did the problem appear with an update?
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version:
  • Docker Desktop Version:
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM:

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. ...
  2. ...

closed time in a month

teafg

issue commentdocker/for-win

Unable to Start Docker with Linux Containers on Windows 10

We're closing this issue because it doesn't contain enough information for us to investigate the problem. If you'd like us to investigate further, could you please open a fresh issue with a more detailed description of the problem and a diagnostic id, following the steps at https://docs.docker.com/docker-for-windows/troubleshoot?

teafg

comment created time in a month

issue commentdocker/for-win

[WSL 1] Symlinks cause IO error on ntfs drive

We’ve fixed some file sharing bugs recently, have you tried with the latest Stable (2.3.0.3)?

greyphoenix

comment created time in a month

issue closeddocker/for-win

Issue while loading docker desktop on windows 10 Enterprise edition

<!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation -->

<!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [x] I have tried with the latest version of my channel (Stable or Edge)
  • [x] I have uploaded Diagnostics
  • Diagnostics ID:

Expected behavior

Actual behavior

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?
  • Is the problem new?
  • Did the problem appear with an update?
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version:
  • Docker Desktop Version:
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM:

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. ...
  2. ...

closed time in a month

kapilmathur

issue commentdocker/for-win

Issue while loading docker desktop on windows 10 Enterprise edition

We're closing this issue because it doesn't contain enough information for us to investigate the problem. If you'd like us to investigate further, could you please open a fresh issue with a more detailed description of the problem and a diagnostic id, following the steps at https://docs.docker.com/docker-for-windows/troubleshoot?

kapilmathur

comment created time in a month

issue commentdocker/for-win

Docker Desktop GUI won't start

Can you explain what you do exactly? Can you look at %LOCALAPPDATA%\Docker\log.txt when that happens to see if there is an error?

thomiel

comment created time in a month

issue commentdocker/for-win

Unable to switch to build/run Windows containers using Docker Desktop on Windows 10 1803

Anything in C:\ProgramData\Docker\panic.log? Do you have a dockerd.exe process running? Assuming you don’t have container or images you want to keep, you can try to quit Docker Desktop then delete C:\ProgramData\Docker and restart Docker Desktop.

seandockery

comment created time in a month

issue commentdocker/for-win

Unable to mount directory using pwd or bash path

2.3.0.3 🙂

Wops, nice catch, fixed. Thanks!

othercorey

comment created time in a month

issue closeddocker/for-win

Install error

<!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation -->

<!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [x] I have tried with the latest version of my channel (Stable or Edge)
  • [x] I have uploaded Diagnostics
  • Diagnostics ID:

Expected behavior

Actual behavior

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?
  • Is the problem new?
  • Did the problem appear with an update?
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version:
  • Docker Desktop Version:
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM:

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. ...
  2. ...

closed time in a month

joegajeckyj

issue commentdocker/for-win

Install error

We're closing this issue because it doesn't contain enough information for us to investigate the problem. If you'd like us to investigate further, could you please open a fresh issue with a more detailed description of the problem and a diagnostic id, following the steps at https://docs.docker.com/docker-for-windows/troubleshoot?

joegajeckyj

comment created time in a month

issue closeddocker/for-win

erro from diagnose&feedback

<!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation -->

<!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [ ] I have tried with the latest version of my channel (Stable or Edge)
  • [ ] I have uploaded Diagnostics
  • Diagnostics ID:

Expected behavior

Actual behavior

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?
  • Is the problem new?
  • Did the problem appear with an update?
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version:
  • Docker Desktop Version:
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM:

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. ...
  2. ...

closed time in a month

GuiLuccaDev

issue commentdocker/for-win

erro from diagnose&feedback

We're closing this issue because it doesn't contain enough information for us to investigate the problem. If you'd like us to investigate further, could you please open a fresh issue with a more detailed description of the problem and a diagnostic id, following the steps at https://docs.docker.com/docker-for-windows/troubleshoot?

GuiLuccaDev

comment created time in a month

issue commentdocker/for-win

Docker Desktop failed to start after updating Win10 to 2004

This seems to be a common problem (I have seen other similar messages with port 53 busy).

I agree, @simonferquel do you believe we could could test the port and pop a nice error message box if it’s already bound?

davidmz

comment created time in a month

more