Docker compose fail with npm error

Open

#191 opened on Jan 9, 2025 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 25/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Stale
Tech stack: docker, docker-compose, node.js
Domain: build-system, devops

Research direction

Start by reproducing docker compose up on macOS Sonoma and inspect the front-end build step that runs npm install. Compare the failure with the reported npm 10.8.2 environment and determine why the build cannot complete; done means the compose build and startup succeed without the npm error.

Written by the indexing model from the issue text.

Description

running
docker compose up
on MacOS Sonoma 14.7.1

=> ERROR [front-end 4/4] RUN npm install                                                                                                                           71.2s
------                                                                                                                                                                    
 > [front-end 4/4] RUN npm install:
71.17 npm error Exit handler never called!
71.17 npm error This is an error with npm itself. Please report this error at:
71.17 npm error   <https://github.com/npm/cli/issues>
71.17 npm error A complete log of this run can be found in: /root/.npm/_logs/2025-01-09T20_05_33_024Z-debug-0.log
------
WARN[0001] current commit information was not captured by the build  error="failed to read current commit information with git rev-parse --is-inside-work-tree"
failed to solve: process "/bin/sh -c npm install" did not complete successfully: exit code: 1

/root directory does not exist.
Searched globally for file 2025-01-09T20_05_33_024Z-debug-0.log and couldn't find it.

Local npm version: 10.8.2
I cleared the npm cache:
npm cache clean --force

Still getting the "npm error Exit handler never called!" error.

Dominant language: Python
Stars: 5.4k
Forks: 1.2k
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

slack-gif-creator: validate_gif() multiplies the last frame's duration by the frame count, so reported duration/fps are wrong (1.0s GIF reported as 1.8s) Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

anthropics/skills#1811 · 1 comment · Opened Sep 23, 2026
App fails to start with gradio 6 (allowed by `gradio>=5.49.1`) Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

speaches-ai/speaches#678 · Opened Sep 23, 2026
ModuleNotFoundError: No module named 'mcp.server.fastmcp'. Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

datalayer/mcp-compose#42 · Opened Sep 23, 2026
import spacy fails with ModuleNotFoundError: No module named 'click' Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

conda-forge/spacy-feedstock#177 · Opened Sep 23, 2026
humaneval: extract_function_body corrupts a fenced body-only reply, so the same correct code scores INCORRECT fenced and CORRECT unfenced Open

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

UKGovernmentBEIS/inspect_evals#2523 · Opened Sep 23, 2026

More Python issues