I want to remove all the unwanted docker images and containers from my system's C: drive. Currently system running out of memory. I had used the commands but it's showing the following error:
error during connect: Post https://192.168.99.100:2376/v1.40/containers/prune: dial tcp 192.168.99.100:2376: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
How do I resolve it?
image1
Running docker comments require the docker daemon (service) to be running.
Related
I am switching from docker to podman currently. Usually that works just fine. However on one of my many company laptops I ran into the following error:
PS C:\WINDOWS\system32> podman pull quay.io/podman/hello
Trying to pull quay.io/podman/hello:latest...
Error: initializing source docker://quay.io/podman/hello:latest: pinging container registry quay.io: Get "https://quay.io/v2/": dial tcp 54.163.152.191:443: i/o timeout
The above error I also get with other container registries. I tried:
Tried:
podman machine set --rootful
removing hyper-v and wsl
changing resolv.conf and adding nameserver
(tried also 8.8.8.8)
looked into symantec endpoint protection logs
(connection is not blocked)
switched between wsl 1 and 2
also tried some stuff from this thread (cf. No internet connection on WSL Ubuntu (Windows Subsystem for Linux))
I also do not get any internet inside e.g. an Ubuntu WSL VM. In Powershell running e.g. curl google.com works just fine
For completeness sake with the third option changes I get:
podman pull quay.io/podman/hello
Trying to pull quay.io/podman/hello:latest...
Error: initializing source docker://quay.io/podman/hello:latest: pinging container registry quay.io: Get "https://quay.io/v2/": dial tcp: lookup quay.io: Temporary failure in name resolution
Update:
I reinstalled Docker and get a similar issue
docker container run hello-world
Unable to find image 'hello-world:latest' locally
docker: initializing source docker://hello-world:latest: pinging container registry registry-1.docker.io: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: Temporary failure in name resolution.
See 'docker run --help'.
I'm running a minikube cluster on Hyper-V using windows 11 Pro.
I'm trying to create a deployment using a docker image (named k8s-web-hello), that is on Docker Hub using the following command :
kubectl create deployment k8s-web-hello --image=username/k8s-web-hello
but the I'm getting the following error :
error: failed to create deployment: Post "https://172.30.215.93:8443/apis/apps/v1/namespaces/default/deployments?fieldManager=kubectl-create&fieldValidation=Strict": dial tcp 172.30.215.93:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Operating System
Windows
Driver
Hyper-V
My docker container fails to communicate with the outside world no matter ports are open and network is properly set. I get ping, container is started without issues, but does not communicate over tcp. I get the error
systemd-udevd[11922]: veth09e2558: Failed to get link config: No such device
Any idea how to solve this?
when i try to install a sandbox-hdp version 2.6.5 by hortonworks on docker in my system by running docker-deploy-hdp256.sh script with sh command i recived the error at the end of all the pulling and some verification checksums are done.
error:
docker: Error response from daemon: Ports are not available: listen tcp 0.0.0.0:50075: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
but i could see the container with name sandbox-hdp. so i opened it and try to run hive. but it is giving some error related to connectivity.
i need to work on hive and for that i need to get this fixed.
In this case, sometimes is hard to turn off or close a port running because some of them is used by our computer or even a range of ports is reserved randomly. So in this opportunity try to delete this port in your sandbox-proxy script because you don't need to expose all ports. Ambari-hortonworks expose a lot of ports with docker and securely you won't use all of them.
ErrorDisplayedHere
I tried many ways like reinstalling Docker, changing DNS server,restarting windows, but nothing worked out.
Unable to find image 'hello-world:latest' locally docker: Error
response from daemon: Get https://registry-1.docker.io/v2/: dial tcp
100.24.246.89:443: connectex: No connection could be made because the target machine actively refused it.
Open Docker Settings and select "Expose daemon on tcp://localhost:2375 without TLS" (on the General tab), then apply & restart Docker. Do note the warning about the vulnerability that this option exposes.