Docker 1.13 cli gives a warning about crypto/x509

[JettJones]

Expected behavior

Docker ouput should be free of warnings (unless there's something to fix)

Actual behavior

Docker 1.13.0 provides a developer warning on every run - it is reporting a library does not exist on windows. That's not something I can fix as a user.

>docker --version
time="2017-01-24T09:45:40-08:00" level=warning msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"
Docker version 1.13.0, build 49bf474

Information

• host distribution and version (Windows version, build number, etc)
  running on windows 10 pro, Version 1607 (OS Build 14292.693)

This might be an issue from Go's system cert pool: golang/go#16736

Steps to reproduce the behavior

1. Install docker 1.13.0 on windows
2. Run docker --version (or any other command)

[dagbjorn]

I see the same issue running on Windows 10 Home, Version 1607 (OS Build 14393.693) after upgrading from Docker 1.12.6 to 1.13.0. Docker seems to work alright, but the warning is annoying.

[dgageot]

@JettJones Thanks for the report. Can I ask you to open an issue on docker/docker? I guess this is not something that can be fixed on Docker for Windows, so I'm going to close the ticket.

[Neelerak]

@#dgageot

This issue was a problem with Go and should be resolved as of 14 days ago, any chance to get a hotfix?

golang/go#16736

[raiello]

this problem still exists - does anyone have an update?

I am having this same issue on Docker Windows - not my primary environment but I am forced to use it.
$> docker --version $> time="2017-03-17T11:35:57-04:00" level=info msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows" Docker version 1.13.1, build 092cba3

Any Ideas?
As far as I can see this does not affect anything, but I get the error on every line or command UNLESS I am using docker-compose to build a file. With docker-compose I am seeing no error.

Hope this helps.

[cyberbeast]

This is irritating. Is there any fix for this at all? I used the amazonec2 driver to init a docker-swarm and since then I've been getting this stupid message and executing "docker info" returns absolutely nothing.

[voltuer]

hahaha seriously no fix in 3 months? docker pls

[raadbintareaf]

I still have the same problem !

[sandhilt]

Same here. For while, I think that a downgrade solve.