When using 'wasp new', I get the error: wasp-bin: /home/callum/WaspProjects/wsl-test: createDirector
I am running in adminisrator mode
5 Replies
Hi @csbk. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
It looks like you're encountering a permission error when trying to create a new Wasp project. This error typically occurs when Wasp doesn't have the necessary permissions to create directories in your specified location.
Based on your mention of "administrator mode" and the error path showing "/home/callum/WaspProjects/wsl-test", it appears you're using WSL (Windows Subsystem for Linux).
Here are a few potential solutions:
1. Check if the directory already exists: Wasp cannot create a new project in a directory that already exists. As noted in the GitHub issues, Wasp's behavior is similar to Git in this regard - it won't initialize in a non-empty directory Github Issue #760.
2. PATH issues: Make sure Wasp is properly installed and in your PATH. If you see warnings about PATH during installation, you may need to add Wasp to your PATH by adding this line to your shell configuration file (~/.bashrc, ~/.zshrc, etc.):
Then reload your configuration with
source ~/.bashrc or equivalent Discord support thread.
3. File system location in WSL: If you're using WSL2, make sure your project is on the Linux file system, not the Windows file system. This is crucial because Wasp won't be able to detect file changes properly if it's on the Windows file system due to a known WSL2 issue Wasp Docs.
4. Permission issues: You might need to check the permissions of the parent directories. Try creating the project in a different location where you definitely have write permissions.
5. Read-only subdirectories: There's a known issue with Wasp when the waspc_datadir contains read-only subdirectories Github Issue #1161.
If you continue to have issues, you might want to join the Wasp Discord community where other WSL users might be able to help with your specific setup.
Let me know if any of these suggestions help resolve your issue!
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @csbk, 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 @csbk, looks like a permission issue. Can you share the screenshot of the command and error?
Also, make sure you've follwed the guide at: https://wasp.sh/blog/2023/11/21/guide-windows-development-wasp-wsl
There are some gotchas with WSL
A Guide to Windows Development with Wasp & WSL | Wasp
<ImgWithCaption
Hi @sodic , thanks very much. I managed to work it out in the end by going through it again and a little help elsewhere
Glad to hear it! Anything we could have documented better?
@sodic I would say it was more of me being a newbie than documentation on your end.