ERROR: failed to solve: process "/bin/sh -c yarn install --production" did not complete successfully: exit code: 1
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Tranquilo
- Stack tecnológico
- docker, javascript, python, ubuntu
- Área
- devops, networking, operating-systems
Línea de trabajo
Start with the getting-started Dockerfile at line 6 and the Compose build that runs pip install -r requirements.txt. Reproduce the reported commands and check the busybox nslookup result to determine whether the failure is in the project or the host's container networking. Done means identifying a reproducible project issue or documenting the required environment fix.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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 ?
- Lenguaje dominante
- JavaScript
- Estrellas
- 3.1k
- Forks
- 6.4k
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de docker/getting-started
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
docker/getting-started#481 · 2 comentarios · 5 reacciones ·
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 65/100
docker/getting-started#394 · 1 comentario · 3 reacciones ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
docker/getting-started#494 ·
-
Chat Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 10/100
docker/getting-started#482 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 1/100
docker/getting-started#477 ·
Todos los issues de docker/getting-started
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
Daemon passes --experimental-wasm-jspi unconditionally on Node >= 24; Node 26 rejects the flag Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Automattic/studio#4908 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
sugarlabs/musicblocks#8847 ·