search

marvel-nccr / quantum-mobile

A Virtual Machine for computational materials science
https://quantum-mobile.readthedocs.io
Other
91 stars 32 forks source link

Docker compose deployment failing in mac M1 #196

Open ramirezfranciscof opened 2 years ago

ramirezfranciscof commented 2 years ago

When I try to run the docker-compose.yml file as indicated in the launching documentation I get an unhealthy container due to problems when running the services:

CONTAINER ID   IMAGE                                COMMAND                  CREATED         STATUS                     PORTS                                                                       NAMES
5088a66f96fe   marvelnccr/quantum-mobile:20.11.2a   "/lib/systemd/systemd"   5 minutes ago   Up 5 minutes (unhealthy)   0.0.0.0:8888->8888/tcp, 0.0.0.0:8890->8890/tcp                              quantum-mobile
(aiida) max@5088a66f96fe:~$ verdi status
 ✔ config dir:  /home/max/.aiida
 ✔ profile:     On profile generic
 ✔ repository:  /home/max/.aiida/repository/generic
 ✘ postgres:    Unable to connect as aiida@localhost:5432
Error: OperationalError: could not connect to server: Connection refused
    Is the server running on host "localhost" (127.0.0.1) and accepting
    TCP/IP connections on port 5432?
could not connect to server: Cannot assign requested address
    Is the server running on host "localhost" (::1) and accepting
    TCP/IP connections on port 5432?

 ✘ rabbitmq:    Unable to connect to rabbitmq with URL: amqp://guest:guest@127.0.0.1:5672?heartbeat=600
Error: ConnectionWrongStateError: Channel allocation requires an open connection: <TornadoConnection CLOSED transport=None params=<ConnectionParameters host=127.0.0.1 port=5672 virtual_host=/ ssl=False>>
Warning: Deleted apparently stale daemon PID file as its associated process<23616> does not exist anymore
 ⏺ daemon:      The daemon is not running

It seems the problem might be related to systemd and the cgroup access. The only potential solution I was able to find seems to be the one proposed here, but honestly I haven't even tried it yet because I am very hesitant to start the container with the extra privileges they require there.

OSX version is Monterey 12.1 and docker is v20.10.11 (build dea9396).

Any ideas? @ltalirz this has not happened to you? Let me know if you need me to run any other test.