Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixing Docker Compose #1010

Open
thdelmas opened this issue Sep 24, 2023 · 1 comment · May be fixed by #1131
Open

Fixing Docker Compose #1010

thdelmas opened this issue Sep 24, 2023 · 1 comment · May be fixed by #1131
Milestone

Comments

@thdelmas
Copy link

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 [email protected]~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! [email protected] 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 [email protected] 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

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
Copy link
Member

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 [email protected]~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: [email protected] (node_modules/webpack-dev-server/node_modules/fsevents):
backend_1   | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
backend_1   | npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/watchpack-chokidar2/node_modules/fsevents):
backend_1   | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
backend_1   | npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
backend_1   | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: 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! [email protected] 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 [email protected] 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

@alexanmtz alexanmtz added this to the v2.0 milestone May 29, 2024
@leej3 leej3 linked a pull request Sep 20, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants
@alexanmtz @thdelmas and others