Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker compose deployment failing in mac M1 #196

Open
ramirezfranciscof opened this issue Feb 7, 2022 · 0 comments
Open

Docker compose deployment failing in mac M1 #196

ramirezfranciscof opened this issue Feb 7, 2022 · 0 comments

Comments

@ramirezfranciscof
Copy link

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:[email protected]: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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant