I am using Docker for Desktop with version 20.10.17. Whenever I try to enable Kubernetes v1.24.2 from Docker Desktop and then click on apply and restart, it shows "Kubernetes failed to start". Moreover, when I type kubectl version in cmd, the version for client is shown but for server it displays "Unable to connect to server: EOF". I have tried a number of solutions including purging and resetting from troubleshooting option of docker desktop. I have disabled VPN, firewall but nothing is helping me. Can anyone help me overcome this problem?
I creates multiple containers remotely in the VM, but sometimes after rebooting the VM it gets this error and only restarting the VM helps. Do you know what this error means and how to solve it?
Docker API responded with status code=InternalServerError,
response={"message":"hcsshim::CreateComputeSystem
21b0a2583de03c0bb0871be6fc19580b74382c2afe697370b13edac0f31379ab: The
requested resource is in use.\n(extra info:
{"SystemType":"Container","Name":"21b0a2583de03c0bb0871be6fc19580b74382c2afe697370b13edac0f31379ab","Owner":"docker","IgnoreFlushesDuringBoot":true,"LayerFolderPath":"C:\\ProgramData\\Docker\\windowsfilter\\21b0a2583de03c0bb0871be6fc19580b74382c2afe697370b13edac0f31379ab","Layers":[{"ID":"6e512ed6-358b-5ade-be48-2ffe0aca7198","Path":"C:\\ProgramData\\Docker\\windowsfilter\\99f07daca1c1f27cebf6734e629331f2591365fb10f01087af5006daaf08dcfe"},{"ID":"89732e48-50f0-58fc-924e-116de51e7fa8","Path":"C:\\ProgramData\\Docker\\windowsfilter\\ffeb491d61491478f7db8de90727ec187246889b07289fcf0167cd81f81bc578"},{"ID":"4d107d52-32b1-58ef-8300-0a6e663ffc96","Path":"C:\\ProgramData\\Docker\\windowsfilter\\1d3356c9b099fb80301e6e2f4f3a47bbc422e7ddb9c496827d45d9c6e04f5fc2"},{"ID":"0b71aac6-7318-5347-a670-992c14d06613","Path":"C:\\ProgramData\\Docker\\windowsfilter\\def8b69f42a59ecf75bc8f74ab8a89a08378ce9a8c08b23a266e5b3c6a698e5f"},{"ID":"713ec9da-4c17-5a81-b458-3bd4a5f6ed27","Path":"C:\\ProgramData\\Docker\\windowsfilter\\abe1c469fd4c7650f55042c06cbe401b02c8bd5aedcb7fabd8c8d7e4a42f827f"},{"ID":"099b6b2c-1067-50b3-99bc-ec9d34027c52","Path":"C:\\ProgramData\\Docker\\windowsfilter\\3f6a34abe173f55b59669c859cc160436dc0d1222d9771bd907098e65efd2d60"},{"ID":"98b515ee-aa27-5fd2-bc30-ef80416b0f6f","Path":"C:\\ProgramData\\Docker\\windowsfilter\\6968b8cb1c76650fd4cb00f6daa20196c48ed3ea859da838b1e983900ceed1cd"},{"ID":"47ef818f-b569-530b-b886-3b94002eb19e","Path":"C:\\ProgramData\\Docker\\windowsfilter\\75114c4fe304656f0ad6be10eebc8e4a44ea193058bf444b536e2ecd8aa1671b"},{"ID":"0e70a491-247c-5574-b86a-24f209823e52","Path":"C:\\ProgramData\\Docker\\windowsfilter\\0193da6cbfd630787e298c7aa77274cd40ac3b444edbcaacfb725f9365210c36"},{"ID":"c3c2426f-1d1e-59eb-bd25-9fdb6bc2677e","Path":"C:\\ProgramData\\Docker\\windowsfilter\\06552a9e13e92f67a507de20d1e3a68e94a3510e716b7591d731d4637b3b6441"},{"ID":"ff3c665d-3a3b-563e-9c80-1f86fa8e7735","Path":"C:\\ProgramData\\Docker\\windowsfilter\\3d5e3b9c49041934ffa8917fb26401e6844a65ae0609705cecf57c958f0821c6"}],"ProcessorCount":5,"MemoryMaximumInMB":6675,"HostName":"21b0a2583de0","HvPartition":true,"EndpointList":["b1c4f68a-6037-4335-ad37-64cd6330159d"],"HvRuntime":{"ImagePath":"C:\\ProgramData\\Docker\\windowsfilter\\06552a9e13e92f67a507de20d1e3a68e94a3510e716b7591d731d4637b3b6441\\UtilityVM"},"AllowUnqualifiedDNSQuery":true})"}
stupid message but the problem with parameter -memory https://forums.docker.com/t/error-the-requested-resource-is-in-use-only-when-using-memory/95851 I will spawn docker in windows server and I will be able to use parameter isolation which resolves docker bug
The problem I face is that the first time the Docker service on my Windows 10 pro computer is started at boot time, then I get all kinds of errors. Restarting the Docker service solves always the problem.
On my Windows 10 pro computer the Docker Service is started automatically. The problem is that the service starts a bit too early. I know about the Windows Fastboot but changing that I find to heavy to configure that to solve this problem.
Is there a way to configure the Docker service to start later in the Windows 10 boot sequence?
You think - make it a program that is started automatically. When I configure Docker NOT as a service, then I get all kinds of problems. The Docker system tray icon sometimes even gets the red color ...
The error messages are:
ERROR: for docker-compose_geosolschmea_1 Cannot start service
geosolschmea: driver failed programming external connectivity on
endpoint docker-compose_geosolschmea_1
(3c0302743b124c050334b9ca3fcd3c9b01a0bcfaa1d629d74f7311cb09a58833):
Error starting userland proxy: mkdir
/port/tcp:0.0.0.0:3306:tcp:172.18.0.2:3306: inpuStarting
docker-compose_jenkins_1 ... error
ERROR: for docker-compose_jenkins_1 Cannot start service jenkins:
driver failed programming external connectivity on endpoint
docker-compose_jenkins_1
(fa039afd6930afba9843b89295e1bbeab32102679964780f867df1cd13282fe0):
Error starting userland proxy: mkdir
/port/tcp:0.0.0.0:8888:tcp:172.18.0.3:8080: input/output error
When I run wolkenkit start on a Windows machine, the command fails and I get the following output:
Starting the application...
Validating the application code...
Verifying health on environment default...
Verifying application status...
Verifying that ports are available...
Setting up network...
Building Docker images...
Starting Docker containers...
✗ Failed to start the application.
docker: Error response from daemon: driver failed programming external connectivity on endpoint boards-postgres (7cf3e33d876e8d22fced3926fdc9ddf2372b499803dc92a4b7bb403fd2552064): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:3030:tcp:172.21.0.4:5432: input/output error.
ExecutableFailed: docker: Error response from daemon: driver failed programming external connectivity on endpoint boards-postgres (7cf3e33d876e8d22fced3926fdc9ddf2372b499803dc92a4b7bb403fd2552064): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:3030:tcp:172.21.0.4:5432: input/output error.
at childProcess.exec (C:\Users\wagle\Dev\tnw\wolkenkit\src\shell\exec.js:21:20)
at ChildProcess.exithandler (child_process.js:301:5)
at ChildProcess.emit (events.js:189:13)
at maybeClose (internal/child_process.js:970:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
I'm running on Windows 10 using Docker Desktop for Windows 2.0.0.3. Any ideas where this problem might originate from?
Actually, we (at the native web, the company behind wolkenkit), ran into this problem as well.
It's actually a problem caused by one of the latest updates for Windows 10. This updated introduced a new feature called "Fast startup" which causes problems for Docker.
See this issue for more details: https://github.com/docker/compose/issues/3277
As a quick fix, you can restart Docker. As a more long term solution, you can disable the "Fast Startup" feature, see https://github.com/docker/for-win/issues/953#issuecomment-342498223
Hope this helps 😊
PS: Please note that I am one of the core developers of wolkenkit.
I am creating a sample Blockchain network using tutorial https://hyperledger-fabric.readthedocs.io/en/release-1.2/build_network.html. I am facing an error while connecting the peers :
Error: failed to create deliver client: orderer client failed to connect to orderer.example.com:7050: failed to create new connection: context deadline exceeded.
I found a probable solution here which I would like to test but I need help for below :
How to update default network of the containers
How to add property for each container.
While accessing my etc/docker directory I am getting error 'Server returned empty listing for directory '/etc/docker' and also it says permission denied when I try to access it from terminal. Any help will be appreciated.
There is no need for making any changes in Docker containers. I faced similar issue, you can clean up the system space or if you are using a VM you install a fresh network in a new VM(assuming you already have all configuration files copied).