Is it normal for the docker compose process to take so long?

[ablackcatstail]

I am wondering if I am encountering a problem. I am trying to set up egroupware on Alma Linux 9.2. I have the docker environment installed and I am running docker compose to bring it up. However on the container creation stages for some I seem to be at over 1600 seconds. Has something gone wrong? The containers: collabora-key, egroupware-docker-mongo-init-replica-1, rocketchat, and egroupware seem stuck. Any ideas? Thanks in advance.

[itwo]

Hi,

how is the load from the server during this process?

Check the logs (german howto) to see some process has an issue:

Error-logs

[StefanU]

Hi Matt.

I am trying to set up egroupware on Alma Linux 9.2

We have not yet created a repo for AlmaLinux:
https://github.com/EGroupware/egroupware/wiki/Installation-using-egroupware-docker-RPM-DEB-package
https://download.opensuse.org/repositories/server:/eGroupWare/

We also do not actively test with RPM-based OS. We recommend Deb-based, primarily Debian, for installation.

If you prefer RPM, you can currently use the repo for CentOS 8. That means: Install via our installation package on an empty system.

If you have/are running an existing Docker environment, you can of course also integrate our containers or assemble them via docker-compose. However, you need to know what you are doing and have a certain amount of knowledge.

Please do not try to install everything directly. Better take care of EGroupware first. No Rocket.Chat, no Collabora Online, …

---

I have just tried the installation under AlmaLinux 9.2. The installation works as expected: Everything is installed, Docker runs with all containers.

But afterwards I get a 502 from the reverse proxy. We’ll have to see why that is.

As I said, we don’t actively test RPM-OS…

Stefan