Sure! Thats the better approach. Just mentioning how to fix the start failure in the original setup.

Op di 16 nov. 2021 om 16:28 schreef Tomas Cohen Arazi <tomascohen@gmail.com>:
I'm more inclined to make ktd use an external rabbitmq container. But yeah, we could do it

El mar., 16 nov. 2021 12:17, Marcel de Rooy <rooy.de.m@gmail.com> escribió:
Looks like we should add this "fix". Before starting the rabbitmq service, rm -rf /var/run/rabbitmq.
Tested this in a Docker container, works fine with starting, stopping and restarting. Before that I had issues with rabbit failing to start.
Seems that ktd could use it too ?

Marcel
---------- Forwarded message ---------
Van: Marcel de Rooy <rooy.de.m@gmail.com>
Date: di 16 nov. 2021 om 14:11
Subject: Rabbitmq
To: koha-devel <koha-devel@lists.koha-community.org>


Hi all,

Nobody seeing things like this?

mkdir: cannot create directory ‘/var/run/rabbitmq’: Permission denied
Failed to create directory: /var/run/rabbitmq
/usr/lib/rabbitmq/bin/rabbitmq-server: 51: /usr/lib/rabbitmq/bin/rabbitmq-server: cannot create /var/run/rabbitmq/pid: Permission denied

Look in /var/log/rabbitmq. Does your rabbitmq service start when you run or restart a container?

The solution is simple (mkdir and chown), but it needs to be placed somewhere.

Marcel

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/