Bitcoin node not booting properly in clarinet integrate
Issue: local devnet is not working, with both bitcoin-node and stacks-node stuck in yellow booting status in the clarinet status window
Expected behaviour: bitcoin-node will start generating blocks allowing stacks-node to connect properly
Environment:
- clarinet v1.4.2
- docker desktop v4.17.0
- Windows 11
Notes: both project and docker are fresh installs. I was able to start the devnet on my first try and it worked fine. However, subsequent tries always give the same issue, with the logs looking exactly the same.
2023-03-09-stacks-bitcoind-log.txt 2023-03-09-stacks-stacksd-log.txt 2023-03-09-stacks-project-logs.zip
Hi @PatrionDigital! Could you retry with the latest clarinet? v1.5.1.
Thanks!
Action: improve cleaning before re-creating / starting containers. We should also investigate the very first fun.
@lgalabru I am facing the same issue.
This usually happens when your VM runs out of space. @ummarikram could you check this?
Yes, I think it is a memory issue. Docker tends to take up a lot of ram. I restricted the memory usage for it and it works
@ummarikram How much RAM ended up working for you here?
@smcclellan I had to restrict docker with the following settings in the .wslconfig file
[wsl2]
memory=1GB # Replace 1GB with the desired memory limit
processors=2 # Replace 2 with the desired CPU limit
@LakshmiLavanyaKasturi Could you add this to troubleshooting?
@MicaiahReid Could this be linked to #974
Yes, I think so. A Linux system using the bind_containers_volumes = true feature should use a lot less memory. However, on Mac, increasing the amount of memory available to docker is a workaround.
I think all that's left to do here is to add some of this information to our troubleshooting guide.
Closing this one. If similar issues happen again, I recommend opening a new issue referencing this one to make it easier to track