Hello laptop experts, I’ve got an issue with docker Desktop.
To run a “node” concerning the Pi Network, I needed to install Docker Desktop.
I’ve got 1 error code in the Pi Node : “PortsChecker container: unknown”
I’ve got 1 error code in Docker : “Pi-Port-Checker AMD64” ----> when I try to start this container by clicking on the button, I get the following error : " HTTP code 500) server error - driver failed programming external connectivity on endpoint pi-port-checker : Bind for 0.0.0.0:31401 failed: port is already allocated "
I believe these things are related but I can’t find a solution ( not on the internet, not in forums regarding the Pi Network, chats of Pi Network, … ).
I think it means that a Port is already in use?
Does anyone know a solution? My knowledge of computer is very very very basic, my english as well.
Unfortunately, I didn’t work.
In your suggestion is marked “to kill the process running the port”. When I do this, Docker ( the program ) shuts down completely : it is Docker itself that uses that container. When I restart, the container “runs” for a couple of seconds. After this the same error occurs…
If you think of other suggestions, you can always reply to this mail.
Don’t appreciate so much as you replied to a spammer. When someone quotes your entire post, it is probably a spambot which adds a spam link to the quored part then or later. And it did… So I deleted the post. Don’t pay attention to these kind of posts.
This is not that kind of forum. It is a Docker community forum where you can have Docker-related questions which you had.
The key part is
Yes.
Find out what is using that port or change the port mapping for the Docker container.
That is going to be a problem. Docker is not for users who “very very very basic” knowledge about computers.You need to know about the operating system, network and containers. You don’t have to be professional, but “very very very basic” is definitely not enough.
As said, the port is occupied by Docker itself.
If I “kill” the port / container, Docker shuts completely down. When opening docker again, the port is still used by Docker.
You wrote that when you kill a process, Docker (Docker Desktop) shuts down, but I haven’t read the spam post after the spam link (no time for reading spam ), so I didn’t know what you wrote that to. Now I checked, but please, share the process you see in the process list and also how you create the container. Don’t forget to format your post using code blocks as described here: How to format your forum posts
Docker Desktop doesn’t use that port and even if an extension uses it, I don’t think the whole Docker Desktop would stop. I can’t say more until I see what you killed actually.
), so I didn’t know what you wrote that to. Now I checked, but please, share the process you see in the process list and also how you create the container. Don’t forget to format your post using code blocks as described here: