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

[bastarte]

Hi, I have an issue, with basically the same effect as #347 but probably a different resolution

docker build from getting-started

I'm on the tutorial, same step as 347
I try to build the image via docker build -t getting-started .
And I end up with:

=> [3/4] COPY . .                                                                                                                                                           0.0s
 => ERROR [4/4] RUN yarn install --production                                                                                                                                0.8s
------                                                                                                                                                                            
 > [4/4] RUN yarn install --production:                                                                                                                                           
#0 0.570 yarn install v1.22.19                                                                                                                                                    
#0 0.599 info No lockfile found.
#0 0.612 [1/4] Resolving packages...
#0 0.714 error An unexpected error occurred: "https://registry.yarnpkg.com/ansi-regex: getaddrinfo EACCES registry.yarnpkg.com".
#0 0.714 info If you think this is a bug, please open a bug report with the information provided in "/app/yarn-error.log".
#0 0.714 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
------
Dockerfile:6
--------------------
   4 |     WORKDIR /app
   5 |     COPY . .
   6 | >>> RUN yarn install --production
   7 |     CMD ["node", "src/index.js"]
   8 |     EXPOSE 3000
--------------------
ERROR: failed to solve: process "/bin/sh -c yarn install --production" did not complete successfully: exit code: 1

docker compose up

Just to try a different build, If I run docker compose up from getting-started/ I get :

WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7ffa4ff71650>: Failed to establish a new connection: [Errno 13] Permission denied')': /simple/mkdocs/
#0 10.11 ERROR: Could not find a version that satisfies the requirement mkdocs==1.3.0 (from versions: none)
#0 10.11 ERROR: No matching distribution found for mkdocs==1.3.0
#0 10.12 WARNING: There was an error checking the latest version of pip.
------
failed to solve: process "/bin/sh -c pip install -r requirements.txt" did not complete successfully: exit code: 1

nslookup registry.yarnpkg.com

And finally if I test the connectivity

docker run busybox nslookup registry.yarnpkg.com
nslookup: socket: Permission denied

Clean try

I also tried to clone the repo again and start from scratch and it's the same. It's an issue from my system. I did reboot too.

I'm on Ubuntu 20.04
Would someone have something to recommend to solve this please ?

[letelumiere]

did you checked the version of metadata? now, I'm following docker tutorial, and have a same issues.

this is default example which i've problem.

FROM node:12-alpine
RUN apk add --no-cache python2 g++ make
WORKDIR /app
COPY . .
RUN yarn install --production
CMD ["node", "/app/src/index.js"]

but i checked the version of nodeJS and python, at the CMD.

FROM node:14-alpine
RUN apk add --no-cache python3 g++ make
WORKDIR /app
COPY . .
RUN yarn install --production
CMD ["node", "/app/src/index.js"]

i'm on ubuntu 11.1.0v but I reckon you can solve a problem.

[mmdmurphy]

I have basically same problem. I'm sorry, but docker came strongly recommended for something I'm trying to do. I can't make it past the tutorial. Frown.

[rashiddilkash]

Try
RUN yarn install --production --ignore-engines
in Docker file

[pframpto]

That worked for me but only after I took out --production
so on the Dockerfile my line read:
RUN yarn install --ignore-engines

thanks Rashiddilkash

[royzhao7]

FROM arm64v8/node
WORKDIR /app
COPY . .
RUN yarn install --ignore-engines
CMD ["node", "src/index.js"]
EXPOSE 3000

This my docker file. it worked for me

[yibajianghudao]

That worked for me.
Thanks Rashiddilkash.

[yibajianghudao]

when i first, my Dockerfile is:
RUN yarn install --product --ignore-engines
it's worked for me.
But second,
RUN yarn install --ignore-engines
it's worked for me.
thanks.

[dradice]

I had the same issue on Pop!_OS 22.04 (an Ubuntu 22.04 derivative) using Docker Desktop. The solution was to add

"dns": [
    "8.8.8.8"
  ],

To the Docker Engine config file (under Settings -> Docker Engine). Now my config file reads

{
  "builder": {
    "gc": {
      "defaultKeepStorage": "20GB",
      "enabled": true
    }
  },
  "dns": [
    "8.8.8.8"
  ],
  "experimental": false
}

[georgetalamantez]

pay 1 million ounces of laddie gold to Austin Greene and he will aprove this. He promises!

…

On 9/13/23, David Radice ***@***.***> wrote: I had the same issue on Pop!_OS 22.04 (an Ubuntu 22.04 derivative) using Docker Desktop. The solution was to add ``` "dns": [ "8.8.8.8" ], ``` To the Docker Engine config file (under Settings -> Docker Engine). Now my config file reads ``` { "builder": { "gc": { "defaultKeepStorage": "20GB", "enabled": true } }, "dns": [ "8.8.8.8" ], "experimental": false } ``` -- Reply to this email directly or view it on GitHub: #381 (comment) You are receiving this because you are subscribed to this thread. Message ID: ***@***.***>

[chy2948331536]

hello! I not search the error of failed to solve: process "/bin/sh -c yarn install --production" did not complete successfully: exit code:
I search the error /app/node_modules/sqlite3: Command failed.

Then I realized that there might be a missing package called npm(The World's Largest Software Registry (Library))
I run
sudo apt install npm
the docker build -t getting-started . go to the next step and complete

output:
(base) caodd@PowerEdge:~/program/getting-started-app$ docker build -t getting-started .
[+] Building 20.2s (11/11) FINISHED docker:default
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 180B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> resolve image config for docker.io/docker/dockerfile:1 1.7s
=> CACHED docker-image://docker.io/docker/dockerfile:1@sha256:ac85f380a63b13dfcefa89046420e1781752bab202122f8f50032edf31be0021 0.0s
=> [internal] load metadata for docker.io/library/node:18-alpine 1.1s
=> [1/4] FROM docker.io/library/node:18-alpine@sha256:3482a20c97e401b56ac50ba8920cc7b5b2022bfc6aa7d4e4c231755770cf892f 0.0s
=> [internal] load build context 0.0s
=> => transferring context: 11.14kB 0.0s
=> CACHED [2/4] WORKDIR /app 0.0s
=> CACHED [3/4] COPY . . 0.0s
=> [4/4] RUN yarn install --production 15.5s
=> exporting to image 1.6s
=> => exporting layers 1.6s
=> => writing image sha256:2748a5a2cb58bfe3ba9cc70b50721704e7582d1582457b07e1fdf258afe209d0 0.0s
=> => naming to docker.io/library/getting-started 0.0s

What's Next?

1. Sign in to your Docker account → docker login
2. View a summary of image vulnerabilities and recommendations → docker scout quickview
   (base) caodd@PowerEdge:~/program/getting-started-app$

[MislavJuric]

I am having the same issue. None of the suggestions above worked for me.

As suggested by #347, when I try to run:

docker run busybox nslookup registry.yarnpkg.com

I get the following output:

Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
3f4d90098f5b: Pull complete 
Digest: sha256:3fbc632167424a6d997e74f52b878d7cc478225cffac6bc977eedfe51c7f4e79
Status: Downloaded newer image for busybox:latest
;; connection timed out; no servers could be reached

[knowledegeupup]

I have the same question and None of the suggestions above worked for me.

[shirakuyanai]

I'm not sure why but leaving the --production flag doesn't work anymore since 1.0.4 Bun update.
Does it have any effect at all on performance or any difference from not having it?

[satishattada]

Please make sure, you have configured .env file in the project level