In this article, we will see some of the solutions to the error “socket hang up” in Docker. At Bobcares, with our Docker Hosting Support Services, we can handle your Docker Hang-up issues.

Error “Socket Hang Up” In Docker

Docker avoids repetitive, tedious config processes and is used across the development lifecycle for quick, simple, and portable app development – desktop and cloud. Its full end-to-end platform comprises UIs, CLIs, APIs, and security that are designed to operate together throughout the whole app delivery lifecycle.

It uses OS-level virtualization to deliver software in packages called containers. It is a small, stand-alone software package that contains everything needed to run an app: code, runtime, system tools, system libraries, and settings.

Here, when the user successfully built and started the Docker container, it is up and running. However, when tried to use it after removing the containers and images and rebuilding it, the following error appears:

Other User Details

Docker File

Container Creation:

# Create Virtual Network
$ sudo docker network create network1 
# Using custom network as there are multiple containers 
# which communicate with each other

# Create Containers
$ sudo docker build -t form_ocr:latest .
$ sudo docker run -d -p 6001:5000 --net network1 --name form_ocr form_ocr

The output of netstat command:

$ netstat -nltp 
...
tcp6 0 0 :::6001 :::* LISTEN -

The output of the Docker container inspect:

$ sudo docker container inspect <container-id>

Output (docker ps output):

$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
835e8cb11eee form_ocr "python3 app.py" 16 hours ago Up 40 seconds 0.0.0.0:6001->5000/tcp form_ocr

Multiple Solutions For The Error “Socket Hang Up” In Docker

Solution 1: Simply include the following code in main.ts, where we listen to the port.

await app.listen(6001, '0.0.0.0', ()  => console.log(`Listening on port:  6000`));

Also include the ‘0.0.0.0’, it should work.

Solution 2: Check that the app is listening on 0.0.0.0 inside the container.

Solution 3: Instead of an internet address, try localhost:6001. We can also try any of the system’s local IP addresses, which we can find by typing ifconfig or ipconfig in Linux or Windows, respectively.

[Looking for a solution to another query? We are just a click away.]

Conclusion

The article provides three solutions from our Tech team to fix the error, “socket hang up” in Docker.