docker-compose fails to start

[haicenhacks]

running the docker compose command as listed in the readme results in the following:

docker-compose -f deploy/docker/docker-compose.yml --compatibility up -d
[+] Running 3/4
 ⠿ Container mailhog         Running                                                                 0.0s
 ⠿ Container postgresdb      Healthy                                                                 1.1s
 ⠿ Container mongodb         Healthy                                                                 1.1s
 ⠿ Container crapi-identity  Waiting                                                                13.6s
container for service "crapi-identity" is unhealthy

OS information: Arch linux kernel 5.15.36-1-lts
Docker Compose version 2.4.1
Docker version 20.10.14, build a224086349

I ran docker-compose without -d, and got the following output:

crapi-identity   | 2022-04-29 19:20:33.521  INFO 7 --- [           main] com.crapi.CRAPIBootApplication           : Starting CRAPIBootApplication v1.0-SNAPSHOT on 8e8201870c71 with PID 7 (/app/user-microservices-1.0-SNAPSHOT.jar started by root in /)
crapi-identity   | 2022-04-29 19:20:33.536  INFO 7 --- [           main] com.crapi.CRAPIBootApplication           : No active profile set, falling back to default profiles: default
crapi-identity   | Killed
container for service "crapi-identity" is unhealthy
crapi-identity exited with code 137

Based on my research, 137 is the out of memory killer, which is very strange because I have 32 GB of ram, and there is no noticable change before or during the docker-compose up process.

I'm happy to help troubleshoot, but I'm not sure where to look.

[haicenhacks]

I found one more possibly relevant error

postgresdb | 2022-04-29 19:56:40.937 UTC [40] FATAL: role "root" does not exist

[PauloASilva]

Hi @haicenhacks,
meanwhile, in order to start hacking, you can consider deploying crAPI locally on a virtual machine using vagrant: I've tested it just now based on the develop branch and it worked.

Cheers,
Paulo A. Silva

[haicenhacks]

I tried vagrant as well, but it also fails.

    default: Created symlink /etc/systemd/system/multi-user.target.wants/crapi.service → /etc/systemd/system/crapi.service.
    default: Job for crapi.service failed because the control process exited with error code.
    default: See "systemctl status crapi.service" and "journalctl -xe" for details.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

is the last message when I run vagrant up. I'm new to vagrant, but since it looks like it is still using docker-compose, so whatever is preventing it from running on my system is also stopping it from running in the vm.

[PauloASilva]

Did you switch to the `develop` branch before running `vagrant up`? Before my previous comment I've done this and crAPI successfully started.

[haicenhacks]

I did some more testing. vagrant on the main branch successfully builds, but for some reason, the develop branch fails. Even the docker version works on main.

I am on 3b87cba (HEAD -> develop, origin/develop, origin/HEAD)

I guess I'll just stick with the main branch for now.

[PauloASilva]

Hi @haicenhacks,
Would you like to test PR#42: it should allow you to run crAPI from the develop branch using Vagrant.

Cheers,
Paulo A. Silva

[haicenhacks]

Ok, I think we can close this now. docker-compose and vagrant are working again on 78d8213