Lesson 12: Connecting WSL2 to Ganache

[ChristianG77]

Hi,

I'm trying to deploy the box contract at the start of lesson 12 and am getting the error below.

The contract deploys on rinkeby so I think it might be an issue connecting WSL2 to Ganache.

Has anyone come across this problem?

christian@DESKTOP-PN8H8CK:/mnt/c/Users/chris/Dropbox/00_CODE/upgrades$ brownie run scripts/deploy_box.py
Brownie v1.17.0 - Python development framework for Ethereum

UpgradesProject is the active project.

Launching 'ganache-cli --port 8545 --gasLimit 12000000 --accounts 10 --hardfork istanbul --mnemonic brownie'...
File "brownie/_cli/main.py", line 64, in main
importlib.import_module(f"brownie._cli.{cmd}").main()
File "brownie/_cli/run.py", line 44, in main
network.connect(CONFIG.argv["network"])
File "brownie/network/main.py", line 50, in connect
rpc.launch(active["cmd"], **active["cmd_settings"])
File "brownie/network/rpc/init.py", line 93, in launch
raise RPCProcessError(cmd, uri)
RPCProcessError: Unable to launch local RPC client.
Command: ganache-cli
URI: http://127.0.0.1:8545

[cromewar]

Hi @ChristianG77 it seems it's trying to access to windows brownie config, I have some recommendations for you.

1. Make sure you have installed ganache-cli on your WSL: npm install -g ganache-cli
2. Move your projects to the Home folder of WSL, this will take the brownie configuration of linux instead of the windows one as it's on the home directory, remember this guide to access to WSL through Windows File Manager, you may see a .brownie folder on the home path: /home/yourUser/.brownie/

Tip: you can access to the home directory via console typing cd

[ChristianG77]

Hi @cromewar thanks for your response.

So I installed ganache-cli on WSL and received the below. Are any of these errors a significant issue?

I have my ganache server settings as per the below.

Then I took a copy of the code folder and placed it to \wsl$\Ubuntu-20.04\home\christian.brownie\00_CODE\upgrades. I don't need to delete the folder on Windows, correct?

I deleted the build, compiled and ran run scripts/deploy_box.py and run scripts/deploy_boxy.py --network rinkeby and received the following.

christian@DESKTOP-PN8H8CK:~/.brownie/00_CODE/upgrades$ brownie compile
Brownie v1.17.0 - Python development framework for Ethereum

Compiling contracts...
Solc version: 0.8.9
Optimizer: Enabled Runs: 200
EVM Version: Istanbul
Generating build data...

• OpenZeppelin/openzeppelin-contracts@4.3.2/Ownable
• OpenZeppelin/openzeppelin-contracts@4.3.2/ERC1967Proxy
• OpenZeppelin/openzeppelin-contracts@4.3.2/ERC1967Upgrade
• OpenZeppelin/openzeppelin-contracts@4.3.2/Proxy
• OpenZeppelin/openzeppelin-contracts@4.3.2/IBeacon
• OpenZeppelin/openzeppelin-contracts@4.3.2/Address
• OpenZeppelin/openzeppelin-contracts@4.3.2/Context
• OpenZeppelin/openzeppelin-contracts@4.3.2/StorageSlot
• Box
• BoxV2
• ProxyAdmin
• TransparentUpgradeableProxy

Project has been compiled. Build artifacts saved at /home/christian/.brownie/00_CODE/upgrades/build/contracts

christian@DESKTOP-PN8H8CK:~/.brownie/00_CODE/upgrades$ brownie run scripts/deploy_box.py
Brownie v1.17.0 - Python development framework for Ethereum

UpgradesProject is the active project.

Launching 'ganache-cli --port 8545 --gasLimit 12000000 --accounts 10 --hardfork istanbul --mnemonic brownie'...
File "brownie/_cli/main.py", line 64, in main
importlib.import_module(f"brownie._cli.{cmd}").main()
File "brownie/_cli/run.py", line 44, in main
network.connect(CONFIG.argv["network"])
File "brownie/network/main.py", line 50, in connect
rpc.launch(active["cmd"], **active["cmd_settings"])
File "brownie/network/rpc/init.py", line 93, in launch
raise RPCProcessError(cmd, uri)
RPCProcessError: Unable to launch local RPC client.
Command: ganache-cli
URI: http://127.0.0.1:8545
christian@DESKTOP-PN8H8CK:~/.brownie/00_CODE/upgrades$ brownie run scripts/deploy_box.py --network rinkeby
Brownie v1.17.0 - Python development framework for Ethereum

UpgradesProject is the active project.
File "brownie/_cli/run.py", line 50, in main
return_value, frame = run(
File "brownie/project/scripts.py", line 53, in run
module = _import_from_path(script)
File "brownie/project/scripts.py", line 149, in _import_from_path
_import_cache[import_str] = importlib.import_module(import_str)
File "/usr/lib/python3.8/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
File "<frozen, line line, in in
ModuleNotFoundError: No module named 'home.christian.'

[cromewar]

"Is there an advantage to storing the code in the WSL environment or have I misunderstood something?"

Well the main advantage is you wont struggle with conflicts on the hostname as you are doing now, Did you solve the problem? Any other thing I could help with?

[ChristianG77]

Thanks @cromewar . So to make it work, would I need to change '@DESKTOP-PN8H8CK:' to '@wsl$'?

[cromewar]

Yes, give it a try, I simpler might be just move the project folders to WSL.

[ChristianG77]

I tried moving the project folders to WSL and loading VS Code using that path and received this error, 'ModuleNotFoundError: No module named 'home.christian.'

This is why I was wondering if the '@DESKTOP-PN8H8CK:' needed to change to '@wsl$'?

[cromewar]

That's estrange I've never faced a conflict with the hostnames, as you should select the interpreter on vscode which might be a virtualenv on your wsl path, please give a try changing the hostname, hope you can solve your problems.