-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Setup-TraefikContainerForBcContainer] Provider connection error error during connect: Get \"http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/version\": open //./pipe/docker_engine: message readmode pipes not supported In the default daemon configuration on Windows #2839
Comments
We're experiencing the same issue. docker ps shows "exactly" when the problem started occuringPS C:\Users\admjtheiner> docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS
0b1064ca654d mcr.microsoft.com/businesscentral:10.0.17763.3650 "powershell -Command…" 2 minutes ago Up About a minute (unhealthy) 80/tcp, 443/tcp, 1433/tcp, 7045-7049/tcp, 7083/tcp, 8080/tcp
1717fa4da71e mcr.microsoft.com/businesscentral:10.0.17763.3650 "powershell -Command…" 5 hours ago Up 5 hours (unhealthy) 80/tcp, 443/tcp, 1433/tcp, 7045-7049/tcp, 7083/tcp, 8080/tcp
141ab654aa73 mcr.microsoft.com/businesscentral:10.0.17763.3650 "powershell -Command…" 8 hours ago Up 8 hours (unhealthy) 80/tcp, 443/tcp, 1433/tcp, 7045-7049/tcp, 7083/tcp, 8080/tcp
b1cb4ed5be48 mcr.microsoft.com/businesscentral:10.0.17763.3650 "powershell -Command…" 11 hours ago Up 11 hours (unhealthy) 80/tcp, 443/tcp, 1433/tcp, 7045-7049/tcp, 7083/tcp, 8080/tcp
72771723f0f5 mcr.microsoft.com/businesscentral:10.0.17763.3650 "powershell -Command…" 12 hours ago Up 12 hours (unhealthy) 80/tcp, 443/tcp, 1433/tcp, 7045-7049/tcp, 7083/tcp, 8080/tcp
488ed96a322f tobiasfenster/traefik-for-windows:v1.7.34 "/traefik --docker.e…" 21 hours ago Up 21 hours 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 0.0.0.0:8080->8080/tcp
8238d719a686 mcr.microsoft.com/businesscentral:10.0.17763.3650 "powershell -Command…" 4 days ago Up 22 hours (healthy) 80/tcp, 443/tcp, 1433/tcp, 7045-7049/tcp, 7083/tcp, 8080/tcp
8a57b92b029b mcr.microsoft.com/businesscentral:10.0.17763.3650 "powershell -Command…" 4 days ago Up 21 hours (healthy) 80/tcp, 443/tcp, 1433/tcp, 7045-7049/tcp, 7083/tcp, 8080/tcp
81b84a7ed5e3 mcr.microsoft.com/businesscentral:10.0.17763.3650 "powershell -Command…" 7 days ago Up 21 hours (healthy) 80/tcp, 443/tcp, 1433/tcp, 7045-7049/tcp, 7083/tcp, 8080/tcp
4375b693f606 mcr.microsoft.com/businesscentral:10.0.17763.3650 "powershell -Command…" 11 days ago Up 21 hours (healthy) 80/tcp, 443/tcp, 1433/tcp, 7045-7049/tcp, 7083/tcp, 8080/tcp
2415c1bafa62 mcr.microsoft.com/businesscentral:10.0.17763.3650 "powershell -Command…" 4 weeks ago Up 21 hours (healthy) 80/tcp, 443/tcp, 1433/tcp, 7045-7049/tcp, 7083/tcp, 8080/tcp
99ecd601ae19 mcr.microsoft.com/businesscentral:10.0.17763.3650 "powershell -Command…" 4 weeks ago Up 21 hours (healthy) 80/tcp, 443/tcp, 1433/tcp, 7045-7049/tcp, 7083/tcp, 8080/tcp
f43438446116 mcr.microsoft.com/businesscentral:10.0.17763.3650 "powershell -Command…" 5 weeks ago Up 21 hours (healthy) 80/tcp, 443/tcp, 1433/tcp, 7045-7049/tcp, 7083/tcp, 8080/tcp
830228db2991 mcr.microsoft.com/businesscentral:10.0.17763.3406 "powershell -Command…" 3 months ago Up 21 hours (healthy) 80/tcp, 443/tcp, 1433/tcp, 7045-7049/tcp, 7083/tcp, 8080/tcp
1009bef759f9 mcr.microsoft.com/businesscentral:10.0.17763.3287 "powershell -Command…" 4 months ago Up 21 hours (healthy) 80/tcp, 443/tcp, 1433/tcp, 7045-7049/tcp, 7083/tcp, 8080/tcp
9e2fc9fa5129 mcr.microsoft.com/businesscentral:10.0.17763.2928 "powershell -Command…" 6 months ago Up 21 hours (healthy) 80/tcp, 443/tcp, 1433/tcp, 7045-7049/tcp, 7083/tcp, 8080/tcp
cd0388a0843c mcr.microsoft.com/businesscentral:10.0.17763.2366 "powershell -Command…" 11 months ago Up 21 hours (healthy) 80/tcp, 443/tcp, 1433/tcp, 7045-7049/tcp, 7083/tcp, 8080/tcp
b3ec15f915c7 mcr.microsoft.com/businesscentral:10.0.17763.2366 "powershell -Command…" 12 months ago Up 21 hours (healthy) 80/tcp, 443/tcp, 1433/tcp, 7045-7049/tcp, 7083/tcp, 8080/tcp docker logs for the traefik container2023/01/08 23:34:17 Using high precision timer
2023/01/09 21:08:55 Using high precision timer
time="2023-01-09T21:08:57+01:00" level=error msg="Failed to retrieve information of the docker client and server host: error during connect: Get \"http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/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."
time="2023-01-09T21:08:57+01:00" level=error msg="Provider connection error error during connect: Get \"http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/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., retrying in 348.546422ms"
time="2023-01-09T21:08:57+01:00" level=error msg="Failed to retrieve information of the docker client and server host: error during connect: Get \"http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/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."
time="2023-01-09T21:08:57+01:00" level=error msg="Provider connection error error during connect: Get \"http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/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., retrying in 472.311552ms"
time="2023-01-09T21:08:58+01:00" level=error msg="Failed to retrieve information of the docker client and server host: error during connect: Get \"http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/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."
time="2023-01-09T21:08:58+01:00" level=error msg="Provider connection error error during connect: Get \"http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/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., retrying in 1.648796439s"
time="2023-01-09T21:08:59+01:00" level=error msg="Failed to retrieve information of the docker client and server host: error during connect: Get \"http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/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."
time="2023-01-09T21:08:59+01:00" level=error msg="Provider connection error error during connect: Get \"http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/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., retrying in 855.729185ms" We also recreate the traefik container each night. Since this image (1.7.34) is also 3 months old, I don't think it's the issue I downgraded to v 4.0.7 of BcContainerHelper (not sure whether the issue appeared with .8 or .9) and recreated the container which didn't help. Then I recreated the traefik container and then recreated the container again, now everything seems to be working again. In future to make it easier to find what got released in which version of bccontainerhelper it would be very helpful if you could add tags when you release a new version so it's easier to compare releases. |
Nothing has changed in this area for a very long time. |
Look what I just found: https://www.axians-infoma.de/techblog/allow-access-to-the-docker-engine-without-admin-rights-on-windows - @tfenster also mentioned the docker_engine_windows. Maybe you'd like to share some insights? |
@christianbraeunlich - that code is built into Check-BcContainerHelperPermissions and will add permissions to this. |
@freddydk Thanks for the quick reply. |
Do you run this with Docker Desktop? I think that is the only way how you can end up with a |
@itsme112358 - I have moved your issue to a new issue - I don't think that is related to Docker Desktop and the original problem |
You are correct, I didn't read the error message correctly, I just read that there was an issue with the named pipe, which it seemed to fit with my issue. Plus it fit the timing 🙈 Sorry about that! See you over there ;) |
@christianbraeunlich - is this still an issue? |
I've just checked in with the info on my working pc (win10) and the content of the deamon.json is also: {
"experimental": false,
"hosts": [
"npipe:////./pipe/docker_engine_windows"
]
} So as Tobias pointed out, it might be the fact that I run Docker Desktop. Don't really know.. I created a workaround for myself by using the Docker Image from Tobias and create all containers with additional parameters, providing the docker labels that Traefik makes use of. So for me the script in this module still does not work, but it might be an edge case. So if anyone else might come up with similar problems in the future we can reference to this issue. |
Ok, thanks |
Hello there,
I was trying to setup some containers using traefik after a long period of time. I think it used to work right of the bat for me, but now I catch some errors which I think is mostly related to docker itself. I like to share the information, get some guidance into the right direction - which is very much appreciated - and maybe contribute if neccessary. Thanks in advance!
FYI: I got it working after a few days: with the latest image of
tobiasfenster/traefik-for-windows:2.9.6
and manually creating the labels for the container. I've also had to migrate the scripts to Traefik 2 and replacepipe/docker_engine
withpipe/docker_engine_windows
(this is not only true to thetraefik.yml
but also when mounting the volume.Describe the issue
When executing the Setup-TraefikContainerForBcContainer.ps1 script it successfully creates the traefik container (tobiasfenster/traefik-for-windows:1.7.34).
Opening the terminal of this container shows that there was no connection established to the Docker Daemon:
Provider connection error error during connect: Get \"http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/version\": open //./pipe/docker_engine: message readmode pipes not supported In the default daemon configuration on Windows
.This blocks traefik from being able to discover the lables of other docker containers. If I would be able to select a docker daemon I could select npipe:////./pipe/docker_engine_windows and I expect it to work.
Maybe you have some insights for me as I also think my setup is a bit off due to the _windows suffix.
Thank you for your help!
Scripts used to create container and cause the issue
Setup-TraefikContainerForBcContainer.ps1
Full output of Setup-TraefikContainerForBcContainer.ps1 script
So far, so good. Now if we take a look into the terminal of the created container we will see lots of errors:
In the end, this is what blocks traefik from discovering other containers.
The content of the C:\ProgramData\Docker\config\daemon.json:
I barely see the named pipe with the suffix _windows in any documentation or forum. I also reinstalled the entire OS + Docker, but it stays the same.
I post my container creation script and output as well just for the record.
New-BcContainerUseTraefik.ps1
Full output of New-BcContainerUseTraefik.ps1.ps1 script
Systeminformation
Docker Desktop 4.15.0 (93002)
The text was updated successfully, but these errors were encountered: