`docker build .` [email protected]: The engine "node" is incompatible with this module
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
- Estancado
- Stack tecnológico
- docker, go, node.js
- Área
- build-system, devops
Línea de trabajo
Comienza con el Dockerfile y la salida fallida de docker build ., especialmente con los pasos buffalo build --static y dep ensure -v. Rastrea el error del motor de Node y los fallos de las restricciones de dependencias de Go reportados; se considera terminado cuando la compilación de Docker se completa correctamente sin esos errores.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
error [email protected]: The engine "node" is incompatible with this module. Expected version ">=4 <=9". Got "12.19.0"
error Found incompatible module.
By reverting to a much earlier Docker build, I was able to get closer to a finished build, but the build still crashes...
# Dockerfile
#FROM gobuffalo/buffalo:development as builder¬
FROM gobuffalo/buffalo:v0.14.7 as builder¬
Unfortunately, even after switching to the v0.14.7 Docker image, I get a long list of constraint failures...
Step 9/17 : RUN buffalo build --static -o /bin/app
---> Running in 29f08a8ad06d
Solving failure: No versions of github.com/gobuffalo/buffalo met constraints:
v0.11.0: Could not introduce github.com/gobuffalo/[email protected], as its subpackage github.com/gobuffalo/buffalo/runtime is missing. (Pa
ckage is required by (root).)
The code here was last updated April 19, 2018.
I also found the docker image tagged updater-enhancements was also completed on April 19, 2018, however I still can't get it to build.
Solving failure: No versions of github.com/shurcooL/octicon met constraints:
master: unable to deduce repository and source type for "dmitri.shuralyov.com/text/kebabcase": unable to read metadata: multiple meta tags match import path "dmitri.shuralyov.com/text/kebabcase"
The command '/bin/sh -c dep ensure -v' returned a non-zero code: 1
I also saw:
(1) ← backtrack: no more versions of github.com/gobuffalo/buffalo to try
(1) ? continue github.com/gobuffalo/buffalo with 6 pkgs; 75 more versions to try
(1) try github.com/gobuffalo/[email protected]
(2) ✗ github.com/gobuffalo/[email protected] not allowed by constraint ^0.11.0:
(2) ^0.11.0 from (root)
(1) try github.com/gobuffalo/[email protected]
(2) ✗ github.com/gobuffalo/[email protected] not allowed by constraint ^0.11.0:
(2) ^0.11.0 from (root)
(1) try github.com/gobuffalo/[email protected]
(2) ✗ github.com/gobuffalo/[email protected] not allowed by constraint ^0.11.0:
(2) ^0.11.0 from (root)
(1) try github.com/gobuffalo/[email protected]
(2) ✗ github.com/gobuffalo/[email protected] not allowed by constraint ^0.11.0:
(2) ^0.11.0 from (root)
(1) try github.com/gobuffalo/[email protected]
(2) ✗ github.com/gobuffalo/[email protected] not allowed by constraint ^0.11.0:
(2) ^0.11.0 from (root)
(1) try github.com/gobuffalo/[email protected]
(2) ✗ github.com/gobuffalo/[email protected] not allowed by constraint ^0.11.0:
(2) ^0.11.0 from (root)
(1) try github.com/gobuffalo/[email protected]
Tried to fix it with a slightly less old Docker image (tagged vgo) but still can't get the build to complete.
- Lenguaje dominante
- Go
- Estrellas
- 4
- Forks
- 0
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Sin guía de contribución
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.
Issues similares
-
kind/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
kubevirt/kubevirt#19559 · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
bug raised-by:verifier
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
medici-finance/assay#3817 ·
Los mantenedores suelen responder en 1 día
-
automation models
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
gtsteffaniak/filebrowser#3244 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
QuantumNous/new-api#7930 ·
Los mantenedores suelen responder en 1 día