Marcin Kozlowski

I have noticed it reads the coverage and corpus from output directory automatically upon subsequent start. But this is something different, right? Is --seed taking a directory parameter? Or just...

Thank you for your issue @srikr Here is a sample solution to give you an idea where to look for. Clone this branch (private_key) https://github.com/marcinguy/betterscan-ce/tree/private_key go to docker folder and...

@srikr Better solution is to make it in backend and frontend. The above setup assumes you have cloned the repo to user directory (i.e /home/user/betterscan-ce or so) and private key...

@srikr It should also run as root. Hmmm Do you have cloned code in /root/betterscan-ce? Try to clone using git command in /root to make sure key (priv/pub) is ok

@srikr Yes. See docker-compose.yml mappings. It has to be in user directory. Otherwise you need to adjust mappings. Place betterscan in /root/betterscan-ce

@srikr Yes, you can change the mapping, but with /root/betterscan-ce and current mapping it should work Can you try to run 1) git -c core.sshCommand="ssh -i /root/.ssh/id_rsa" clone [email protected]:avinetworks/avi-dev.git Does...

@srikr I think I see the problem Your key is passphrase protected. See: `Enter passphrase for key '/root/.ssh/id_rsa': ` So it will not work like this with Betterscan. Key needs...

@srikr FYI It works on my end, with key without passphrase protection

@srikr If you need to have a key with passphrase you can try this: ssh-add /root/.ssh/id_rsa Enter your passphrase Start betterscan-ce under the same user Hopefully betterscan can later see...

@srikr Good and bad news. You have to debug your issue. It seems like a different issue. Try also different repositories. I never encountered it like you. For me the...