trailofbits/algo

Can't deploy algo due to dependency issues (multiple deployment paths tried)

mtferg86 opened this issue · 2 comments

Describe the bug

I encountered the same problem where "line 23 Ansible playbook" error was was thrown back due to incorrect dependencies being loaded in the set up process while following the instructions (occurred on MacOS, Google Shell (Linux), and Windows WSL Linux). this prevented the "./algo" command from running and after trying to debug most of the dependency issues, i also encountered problems deploying to DigitalOcean but that could be my own issues on my desktop.

I also tried to deploy using Docker and it was able to run through the prompts but had errors with deploying to DigitalOcean as well which makes me think there is a larger bug.

It appears to be due to some issues with the latest versions of python and dependencies that have been rolled back, but i didn't have enough time to further investigate.

To Reproduce

Steps to reproduce the behavior:

  1. Follow the basic directions for in the readme for MacOS, Google Shell (Linux), and Windows WSL Linux, and Docker

Expected behavior

  1. "line 23 Ansible playbook missing" causing the ".'algo" call to fail
  2. unable to deploy to cloud platforms

Additional context

See above

Full log

-will update when I try again tonight along with any temporary work arounds

PUT THE OUTPUT HERE

Algo now requires at least Python 3.8. This might be the cause of your problems.

Unfortunately, Cloud Shell only has Python 3.7.3. When configuring a new Algo download I see the error message:

ERROR: No matching distribution found for ansible-core==2.12.1

If I ignore the message and run ./algo I get:

(.env) dem@cloudshell:~/algo$ ./algo
./algo: line 23: ansible-playbook: command not found

Check the version of Python on your other platforms. For WSL make sure you're running Ubuntu 20.04 instead of 18.04.

Thanks for the reply, that is what was starting to discover (re: python 3.8) and will see if I can run through and get everything running correctly tonight (I gave up at 3am and am busy with my day job right now):

I have v3.8 on WSL and am using Ubuntu 20.04. I'll take another crack at it tonight and if I can get it to run through without problems, I'll give an update with details on what ended up working in the end.