You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I ran docker build -t welcome-to-docker . I received the following error message "npm error Exit handler never called!
npm error This is an error with npm itself. Please report this error at:
npm error https://github.com/npm/cli/issues
npm error A complete log of this run can be found in: /root/.npm/_logs/2024-12-18T17_11_12_349Z-debug-0.log
npm error code UNABLE_TO_GET_ISSUER_CERT_LOCALLY
npm error errno UNABLE_TO_GET_ISSUER_CERT_LOCALLY
npm error request to https://registry.npmjs.org/serve failed, reason: unable to get local issuer certificate
npm error A complete log of this run can be found in: /root/.npm/_logs/2024-12-18T17_11_12_349Z-debug-0.log"
I made sure node.js and npm were up to date and installed and reran the same command however got the same result.
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
When I ran docker build -t welcome-to-docker . I received the following error message "npm error Exit handler never called!
npm error This is an error with npm itself. Please report this error at:
npm error https://github.com/npm/cli/issues
npm error A complete log of this run can be found in: /root/.npm/_logs/2024-12-18T17_11_12_349Z-debug-0.log
npm error code UNABLE_TO_GET_ISSUER_CERT_LOCALLY
npm error errno UNABLE_TO_GET_ISSUER_CERT_LOCALLY
npm error request to https://registry.npmjs.org/serve failed, reason: unable to get local issuer certificate
npm error A complete log of this run can be found in: /root/.npm/_logs/2024-12-18T17_11_12_349Z-debug-0.log"
I made sure node.js and npm were up to date and installed and reran the same command however got the same result.
Expected Behavior
was supposed to create a image file.
Steps To Reproduce
Environment
; copy and paste output from `npm config ls` here
The text was updated successfully, but these errors were encountered: