-
Notifications
You must be signed in to change notification settings - Fork 419
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
ghcr.io/devcontainers/features/node doesn't work on macos #1240
Comments
Thanks for opening. @Kaniska244 if you get a moment, could you please take a closer look? |
Hi @yu2003w , This "ghcr.io/devcontainers/features/node:1" isn’t a regular image. Its a feature added on top of other devcontainer images. You could check https://github.com/devcontainers/images/blob/main/src/javascript-node/README.md#using-this-image , which contain reference of full fledged, regular devcontainer images for node from MCR repo for different linux flavors such as the followings. mcr.microsoft.com/devcontainers/javascript-node (latest) Kindly let me know in case of any further concern on this. With Regards, |
Hi @Kaniska244,
6.559 NVM_VERSION=0.40.1
|
Hi @yu2003w , This is indeed failing while installing the node feature which is configured in the devcontainer.json in https://github.com/langflow-ai/langflow repo. The problem looks like that in MacBook you must be having default prompt as zsh & I can see as per the error stack trace, its being executed in zsh. Please let me know in case of any further concern on this. With Regards, |
Hi @Kaniska244 ,
I still got the error as below,
Possibly I misunderstood something. |
Hi, it seems that features/node doesn't work on mac os.
Is there any plan to support this?
`bash-3.2$ docker pull ghcr.io/devcontainers/features/node:1
1: Pulling from devcontainers/features/node
unsupported media type application/vnd.devcontainers
bash-3.2$ uname -a
Darwin macbook.local 24.2.0 Darwin Kernel Version 24.2.0: Fri Dec 6 19:00:33 PST 2024; root:xnu11215.61.5~2/RELEASE_ARM64_T8122 arm64`
The text was updated successfully, but these errors were encountered: