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

error in step 5/5 with RUN npm install #10

Open
gpapat26 opened this issue Feb 14, 2024 · 1 comment
Open

error in step 5/5 with RUN npm install #10

gpapat26 opened this issue Feb 14, 2024 · 1 comment

Comments

@gpapat26
Copy link

gpapat26 commented Feb 14, 2024

Hello,
I m running the example and trying locally to build an image :

docker build -t gpapathe/qsk-book:1.0 .

but I get an error . I have bought the book and trying to follow step by step.
I m dont have a docker account in some registry or have created some account in some cloud cluster provider yet.
I m trying to do stuff locally which I assume it
I have tried behind company proxy , removing the proxy. Connecting via my mobile hotspot. In either scenario the npm install command from within the docker image does not seem to work. It seems that this is a timeout thing as it runs for many seconds.. and then boom error :

`papathe@l9kg3hw3-ath:/space/kubernetes/nigel_quick_start_examples/qsk-book/Appv1.1$ docker build -t gpapathe/qsk-book:1.0 .
[+] Building 519.1s (9/9) FINISHED docker:default
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 682B 0.0s
=> [internal] load .dockerignore 0.1s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for docker.io/library/node:current-alpine 1.6s
=> [1/5] FROM docker.io/library/node:current-alpine@sha256:4cc2d9f365691fc6f8fe227321d32d9a2691216a71f51c21c7f02224515dea48 4.4s
=> => resolve docker.io/library/node:current-alpine@sha256:4cc2d9f365691fc6f8fe227321d32d9a2691216a71f51c21c7f02224515dea48 0.0s
=> => sha256:f16884bf7ba38fab89edcd0cb8ba1f5d481495ca482476e73f5297cdd299dc2d 43.52MB / 43.52MB 2.8s
=> => sha256:12fe8815c466514f8488b5ca8bda5e7aadec8e77e9fe1b494040cac76af4da82 2.37MB / 2.37MB 1.2s
=> => sha256:4cc2d9f365691fc6f8fe227321d32d9a2691216a71f51c21c7f02224515dea48 1.43kB / 1.43kB 0.0s
=> => sha256:a4846d0aac29ceb77a633edcbc56260231fe6f0ba3aeca1ed8f3085a26c54f8e 1.16kB / 1.16kB 0.0s
=> => sha256:a4953861f11d2c59d7d524dbcc90827fc27bde5ed4ffee7df711319523c8b35d 7.13kB / 7.13kB 0.0s
=> => sha256:4abcf20661432fb2d719aaf90656f55c287f8ca915dc1c92ec14ff61e67fbaf8 3.41MB / 3.41MB 0.7s
=> => extracting sha256:4abcf20661432fb2d719aaf90656f55c287f8ca915dc1c92ec14ff61e67fbaf8 0.1s
=> => sha256:9b5c6033110b9fc74a8d438ab7fe7a1042a36dd5d402cc0975ded8f53e2a2f16 449B / 449B 1.0s
=> => extracting sha256:f16884bf7ba38fab89edcd0cb8ba1f5d481495ca482476e73f5297cdd299dc2d 1.2s
=> => extracting sha256:12fe8815c466514f8488b5ca8bda5e7aadec8e77e9fe1b494040cac76af4da82 0.1s
=> => extracting sha256:9b5c6033110b9fc74a8d438ab7fe7a1042a36dd5d402cc0975ded8f53e2a2f16 0.0s
=> [internal] load build context 0.0s
=> => transferring context: 52.35kB 0.0s
=> [2/5] RUN mkdir -p /usr/src/app 0.6s
=> [3/5] COPY . /usr/src/app 0.1s
=> [4/5] WORKDIR /usr/src/app 0.1s
=> ERROR [5/5] RUN npm install 512.2s

[5/5] RUN npm install:
512.2 npm ERR! code EAI_AGAIN
512.2 npm ERR! syscall getaddrinfo
512.2 npm ERR! errno EAI_AGAIN
512.2 npm ERR! request to https://registry.npmjs.org/bytes failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org
512.2
512.2 npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-02-14T10_42_14_959Z-debug-0.log


Dockerfile:18

16 |
17 | # Install dependencies from packages.json
18 | >>> RUN npm install
19 |
20 | # Command for container to execute

ERROR: failed to solve: process "/bin/sh -c npm install" did not complete successfully: exit code: 1`

@gpapat26
Copy link
Author

For Ubundu I had the following docker options :

OPTIONS="--data-root /space/docker -H unix:///var/run/docker.sock --ip-forward=true --iptables=true --ip-masq=true --bridge docker0 -G docker --dns 172.17.0.1 --dns-search my_company"

I updated to : -dns 10.85.167.11 --dns 8.8.8.8

OPTIONS="--data-root /space/docker -H unix:///var/run/docker.sock --ip-forward=true --iptables=true --ip-masq=true --bridge docker0 -G docker --dns 10.85.167.11 --dns 8.8.8.8 --dns 172.17.0.1 --dns-search my_company"

The topic is analysed in :

https://robinwinslow.uk/fix-docker-networking-dns
https://serverfault.com/questions/612075/how-to-configure-custom-dns-server-with-docker

Us poor ubundu users seem to get into network trouble and blame books for this when the issue is elsewhere.

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

1 participant