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

🐞 Bug - services not starting locally #3585

Open
3 of 4 tasks
B-Prod opened this issue Dec 2, 2024 · 0 comments
Open
3 of 4 tasks

🐞 Bug - services not starting locally #3585

B-Prod opened this issue Dec 2, 2024 · 0 comments
Assignees

Comments

@B-Prod
Copy link

B-Prod commented Dec 2, 2024

🖥️ Site(s) concerné(s)

  • DomiFa - côté structures
  • Mon DomiFa - portail domiciliés
  • Admin DomiFa
  • Metabase

🚫 Description du problème

The 3 following services do not build:

  • portail-admins
  • portail-usagers
  • frontend

To reproduce the issue on the frontend application, we just create a very simple docker-compose.yml file based on the provided file docker-compose.local.yml, with the following contents:

services:
   frontend:
     container_name: domifa-frontend
     hostname: domifa-frontend
     build:
       context: _scripts/dev
       dockerfile: local-node.dockerfile
     command: tail -f /dev/null
     working_dir: /app/packages/frontend
     volumes:
       - ./:/app:delegated
     ports:
       - 4200:4200
     env_file:
       - ./.env
     environment:
       TZ: Europe/Paris

Then we start the service:

docker compose -f docker-compose.yml up -d
docker exec -it domifa-frontend bash
yarn install
yarn start

The yarn start command throws the following error:

  ➜  Network: http://172.18.0.7:4200/
node:events:495
      throw er; // Unhandled 'error' event
      ^
Error: spawn xdg-open ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:284:19)
    at onErrorNT (node:internal/child_process:477:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on ChildProcess instance at:
    at ChildProcess._handle.onexit (node:internal/child_process:290:12)
    at onErrorNT (node:internal/child_process:477:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn xdg-open',
  path: 'xdg-open',
  spawnargs: [ 'http://localhost:4200/' ]
}
Node.js v18.20.0

Structure concernée (optionnel)

No response

🔮 Comportement attendu

The yarn start command should run without errors, allowing to access the application through the expected URL.

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

No branches or pull requests

2 participants