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
It looks like the docker images that use node:gallium (node:16) fail to execute run scripts (e.g. npm run test) which seems to be related to issue nodejs/docker-node#1734
Not too sure what the best path forward is, it looks like this was introduced as of node image v16.15.1. The immediate workaround is to use the node:16.15.0 image, figured I'd flag it here as an FYI 🙂
Perhaps a consideration is having support for version specific images (e.g. docker pull timbru31/node-chrome:16.15.0)
The text was updated successfully, but these errors were encountered:
I've ran the example in the linked issue with both:
# Node.js is at 16.17.0
docker run --rm -v $PWD:/app --workdir /app --entrypoint npm timbru31/node-chrome:16-alpine run ver
docker run --rm -v $PWD:/app --workdir /app --entrypoint npm timbru31/node-chrome:16 run ver
Both work fine for me. Closing. Let me know if any new issues arise.
It looks like the docker images that use
node:gallium
(node:16
) fail to execute run scripts (e.g.npm run test
) which seems to be related to issue nodejs/docker-node#1734Not too sure what the best path forward is, it looks like this was introduced as of node image v16.15.1. The immediate workaround is to use the node:16.15.0 image, figured I'd flag it here as an FYI 🙂
Perhaps a consideration is having support for version specific images (e.g.
docker pull timbru31/node-chrome:16.15.0
)The text was updated successfully, but these errors were encountered: