Bug Report: npm run setup command encountering an issue when starting Docker Containers on Linux

[Aad1tya27]

Describe the bug
When running npm run setup, and choosing to start the docker containers, we encounter an error because of the outdated version of docker compose being used in setup.ts .

To Reproduce
Steps to reproduce the behavior:

1. Run npm run setup in the root folder of the talawa-api.
2. Select all default options, and answer "Are you setting up this project using Docker?" with Y.
3. Answer "Do you want to start the Docker containers now?" with Y

Expected behavior
Docker containers should have started and docker build file should have run in detached mode.

Actual behavior
Error: spawn docker-compose ENOENT
Error running docker-compose: Error: spawn docker-compose ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:286:19)
at onErrorNT (node:internal/child_process:484:16)
at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
errno: -2,
code: 'ENOENT',
syscall: 'spawn docker-compose',
path: 'docker-compose',
spawnargs: [ '-f', 'docker-compose.dev.yaml', 'up', '--build', '-d' ]
}
Some error occurred: Error: spawn docker-compose ENOENT

Screenshots

Additional details
In the setup.ts file, the spawn function takes "docker-compose" as the command for Linux Users. Now this function is deprecated and by default on Docker Desktop or Compose installation, Docker Compose V2 is installed.

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

• Student Internship Programs talawa#359

[Aad1tya27]

Can I work on this issue?

[github-actions]

Congratulations on making your first Issue! 🎊 If you haven't already, check out our Contributing Guidelines and Issue Reporting Guidelines to ensure that you are following our guidelines for contributing and making issues.