setup of talawa-api in local machine using docker is giving error regarding "PWD" variable not set correctly

[DipanshuOjha]

Describe the bug
A clear and concise description of what the bug is.

This bug is regarding docker-compose.dev.yaml file because of which we are not able to set-up talawa-api in our system.

Expected behavior
It should setup the talawa-api by successfully creating 3 docker containers

1. mongodb
   2.redis-stack-server
   3.minio
   upon which the "talawa-api-dev" services depends

Actual behavior
A clear and concise description of how the code performed w.r.t expectations.
Error indicate that mongodb is not able to established connection with other containers

I have attached the screenshot for more detail

Screenshots

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

• Student Internship Programs talawa#359

[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.

[vaibhavityagi]

This is a redis-stack-server not found error, which occurs due to the talawa-api container creating a default network when it is first mounted. And then obviously there are issues with the caddy service.

I have faced all these issues while trying to set up the project locally and spent hours finding the fix. I would love to take it up!

[pranshugupta54]

@vaibhavityagi, You currently have 2 issues. Our policy is to assign no more than two issues to each contributor across all repositories. This way everyone gets a chance to participate in the projects. We sometimes give exceptions for more urgent cases and sometimes we lose track, but the policy stands. You have reached your limit, please wait until your existing issues are closed before requesting more issues. You could unassign yourself from one of the other issues too.

[vaibhavityagi]

@pranshugupta54 I have unassigned myself from one of the issues as it was already fixed.

[DipanshuOjha]

Hey
I would also like to work on this issue.

[pranshugupta54]

Hey @DipanshuOjha, this issue is already assigned. You can comment on other issues which are open and not yet assigned.

[vaibhavityagi]

I have found all the fixes. Looking for the Caddyfile fix, will raise a PR in a week

[palisadoes]

@vaibhavityagi

1. Update the setup script to modify the .env file in the root directory of the talawa-api repository to have a PWD entry as shown below. This will set up the "PWD" variable and if we again run the command for docker build, it will get successfully executed.

PWD=.

1. This must only be done when the Docker option is set
2. The "PWD" entry must not be present when the Docker option is not set
3. This behavior must be automatic
4. Valid tests must be written for your work so that this does not happen again.
   1. The setup script has its own set of tests
5. No other functionality must be altered

[abhayymishraa]

anyone working on this ?? . i found the bug because of why we are not able to access the api server on main branch through docker !! assign it to me

[abhayymishraa]

i have raised the pr but should i add the things that the workflow suggests???

[palisadoes]

1. We need the functionality as described in original issue comment.
2. You will need to make sure that the existing test that ensures the API starts is not affected. You may have to stop the app before your docker starting test begins.

[palisadoes]

During the week of November 11, 2024 we will start a code freeze on the develop branches in Talawa, Talawa Admin and Talawa-API.

We have completed a project to convert the Talawa-API backend to use PostgreSQL. Work will then begin with us merging code in the develop branches to a new develop-postrgres branch in each repository.

Planning activities for this will be managed in our #talawa-projects slack channel. A GitHub project will be created to track specially labeled issues. We completed a similar exercise last year using a similar methodology.

Starting November 12, California time no new PRs will be accepted against the develop branch. They must be applied to the develop-postrgres branch.

There are some GSoC project features that will need to be merged into develop. These will be the only exceptions.

This activity and the post GSoC 2024 start date was announced in our #general Slack channel last month as a pinned post.

[abhayymishraa]

i did fix but the caddy is giving error in the docker-compose.dev cause it didnt get ssl it will not fail in production thats why i had tallk with maintainers in the slack they adviced me to do this separate the docker-compose.cloud and fix the docker-compose.dev which i did and now if we run from the command npm run test it is working fine from system so what will now i do ? will i need to go back like how previous docker-compose.dev configuration and fix that database not connecting issue or i continue with this?? @palisadoes
also what about the pwd its fine for me i didnt get any error while others are getting error should i add a condition when start with docker option so the env add PWD = .

[abhayymishraa]

updatess??
@palisadoes

[abhayymishraa]

Also i found a bug in the testcase thats why the test cases are failing !!!! and i fixed it

[palisadoes]

Please ask the #talawa-api channel in slack

[palisadoes]

Unassigning. Inactivity in the PR

[abhayymishraa]

@palisadoes i was working on it
but i dont find where to make a pr as gc is unactive

[palisadoes]

I'm going to assign this to someone else. The PR was abandoned.
@Shriya-Chauhan You created an issue for this. Please ask to be assigned.

[Shriya-Chauhan]

@palisadoes Yes! Please assign this issue to me. I am working on this.

[Shriya-Chauhan]

Fixes I have done and thinking:

1. Added PWD=. in .env file.Reason: This will fix the path errors eg. caddyfile mount error, pwd variable error.
2. The documentation is not clear enough for all OS users wrt to docker. For eg. I faced issue Port already in use which requires off documentation assistance.

Doubt: Reason behind using 80 port?

I have made some changes. Please review! #2734

[abhayymishraa]

@Shriya-Chauhan
maybe reason behind is that it is a docker file for production so maybe both http and https request are allowed also everything is reverse proxied to the api

[palisadoes]

@Shriya-Chauhan

This may be related

• Error response from daemon: Ports are not available (80 for caddy service) during docker build  #2735