wasp start error
wasp start fails with a bunch of errors like "npm warn cleanup Failed to remove some directories"
and "Error: EPERM: operation not permitted, rmdir " on windows wsl ubuntu
4 Replies
Hi @jaeba. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the information in the knowledge sources, it appears you're experiencing permission issues when running
wasp start in WSL on Windows. This is a common issue that can occur for several reasons.
Possible causes and solutions:
1. WSL File System Location:
If your Wasp project is located on the Windows file system (rather than the Linux file system within WSL), you might encounter file permission issues. Wasp won't be able to detect file changes properly due to a known issue in WSL2.
As mentioned in the documentation, you should ensure your Wasp project is on the Linux file system, not the Windows file system:
"If you are using WSL2, make sure that your Wasp project is not on the Windows file system, but instead on the Linux file system. Otherwise, Wasp won't be able to detect file changes, due to the issue in WSL2." Quick Start Documentation2. Docker Permissions: If you're using Docker with Wasp (for database functionality), you might need to set up Docker permissions correctly: - You can follow the Docker post-installation steps for Linux to manage Docker as a non-root user - Alternatively, installing Docker Desktop might make the process easier, as mentioned in one of the support threads 3. File Ownership Issues: The error messages about "operation not permitted" suggest you might have permission/ownership issues with the files and directories in your project. Recommended steps: 1. Try running
wasp clean in your app directory and then wasp start again. This will remove old node_modules and might resolve permission issues.
2. Make sure your project is located in the Linux file system of WSL, not on the Windows file system (not in /mnt/c/ or similar paths).
3. If you're still having issues, you might want to check out this guide specifically for Windows development with Wasp and WSL: Guide to Windows Development with Wasp and WSL
If these steps don't resolve your issue, you might want to join the Wasp Discord community for more specific help with your setup.
I hope this helps you resolve the issue!
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @jaeba, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?hey @jaeba did you follow the guide to using WSL on windows with Wasp?
yes I got it working! thanks for your reply!