oppia: [Setup Issue] Can not start the dev server in setup process while using Docker on Windows
Platform: Docker on Windows
@justcrossheaven and @manishaag7 both have been facing the following issue while using python -m scripts.start while setting up the project.

Tried solutions(not worked)
- deleting
oppia_toolsdirectory - pip install future and six
Diagnosis checks
python -c "import Queue"- No output and it is the expected behavior.
@manishaag7 only got python 2 installed in his laptop.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 46 (24 by maintainers)
Hey @gp201 and @EricZLou , Thank you for your help. Finally the development server started successfully. I can access the website on
localhost:8181. To make it work, I had to downgrade my WSL 2 to WSL 1 and then I started the elastic search server on a separate terminal using this command./oppia_tools/elasticsearch-7.10.1/bin/elasticsearch.Everything is working except for this page
http://localhost:8181/community-library. It is not able to fetch the lessons from the elastic search server. On the terminal is showingtimeout errorand elastic search is not able to fetch data.@EricZLou and @gp201. I had to reset my Ubuntu 18.04 on WSL. Cleared all the data. Then again tried installing Oppia and finally this time it worked. đ . I would like to know the port number at which the Oppia is running. I am unable to find it. đ
@EricZLou and @gp201. I am trying to do a fresh install of WSL2 and will install Ubuntu 18.04 on it. I hope this will work, I will update you about the result.
Great to hear you got the devserver working @MohdImran001!!
Looks like youâve run into some connection bug that pops up every now and then for Windows developers. If a page doesnât load (like the library page), just try refreshing it and see if it loads correctly the 2nd time. In the meantime, Iâll file a bug report for this and see if we can find anything.
@MohdImran001 can you probably put a couple of print stmts in the below file and see where the problem is? https://github.com/oppia/oppia/blob/8d39eb9a2f1f1443c1b7af06e6cc43c00cafa218/scripts/start.py#L107
@MohdImran001 Can you send a picture? can you also take a pic of the CPU load and disk usage. (Not sure if it will change anything)
For development on Windows machines, we actually need to use
python -m scripts.start --no_browser. Also, thereâs an ongoing issue with failing to start localhost, and you will probably need to make the change noted here before running the start command.Let us know if that works!
@EricZLou I doubt it is an issue for Docker alone since it is occurring in WSL too. @MohdImran001 had installed Oppia in windows WSL and is facing it. see the comment above
Also if we think there may be an error in the urllib3 package, maybe itâd be easier to post an issue on their Github? Theyâre active on Github and may have some insights. @gp201
Not sure if this would make a difference, but note that the Docker for Windows instructions were never tested inside WSL or WSL2. It is meant to be done directly in Windows Command Prompt.
@MohdImran001 @manishaag7 @justcrossheaven are you all using Docker inside WSL/WSL2? If you already have WSL2 installed, youâre very close to completing the first option for Windows setup instructions (Installing Oppia in Windows and WSL2").
And Iâll try the Docker setup in Windows Command Prompt to see if itâs still functional or if it throws the same error as youâre all getting.
@manishaag7 @justcrossheaven and @MohdImran001 can you do the following change to the code:
Can you try whatâs given in the thread below and report the results here? https://github.com/python-zk/kazoo/issues/239
@MohdImran001 can you also follow this and report it here?