Troubleshooting

Try to git clone with both SSH and HTTPS formats. Here are the two commands to try:

git clone --recurse-submodules https://github.com/Zeus-Labs/ZeusCloud.git

git clone --recurse-submodules git@github.com:Zeus-Labs/ZeusCloud.git

Docker may not be running on your system, and you may need to restart it.

Docker / Docker Desktop may not be running on your system, and you may need to restart it.

Make sure port 80 is not occupied by other projects / containers / etc.

If deploying ZeusCloud doesn’t work, you may find a neo4j container log stating Invalid memory configuration - exceeds physical memory.

This happens if ZeusCloud requires more memory than available on Docker Desktop. Some fixes include

• Increase the memory allocated to Docker Desktop. The default is usally 2 GB. Here’s some documentation on increasing memory allocated.
• Reduce the memory used by ZeusCloud. In the docker-compose.yaml file, reduce the values of NEO4J_dbms_memory_pagecache_size, NEO4J_dbms.memory.heap.initial_size, and NEO4J_dbms_memory_heap_max__size. The default values are 250m.
• Delete existing containers, images, and volumes to make room for ZeusCloud.

If the ZeusCloud scan doesn’t complete, you may find a botocore.exceptions.NoRegionError in the logs for the cartography container.

This may be because you have not assigned a region to the named profile that ZeusCloud is using to connect to your AWS environment. Edit the AWS_CONFIG_FILE (default is ~/.aws/config) to specify a region for the named profile.

If you are not deploying locally (on an AWS VM, for instance), you will need to change the WEBSITE_DOMAIN and REACT_APP_API_DOMAIN environment variables in the .env file before deploying. Examples are http://<your-vm-ip>:80 or https://<your-deployed-domain>:443.

If your deployment of ZeusCloud reaches an irreversibly screwed up state, you may want to start over from scratch. Delete any persistent data with a make clean and then redeploy.

make clean
make quick-deploy