docker 无法构建

└─# docker build . -t cloudsploit:0.0.1 1 ⨯
Sending build context to Docker daemon 202.7MB
Step 1/7 : FROM node:lts-alpine3.12
---> 7ae9aa692723
Step 2/7 : ARG PACKAGENAME=cloudsploit
---> Using cache
---> 40ecb3439945
Step 3/7 : COPY . /var/scan/cloudsploit/
---> Using cache
---> ed501423d1f1
Step 4/7 : RUN cd /var/scan && npm init --yes && npm install ${PACKAGENAME}
---> Running in 367f2805bb07
Wrote to /var/scan/package.json:

{
"name": "scan",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"keywords": [],
"author": "",
"license": "ISC"
}

npm ERR! code EAI_AGAIN
npm ERR! syscall getaddrinfo
npm ERR! errno EAI_AGAIN
npm ERR! request to https://registry.npmjs.org/cloudsploit failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2023-02-09T00_08_01_106Z-debug.log
The command '/bin/sh -c cd /var/scan && npm init --yes && npm install ${PACKAGENAME}' returned a non-zero code: 1

Start with the Docker build output and inspect the build definition around the npm install step shown in Step 4/7. Check whether the container can resolve and reach registry.npmjs.org, then rerun the build; done means the image builds successfully without the EAI_AGAIN error.

Written by the indexing model from the issue text.