trouble building with docker for Dockerfile.arm64v8
See original GitHub issue- Version (
cloudcmd -v
): checkout from github 2020-06-06 (4076ded) - Node Version
node -v
: v10.19.0 - OS (
uname -a
on Linux): Linux rivendale.selab.ca 5.4.0-1011-raspi #11-Ubuntu SMP Fri May 8 07:43:33 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux - Browser name/version: n/a
- Used Command Line Parameters: n/a
- Changed Config: when I first tried with arm64v8/node:slim the npm install --production core dumped and exited 134 I am building a computer lab appliance and want the student containers to have Ubuntu so I tried again with Ubuntu:
< FROM arm64v8/node:slim
---
> FROM arm64v8/ubuntu
10c10
< RUN apt-get update && apt-get -y install python3 make g++
---
> RUN apt-get update && DEBIAN_FRONTEND=noninteractive apt-get -y install nodejs npm python3 make g++
14,17c14
This is the error that I get:
Traceback (most recent call last):
File "/usr/share/nodejs/node-gyp/gyp/gyp_main.py", line 6, in <module>
from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/usr/share/nodejs/node-gyp/lib/configure.js:355:16)
gyp ERR! stack at ChildProcess.emit (events.js:198:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Linux 5.4.0-1011-raspi
gyp ERR! command "/usr/bin/node" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /usr/src/app/node_modules/node-pty
gyp ERR! node -v v10.19.0
gyp ERR! node-gyp -v v6.1.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-pty@0.9.0 install: `node scripts/install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-pty@0.9.0 install script.
I also changed the docker-compose.yml to build the Dockerfile
web:
+ build: .
ports:
- 8000:8000
I am really eager for this to work on PI. I have 2 virtual classes scheduled for the fall term in python and Jekyl. It looks like I maybe should change the version of node-pty. I will keep digging in to this myself but I was hoping that you might have some insight.
Thanks
Rich
Issue Analytics
- State:
- Created 3 years ago
- Comments:16 (15 by maintainers)
Top Results From Across the Web
Building Multi-Arch Images for Arm and x86 with Docker Desktop
Let's create a simple example Dockerfile, build a couple of image variants, and push them to Hub. ~ ❯❯❯ mkdir test && cd...
Read more >Multi-arch build and images, the simple way | Docker
To fix this problem, Docker introduced the principle of multi-arch builds and we'll see how to use this and put it into production....
Read more >arm64v8/docker - Docker Image
Although running Docker inside Docker is generally not recommended, there are some legitimate use cases, such as development of Docker itself. Docker is...
Read more >Multi-platform images | Docker Documentation
You can build multi-platform images using three different strategies that are supported by Buildx and Dockerfiles: Using the QEMU emulation support in the ......
Read more >arm64v8/r-base - Docker Image
Supported tags and respective Dockerfile links. 4.2.2 , latest · arm64v8/r-base build status badge. Quick reference (cont.).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Landed in v15.3.4 🎉 , @timoknapp thanks a lot 😃 @rhildred, is it works for you?
Hi @rhildred
I guess this bug will be resolved whenever the new version of
cloudcmd
is released by @coderaiser .Just as hint the following types of
docker
images are then available:Regards Timo