Why does npm install fail with Assertion failed: (fd > STDERR_FILENO) using buildah?

iaquobe

7/3/24, 1:29 PM

Hey I have a Dockerfile for a project that I want to build inside of a Gitlab ci/cd pipeline running on Kubernetes. The Image is built inside a buildah container from quay.io, but while the project compiles locally, it does not for the pipeline:

STEP 4/7: RUN npm install yarn
node: ../deps/uv/src/unix/core.c:633: uv__close: Assertion `fd > STDERR_FILENO' failed.
Aborted (core dumped)
subprocess exited with status 134
subprocess exited with status 134
error building at STEP "RUN npm install yarn": exit status 134

In fact even npm --version fails with the same error.

I tried to reproduce the environment locally with podman run --privileged -v $(pwd):/image quay.io/containers/buildah buildah build image which worked. But locally I am running with runc, while the pipeline is running with crio. I could not figure out how to run a container with crio.

What could be the cause of this? Could this be a crio configuration thing? I'd appreciate any help in figuring out, where to even start searching.

Thanks :)

0 + 0

kubernetes

gitlab-auto-devops

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Why does npm install fail with Assertion failed: (fd > STDERR_FILENO) using buildah?

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.