Develop docker-compse service locally - package.json: engines.node must be specified

Product support
12

Actually, there is no package.json .
Rather, there is a docker-compose.yml .

Nonetheless, for some reason the CLI is failing to find or to parse the docker-compose.yml file in the “current working directory” (current folder). When this happens, the CLI looks for a Dockerfile or a package.json file as alternatives. Suggestions:

  • Check that the balena push command is being executed on the correct folder – i.e. run cd to the folder where docker-compose.yml is, or use the --source option (CLI issue 1421).
    • In particular, check that balena push is not being executed in a project subdirectory (perhaps one that contains a package.json file).
  • Check that the docker-compose.yml file is not listed in any .gitignore or .dockerignore files, even any such files in project subdirectories (CLI issue 1032).
  • Check that the docker-compose.yml file meets the compatibility requirements (even though this should not be the problem, as you mentioned that git push works):

Could any of the above be the case?

1 Like