khast3x / Redcloud

Automated Red Team Infrastructure deployement using Docker
MIT License
1.19k stars 202 forks source link

Some issues with the templates and questions #25

Open KyleWebster46 opened 1 year ago

KyleWebster46 commented 1 year ago

Hello all, I have been working on using RedCloud for a school project and I have run into a few issues. Some background information: I am using AWS EC2 as my cloud provider to host RedCloud. I am able to successfully install and run RedCloud in my environment with no errors. When I go to launch a container from the templates page is where I run into issues. Some templates work just fine and launch the appropriate container. Others will spin their wheels for a while and then an error message pops up that says the Image does not exist. Both the Kali vms seem to be doing this right now. Other times A container will successfully launch and when I go to launch a terminal it says that the container is restarting, despite the container status being displayed as running. I have checked docker hub, and both of the images the kali vms are missing do not seem to exist on there. I'm not sure if it is something I am doing, or a bug within the current version. Please let me know!

I also have an additional question about the dvwa container. Dvwa is one of the containers that seems to work properly, however I am unsure how to access the web UI once the container is deployed. I tried clicking on the "published ports" within the portainer UI, however that does not lead anywhere. Any help would be greatly apricated! Thanks!

khast3x commented 1 year ago

Hello,
I am currently traveling so I cant help with specifics, but I think the official kali docker image has been renamed to https://kalilinux/kali-rolling here so you might need to reflect this change in the templates.yml file. The other unofficial kali did not change IIRC but you might need to confirm that.
In general, try launching the docker image without Redcloud, and see from there. Same for DVWA. But for DVWA you might need to add the ports to publish in the Portainer app before running the container.
I'll mark this issue so that maybe someone else can help you out more.

Cheers!