Unable to create docker image and vagrant vm (kali)

[guzzisec]

when i use docker to create the image show me an error "docker container is unhealthy".
in vagrant I can not enter to the crAPI application only to mailhog in port (8025).

[guzzisec]

When i run the box in virtual box only see the (8025) mail service.. but nothing happens in 192.168.33.20.

[willmccardell]

I can confirm this. When I run it across 3 different machines, the instructions provided do not work. In many of the cases, I was seeing different errors each time, but lately it's been a fairly standard error.

crapi-identity exits with status code 137. The dockerfile for it limits the Java max memory to 128mb, but increasing this and rebuilding does not fix the problem.

As you can see, crapi-identity finishes starting, but then crashes later on.

output of docker logs:

I was able to get the docker-compose command to finish twice out of maybe 60 attempts, so while it won't always fail, it almost always does.

Platforms tested on:

• AWS Linux
• Ubuntu hosted in AWS, fresh instance spun up entirely for this debugging.
  ** Linux redacted 5.15.0-1004-aws Profile Picture image not loading on Community Forum #6-Ubuntu SMP Thu Mar 31 09:44:20 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
• Kali Linux VM hosted on Windows
  ** This was the host that docker-compose finished twice on.

This problem is similar to #9

[willmccardell]

Issue fixed by increasing the memory for the crapi-identity block in docker-compose.yml to be 512M, from 256M.

[guzzisec]

i changed the crapi-identity block from 256M to 512M and don't work for me :(

im run the same command : VERSION=latest docker-compose -f docker-compose.yml --compatibility up -d

[guzzisec]

[willmccardell]

Our issues were actually different, so I created a new issue to track my problem. Exit Code 132 apparently suggests that your CPU architecture is too old, and you may need to either upgrade to a newer machine or do the steps here: https://stackoverflow.com/a/68575327 and troubleshoot. If you have access to AWS and EC2, a basic Ubuntu systems works with my change mentioned above.

[guzzisec]

yeah! it works in ubuntu EC2 with the modification that you say. Now how can I connect to the crAPI application from the internet or how can I start playing with crAPI? I am a complete noob in EC2.. thanks!

[willmccardell]

If you join the OWASP Slack community listed here and the #crapi channel there I can help you with the details later, but broadly (and kind of insecurely) speaking you have to do two things: get AWS to allow traffic to your instance and get crAPI listening on a remotely-accessible address:

• set the EC2 instance's security group to allow all traffic from your IP and only your IP (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/authorizing-access-to-an-instance.html)
• Change the docker-compose.yml file to use the IP address 0.0.0.0 instead of 127.0.0.1 (and uncomment the parts where 127.0.0.1 is used)

[guzzisec]

okay!! Thanks so much