- Notifications
You must be signed in to change notification settings - Fork303
Closed
Description
- Fresh install on Windows 10.
- Virtual machine "Moby" created successfully in Hyper-V and is able to start successfully.
- Tray application states "Docker is up and running!".
Expected behavior
- Issue a "docker images" at command prompt
- docker should return an (empty) list of images.
Actual behavior
- Issue a "docker images" at command prompt
- an error message is presented stating
"could not read CA certificate "C:\\Users\\...\\.docker\\machine\\machines\\default\\ca.pem": open C:\Users\...\.docker\machine\machines\default\ca.pem: The system cannot find the path specified."
(*note the "..." in the path is my username for my home directory)
I'd expect that the default docker-machine would automatically generate certificates in the correct location. Instead ...\.docker\machine\machines is empty.
Information
Diagnostic ID from "Diagnose & Feedback" in the menu.
A diagnostic was uploaded with id: 922D6223-5E7B-4382-9261-2357D39E22AC/2018-02-23_09-04-38host distribution and version (Windows version, build number, etc)
Windows version: Windows 10 Enterprise
OS Build: 14393.2035
Version: 1607
Docker Version: Version 17.12.0-ce-win47 (15139)
Steps to reproduce the behavior
- Download and run (elevated) "Docker for Windows Installer.exe" (MD5: 8427cee2e9ee0c2c342e0ce8747c4217 )
- After installation, execute "Docker for Windows" shortcut on desktop (elevated).
- Wait until dialog pops up saying "Docker is running!".
- Open PowerShell and type 'docker images'
- Sit and stare the the error message for a moment, and then go on a hunt for missing certificates...