docker-compose fails to start about crapi HOT 7 CLOSED

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

from crapi.

I found one more possibly relevant error

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

from crapi.

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

from crapi.

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.

from crapi.

from crapi.

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.

from crapi.

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

from crapi.