root
/
rabbitmq-server
mirror of https://github.com/rabbitmq/rabbitmq-server.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity
rabbitmq-server/deps/rabbitmq_prometheus/docker/erlang.cookie

2 lines
20 B
Plaintext
Raw Normal View History

Mount .erlang.cookie file Context: we want to move away from environment variables and use either config files or env files (such as the rabbitmq-env.conf). Since .erlang.cookie is neither, the official RabbitMQ Docker image handles this by writing the value from the RABBITMQ_ERLANG_COOKIE env var into the file if it does not exist. The problem is that if this file exists, and the value is different from the RABBITMQ_ERLANG_COOKIE env var, CLI tools will not be able to communicate with the rabbit node, as described here: https://github.com/rabbitmq/rabbitmq-cli/issues/443 The only gotcha is that this file must be owned by the user, and privileges should not be too open (git should have captured this). If not, RabbitMQ will fail to boot. This is somewhat similar to how OpenSSH reacts when private key permissions are too open. re https://github.com/docker-library/rabbitmq/pull/422#issuecomment-650074731 Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
2020-07-02 00:07:16 +08:00
rabbitmq-prometheus