Something up with build engine?

Product support
1

Hi, I’m seeing some strange behavior where pushing my docker-compose.yml fails. I’ve tried on several different applications and continue to get this error:

[Error]    Could not detect project type: Service main: package.json: engines.node must be specified
[Error]    Not deploying release.
Remote build failed

The release logs show that Balena is trying to build this generic compose file, which is not what I’m pushing:

version: '2.1'
networks: {}
volumes:
  resin-data: {}
services:
  main:
    build:
      context: .
    privileged: true
    tty: true
    restart: always
    network_mode: host
    volumes:
      - 'resin-data:/data'
    labels:
      io.resin.features.kernel-modules: '1'
      io.resin.features.firmware: '1'
      io.resin.features.dbus: '1'
      io.resin.features.supervisor-api: '1'
      io.resin.features.resin-api: '1'
4

Hi.

What does your project structure look like?
What exact commands are you running?
Can you share any additional context?

While the error message itself is not super helpful, I suspect that there’s something off with the project configuration.
For example, this thread discusses the identical error that was caused by Dockerfile.template mistakenly named dockerfile.template.

1 Like
6

Sorry yeah, false alarm I had a formatting error in the compose file I believe. Refreshed the repo and it fixed itself. Thanks for the tip.