-
Notifications
You must be signed in to change notification settings - Fork 243
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
bootstrap-image fails on node-pty when running on Cortex-A53 #400
Comments
To dig into this more, I manually booted up a container on the board using the "node:16.16.0" image and installed node-pty works fine!
Manually running the Dockerfile provided bootstrap-image does fail. So theres some critical difference between devcontainer apline image and node's image to not let node-pty install properly.
|
I commended out the /root/.npm/_logs/2023-02-04T02_36_56_294Z-debug-0.log
|
Hi @jrj2211 👋 Do you mind pasting the contents of your |
Thanks for the quick response. I found an issue over on Docker's repo about alpine v3.14 having this issue with Docker versions older than 20.10. The version of Linux these boards ship with only has Docker 18.09.1 which is EOL. The solution seems to be update to a current version of Docker (hopefully). I will report back shortly, hopefully closing this issue with it just being a Docker version mismatch. |
Yup! It was just an out of date Docker that was causing the permission error. |
I hope this is the correct repo for this. I have a devcontainer that works when cloning in Windows. I need to also be able to run it on our actual hardware, which we use a Tordex Verdin ARMv8-A SOM.
In Vscode, I'm first connecting to my board via remote-ssh. I'm then using the "Dev Containers: Clone repository in container volume" command. Using my projects repo or any of Microsofts "remote-try-xxx" projects, the same error occurs which appears to be when building the "bootstrap-image" container:
These Toradex boards use a very stripped down version of linux to speed up boot time so I'm guessing I'm probably missing some needed dependency but the provided error doesn't lend itself to figure out what could be missing. Any help would be appreciated. Looking through the old devcontainers repository, there was an issue for supporting arm64 which seems like it was completed. Maybe I'm wrong on that assumption.
Full stack trace
The text was updated successfully, but these errors were encountered: