[Bug]: `npm create storybook@latest` fails in Alpine containers

[beporter]

Describe the bug

The issue is that busybox's ps binary doesn't know about the -p switch, so running npm create storybook@latest fails in a stock node:lts-alpine docker container.

ps: unrecognized option: p
BusyBox v1.37.0 (2025-12-16 14:19:28 UTC) multi-call binary.

Usage: ps [-o COL1,COL2=HEADER] [-T]

Show list of processes

	-o COL1,COL2=HEADER	Select columns for display
	-T			Show threads

Reproduction link

https://gist.github.com/beporter/a45cbf03afa37b474f1127fe89144a90

Reproduction steps

Since this error occurs during project setup, it can not be represented in a static git repository. The link above is a transcript of the commands necessary to trigger the error. Those commands (without their output) can be summarized as:

% docker run -it --rm node:lts-alpine sh

% npm create vue@latest

% cd vue-project/

% npm install

% npm create storybook@latest

System

# cat /etc/os-release
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.23.3
PRETTY_NAME="Alpine Linux v3.23"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://gitlab.alpinelinux.org/alpine/aports/-/issues"

Additional context

No response

[beporter]

This is surely an upstream bug, but I couldn't spot it in vite-plugin-inspect so it's possibly further upstream? I'm not up to speed on the ecosystem though.

[dosubot]

Hi @beporter! I'm Dosu and I’m helping the storybook team.

Good instinct — it's likely not vite-plugin-inspect itself. Based on the codebase, the ps -p usage is most likely coming from the detect-port package, which Storybook uses during server initialization to find available ports.

So the upstream bug would be in detect-port rather than any Vite plugin.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[darshjme-codes]

Triage note:

Bug: npm create storybook@latest fails in Alpine container.

Labels applied: bug, needs triage ✓

Suggested additional labels:

• cli
• docker

Common Alpine issues:

• Missing native dependencies (glibc, build tools)
• Node binary compatibility (musl vs glibc)
• npm/node version mismatch

Workaround: Use Debian-based images or install Alpine build dependencies

Error message needed: Specific failure output