Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node gallium images fail to invoke npm when using run scripts #364

Closed
iouym opened this issue Aug 10, 2022 · 2 comments
Closed

Node gallium images fail to invoke npm when using run scripts #364

iouym opened this issue Aug 10, 2022 · 2 comments

Comments

@iouym
Copy link

iouym commented Aug 10, 2022

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)

@timbru31
Copy link
Owner

Thanks for the update - was not aware of such an issue.

Perhaps a consideration is having support for version specific images (e.g. docker pull timbru31/node-chrome:16.15.0)

Yes, this might be a good addition, but requires manual work for each new Node.js release.

@timbru31
Copy link
Owner

timbru31 commented Aug 24, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants