WSL Install Errors: EISDIR & symlink
I'm encountering the same issue as this thread:
https://discord.com/channels/686873244791210014/1132507430060826644/1132606906704339024
But I've tried the suggestions in the thread, and they didn't seem to work. I've tried ChatGPT to help trouble shoot, but it's not helping. So here's what I'm seeing and what I've tried.
Help?! 🙂
Here's the error history with the steps I've taken.
4 Replies
Hi @Justin Williams. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I apologize, but the knowledge sources provided don't contain specific information about the exact error you're encountering or the steps you've taken. However, I can provide some general guidance based on the available information about WSL and Wasp installation issues.
It seems you're having trouble installing Wasp on Windows Subsystem for Linux (WSL). While I don't have the exact details of your error, here are some general troubleshooting steps that might help:
1. Update WSL and Ubuntu:
Make sure your WSL and Ubuntu installation are up to date. You can do this by running
wsl --update in PowerShell and sudo apt update && sudo apt upgrade in your Ubuntu terminal.
2. Reinstall curl:
As mentioned in this Github issue comment, sometimes the issue is related to curl. Try removing the snap version of curl and installing the apt version:
3. Check your Ubuntu version:
Ensure you're using a recent version of Ubuntu. As mentioned in this Github issue comment, Wasp 0.7.1 requires glibc 2.34 or greater. If you're using an older version of Ubuntu, consider upgrading to Ubuntu 22.04 LTS (Jammy Jellyfish) which has glibc 2.36.
4. Permissions and ownership:
Make sure you have the correct permissions and ownership for the directories where Wasp is being installed. You might need to use sudo chown to change ownership of certain directories.
5. Clean installation:
If you've attempted to install Wasp before, try removing any existing Wasp-related files or directories and start with a clean installation.
If these steps don't resolve your issue, it would be helpful to see the exact error messages you're receiving and the steps you've already taken. This would allow for more specific troubleshooting advice.
For more detailed guidance on setting up WSL for Wasp development, you can check out this article on supercharging your Windows development with WSL.
If you continue to face issues, consider sharing more details about your specific errors and the steps you've taken in the Wasp Discord community for more targeted assistance.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Justin Williams, 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?An issue for you @martinsos
I deleted everything and started over and was able to get things running. Not sure what the issue was, but not worth following up here, IMO. Probably something squirly that I did or with my setup.
@Justin Williams it seems this was about the permissons in the WSL, but it is hard for me to say what exactly it was. Glad to hear you got it going though! It would help if you could maybe figure out what changed on yoru second attempt -> what might have you deleted or done differently that enabled it to work then?