Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`docker build .` [email protected]: The engine "node" is incompatible with this module

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, go, node.js

Research direction

Start with the Dockerfile and the failing docker build . output, especially the buffalo build --static and dep ensure -v steps. Trace the Node engine error and the reported Go dependency constraint failures; done means the Docker build completes successfully without those errors.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Go
Stars
4
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.