Fixing Docker Compose

[thdelmas]

Description
Docker Compose fails when running it

• Tested on macOS Big Sur - version 11.6

Why

Solving this issue aims to simplify two things:

• Onboarding new contributors by providing an easy plug&play setup
• Deploying services and their updates on the servers

Level

Level required to conclude this issue
Beginner

Current behavior

Currently running docker-compose up will not work

gitpay-frontend-1 | SyntaxError: Unexpected token {
gitpay-frontend-1 | npm info lifecycle frontend@1.0.0~dev: Failed to exec dev script
gitpay-frontend-1 | npm ERR! code ELIFECYCLE
gitpay-frontend-1 | npm ERR! errno 2
gitpay-frontend-1 | npm ERR! frontend@1.0.0 dev: `webpack serve --progress`
gitpay-frontend-1 | npm ERR! Exit status 2
gitpay-frontend-1 | npm ERR!
gitpay-frontend-1 | npm ERR! Failed at the frontend@1.0.0 dev script.
gitpay-frontend-1 | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
gitpay-frontend-1 |
gitpay-frontend-1 | npm ERR! A complete log of this run can be found in:
gitpay-frontend-1 | npm ERR!  /root/.npm/_logs/2023-09-20T16_43_22_681Z-debug.log

Expected behavior

After cloning the repo from main branch and running docker-compose up should set-up the project locally and all services should be ready to listen

Useful links

• Docker Compose documentation

Screenshot attached

No Screenshots

How to reproduce the user scenario

• Scenario 1

  • Clone the project from main branch
  • cd into the repo
  • Run docker-compose up

• Scenario 2

  • Clone the project from main branch
  • cd into the repo
  • Run docker-compose -f docker-compose-linux.yml up

What you will need to complete this issue

• Optional: UML of the infra and services

Tips

• No tips

[alexanmtz]

backend_1   | The Node-API version of this Node instance is 1. This module supports Node-API version(s) 3. This Node instance cannot run this module.
backend_1   | npm info lifecycle bcrypt@5.1.1~install: Failed to exec install script
backend_1   | npm WARN The package dotenv is included as both a dev and production dependency.
backend_1   | npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/webpack-dev-server/node_modules/fsevents):
backend_1   | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
backend_1   | npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/watchpack-chokidar2/node_modules/fsevents):
backend_1   | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
backend_1   | npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.3 (node_modules/fsevents):
backend_1   | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
backend_1   |
backend_1   | npm ERR! code ELIFECYCLE
backend_1   | npm ERR! errno 1
backend_1   | npm ERR! bcrypt@5.1.1 install: `node-pre-gyp install --fallback-to-build`
backend_1   | npm ERR! Exit status 1
backend_1   | npm ERR!
backend_1   | npm ERR! Failed at the bcrypt@5.1.1 install script.
backend_1   | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
backend_1   |
backend_1   | npm ERR! A complete log of this run can be found in:
backend_1   | npm ERR!     /root/.npm/_logs/2024-02-09T22_51_33_512Z-debug.log