That worked for running holoscape, installing PeerChat, setting up identity and all that.
When attempting to build my project, however, I’m running into an issue with cargo talking to github. It appears as though this isn’t a new/unknown issue with cargo, and @wollum has fought it in the past. That said, I haven’t found a way to get the workaround presented in that issue to work, as it involves intentionally setting your username/password for a proxy in an environment variable and I’m not sure what to use for that in the WSL specific setup.
[nix-shell:/mnt/c/holochain/memory-vault]$ hc package
cargo build --release --target=wasm32-unknown-unknown
Updating git repository https://github.com/holochain/holochain-rust
warning: spurious network error (2 tries remaining): failed to mmap. Could not write data: Permission denied; class=Os (2)
In troubleshooting I have confirmed that git cli is working from within my ubuntu setup, I have not yet apparently found the right spot for the cargo config update to tell it to use git cli instead, but hope that will fix it once I get the right config updated.
No luck on getting the config to pull from git cli (or if any change has happened I still see the spurious permission denial).
I have found, however, that if I stay in ubuntu yet outside of nix-shell and run ~/.hc-linux package, it will build just fine, so it’s not specifically about WSL2/ubuntu, but is specific to something in the nix-shell setup.
@petersgrandadventure WSL2 worked OK for me on my spectre/windows but it was noticeably slugglish compared to linux/mac/nixos running the same commands
even using virtualbox ubuntu or something and running nix-shell inside there was faster for me than WSL2 - take this all with a grain of salt though because i was using an early developer preview of WSL2 and didn’t spend any time looking into performance optimisations