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

Development setup on Windows with Docker Desktop with WSL2 is extremely slow to create a new site #1365

Closed
guilmori opened this issue Mar 30, 2024 · 2 comments

Comments

@guilmori
Copy link

I used this guide in the past with great success:
https://github.com/frappe/frappe_docker/blob/main/docs/development.md

It was about a year ago I did this setup. The only thing I changed back then was to adapt the docker-compose.yml to not mount windows files into /workspace. Use a volume instead, so that all files are local to wsl2.

Now I try to do the same setup on a new Windows 11 machine.
I am able to init bench with success, it is running fast:
bench init --skip-redis-config-generation --frappe-branch version-14 frappe-bench

But when reach the step to create the new-site, it is extremely slow:
bench new-site --mariadb-root-password 123 --admin-password admin --no-mariadb-socket development.localhost

It gets stuck at the step showing Updating Frappe doctypes with a percentage, it takes more than 2 hours to complete. Then doing Erpnext is even longer.
I understand this step is doing migration and creating database tables.

I tried this on different Windows machines, same issue.
I even tried using docker engine installed in WSL2 Ubuntu (instead of windows docker desktop), still same issue.

Then I tried in an Ubuntu VM, and it was OK. So it seems to be related to WSL2.

Could anyone try to follow the exact step of this setup guide (on Windows) and report back if you have the same issue.

Thanks!

@guilmori guilmori added the bug label Mar 30, 2024
@guilmori
Copy link
Author

I just did another test with Docker Desktop using Hyper-V instead of WSL2, and it went very fast, no issue at all.
No sure what is going on with WSL2...

Copy link
Contributor

This issue has been automatically marked as stale. You have a week to explain why you believe this is an error.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant