Issue with wasp start
Hi, I succesfully installed wasp on my pc using wsl for windows. I also successfully created a wasp project, but when I run wasp start, I get symlink errors. The first ss is error when I run wasp start for a new project, the second is error when i run wasp db migrate dev for an existing wasp project (usemage). I understand that this is an error wth permissions, but idk what to do,
Please help...
7 Replies
Hi @e1.victor.o. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Wohooo @e1.victor.o, you just became a Waspeteer level 1!
----------------------
Based on the information provided in the knowledge sources, it appears you're encountering a common issue when using Wasp with WSL on Windows. This is likely related to file system permissions and the location of your project files. Here's what you can do to resolve this:
1. Ensure your project is on the Linux file system:
The most important step is to make sure your Wasp project is located on the Linux file system within WSL, not on the Windows file system. As mentioned in the Wasp Quick Start guide:
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.2. Check file permissions: If your project is already on the Linux file system, you might need to adjust the file permissions. You can try running the following command in your project directory: Replace
/path/to/your/project with the actual path to your Wasp project.
3. Use the latest WSL version:
Make sure you're using the latest version of WSL and that you've properly set up Ubuntu on WSL. You can follow the detailed guide in this Wasp blog post for setting up WSL correctly.
4. Docker permissions:
If you're using Docker with WSL, ensure that your Docker permissions are set up correctly. You might need to add your user to the docker group or adjust Docker Desktop settings as described in this Discord thread.
If you continue to experience issues after trying these steps, it would be helpful to provide more specific error messages or screenshots of the errors you're encountering. The Wasp community on Discord is also a great resource for getting help with WSL-specific issues.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @e1.victor.o, 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?Hello? Is there anyone that can help?
I'd recommend reading this and setting up your WSL like this: https://wasp-lang.dev/blog/2023/11/21/guide-windows-development-wasp-wsl
@Boris wrote it and it worked for most people
Followed this to the letter. Still brought me where I am now
Couple of potential issues:
1) Are you using any VPN or proxy? That can cause issues in communication between Windows and Linux in WSL.
2) It seems like an issue with NPM installation, which isn't Wasp-specific. Try running any web project in WSL
3) Is it installed on C drive? WSL can cause issues if it's not on the C drive