Continuous Integration Deployment - Jenkins is configured to use Docker on a remote server to execute build tasks

After using Jenkins for a period of time, you will find that after Jenkins builds images of N multiple projects, the current server or Jenkins container will occupy a large amount of memory. Over time, the Jenkins server hard disk will run out of space. Of course, if you don’t consider resource issues, you don’t have to worry about this issue.

I record here the Jenkins configuration to use the Docker of the remote server to perform the build task.

First, post the error message encountered:

Something went wrong, cannot connect to tcp://192.168.104.51:2375, cause: java.net