node:21-slim podman build issue

[saivamsilolla]

Environment

• Platform: linux - jenkins pipeline which is creating a docker image
• Docker Version: podman
• Node.js Version: 21-slim
• Image Tag:

Expected Behavior

Here is the definition of our dockerfile

FROM docker.****.com/docker-rmt/node:21-slim
ARG src="api-merged-oa3.yaml"
RUN npm i -g @stoplight/prism-cli@4.10.5

command used as part of our pipeline

podman build --storage-driver=overlay --isolation=chroot --ulimit=nofile=1048576:1048576 --cgroup-manager=systemd --events-backend=file

This command should properly build the docker image. with "19-slim" docker image there was no issue.

Current Behavior

the above build command fails with following error

Getting image source signatures

Copying blob sha256:aecd05d1cbe1c4670acb3bdc66a317a262fd1f3e77d2ff4e1d9d4156b401ac4e

Copying blob sha256:bc194d4002b7a538754445d95c1ab78a0cf9f6b0b58999a3b53d58d319f44a2d

Copying blob sha256:a378f10b321842c3042cdeff4f6997f34f4cb21f2eff27704b7f6193ab7b5fea

Copying blob sha256:2b6023d28a29f8617511a53ede6eeab191b807b2f452f67b7519d41169a7e8f8

Copying blob sha256:b149feab63ac3fc5a32f7e797043f852a6ae09e6216678b09a301ae44b53101f

Copying blob sha256:bc194d4002b7a538754445d95c1ab78a0cf9f6b0b58999a3b53d58d319f44a2d

Copying blob sha256:aecd05d1cbe1c4670acb3bdc66a317a262fd1f3e77d2ff4e1d9d4156b401ac4e

Copying blob sha256:2b6023d28a29f8617511a53ede6eeab191b807b2f452f67b7519d41169a7e8f8

Copying blob sha256:a378f10b321842c3042cdeff4f6997f34f4cb21f2eff27704b7f6193ab7b5fea

Copying blob sha256:b149feab63ac3fc5a32f7e797043f852a6ae09e6216678b09a301ae44b53101f

Copying config sha256:f25f2d758a02e6545fb1444c7dd3d4a2c4b93b3338e2b1cbbb87c087d14749e8

Writing manifest to image destination

Storing signatures

STEP 2/8: ARG src="api-merged-oa3.yaml"

--> d26dc54a16e

STEP 3/8: RUN npm i -g @stoplight/prism-cli@4.10.5

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

Additional Information

This was working earlier. I suspect this is something to do with node:21-slim

[shlok-kothari]

Seeing this issue with the node:20 image as well