docker桌面错误:TLS配置无效(docker_tls_verify和docker_cert_path的问题)
我在Windows 10机器(v4.9.1)上安装了Docker桌面。它工作正常,直到我删除 docker 和 .docker 配置文件夹(尽可能多)。 (我现在很遗憾。)现在,我想启动我的docker-compose.yml并得到:
PS C:\test> docker-compose up -d
ERROR: TLS configuration is invalid - make sure your DOCKER_TLS_VERIFY and DOCKER_CERT_PATH are set correctly.
You might need to run `eval "$(docker-machine env default)"`
我卸载了Docker桌面并再次安装了它,但我仍然有相同的功能。 我在互联网上搜索并找到了一些这里可能的解决方案,但我想了解这个问题,因为这是我第一次使用Docker桌面。
编辑:
启动码头台式机中有一个教程电源壳命令行。 Docker-Compose在那里工作...
I installed Docker Desktop on my Windows 10 machine (v4.9.1). It worked fine until I deleted Docker and .docker configuration folders (as much as possible). (I regret it now.) Now, I want to start my docker-compose.yml and get this:
PS C:\test> docker-compose up -d
ERROR: TLS configuration is invalid - make sure your DOCKER_TLS_VERIFY and DOCKER_CERT_PATH are set correctly.
You might need to run `eval "$(docker-machine env default)"`
I uninstalled the Docker Desktop and installed it again and I still have the same.
I searched on the internet and found some possible solutions here, but I want to understand the problem because this is the first time I have used Docker Desktop.
EDIT:
There is a tutorial power shell command line in Docker Desktop after starting it. The docker-compose works there...
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
已解决:我删除了Docker_tls_verify和Docker_cert_path环境变量。这些指向删除的配置。无论如何,我现在不需要这个。
此外,我看不到Docker桌面PowerShell中的这些环境变量,因此我可以在那里工作。这让我有些困惑。我不知道为什么Docker桌面环境有所不同。过去,我在机器上安装了Docker,也许这也可能引起问题。
Solved: I removed DOCKER_TLS_VERIFY and DOCKER_CERT_PATH environment variables. These pointed to deleted configuration. Anyway, I don't need this now.
Furthermore, I couldn't see these environment variables in Docker Desktop PowerShell, thus I could work there. It confused me a bit. I don't know why the Docker Desktop environment is different. In the past I had Docker installation on my machine, maybe this also could cause problems.