Containerized rabbitmq versions 3.6-management+ not working with conf file

[tinakurian-pki]

Hello!

I have a docker-compose setup to run rabbitmq in a container. The setup works on windows, but not on a mac. I've also recognized that version 3.5-management does work on a mac. However, anything newer, will not work. The issue is directly related to applying a rabbitmq.conf file.

docker-compose.yaml file:

version: '3.7'
networks:
  credentials_network:
    driver: bridge
    ipam:
      config:
        - subnet: 169.254.170.0/24
          gateway: 169.254.170.1
services:
  rabbitmq:
    container_name: my-rabbitmq
    image: 'rabbitmq:3.11.5-management' # if this is changed to 'rabbitmq:3.5-management' it works!
    environment:
      RABBITMQ_SERVER_ADDITIONAL_ERL_ARGS: '-rabbitmq_stream advertised_host rabbitmq'
    ports:
      - '5672:5672'
      - '5552:5552'
      - '15672:15672'
    volumes:
      - ./rabbitmq.conf:/etc/rabbitmq/rabbitmq.conf:ro
     # - ./enabled_plugins:/etc/rabbitmq/enabled_plugins:ro
    healthcheck:
      test: rabbitmq-diagnostics -q ping
      interval: 15s
      timeout: 15s
      retries: 5
    networks:
      credentials_network:
        aliases:
          - rabbitmq
          - my-rabbitmq
volumes:
  data: {}

rabbitmq.conf file:

streamlistenerstcp1 = 5552
streamtcp_listen_optionsbacklog = 4096
streamtcp_listen_optionsrecbuf = 131072
streamtcp_listen_optionssndbuf = 131072
streamtcp_listen_optionskeepalive = true
streamtcp_listen_optionsnodelay = true
streamtcp_listen_optionsexit_on_close = true
streamtcp_listen_optionssend_timeout = 120

enabled_plugins file:
[rabbitmq_management,rabbitmq_prometheus,rabbitmq_stream,rabbitmq_stream_management].

The error i see is as follows:

Output

``` Attaching to my-rabbitmq my-rabbitmq | 2023-01-05 16:07:02.123357+00:00 [error] <0.132.0> File operation error: eperm. Target: /etc/rabbitmq/rabbitmq.conf. Function: get_file. Process: rabbit_prelaunch_sup. my-rabbitmq | 2023-01-05 16:07:02.155232+00:00 [error] <0.132.0> Error parsing configuration: my-rabbitmq | 2023-01-05 16:07:02.175412+00:00 [error] <0.132.0> - Could not open file (/etc/rabbitmq/rabbitmq.conf) for Reason undefined my-rabbitmq | 2023-01-05 16:07:02.175464+00:00 [error] <0.132.0> Are these files using the Cuttlefish format? my-rabbitmq | my-rabbitmq | BOOT FAILED my-rabbitmq | =========== my-rabbitmq | Error during startup: {error,failed_to_parse_configuration_file} my-rabbitmq | my-rabbitmq | 2023-01-05 16:07:02.180556+00:00 [error] <0.132.0> my-rabbitmq | 2023-01-05 16:07:02.180556+00:00 [error] <0.132.0> BOOT FAILED my-rabbitmq | 2023-01-05 16:07:02.180556+00:00 [error] <0.132.0> =========== my-rabbitmq | 2023-01-05 16:07:02.180556+00:00 [error] <0.132.0> Error during startup: {error,failed_to_parse_configuration_file} my-rabbitmq | 2023-01-05 16:07:02.180556+00:00 [error] <0.132.0> my-rabbitmq | 2023-01-05 16:07:03.193079+00:00 [error] <0.132.0> supervisor: {local,rabbit_prelaunch_sup} my-rabbitmq | 2023-01-05 16:07:03.193079+00:00 [error] <0.132.0> errorContext: start_error my-rabbitmq | 2023-01-05 16:07:03.193079+00:00 [error] <0.132.0> reason: failed_to_parse_configuration_file my-rabbitmq | 2023-01-05 16:07:03.193079+00:00 [error] <0.132.0> offender: [{pid,undefined}, my-rabbitmq | 2023-01-05 16:07:03.193079+00:00 [error] <0.132.0> {id,prelaunch}, my-rabbitmq | 2023-01-05 16:07:03.193079+00:00 [error] <0.132.0> {mfargs,{rabbit_prelaunch,run_prelaunch_first_phase,[]}}, my-rabbitmq | 2023-01-05 16:07:03.193079+00:00 [error] <0.132.0> {restart_type,transient}, my-rabbitmq | 2023-01-05 16:07:03.193079+00:00 [error] <0.132.0> {significant,false}, my-rabbitmq | 2023-01-05 16:07:03.193079+00:00 [error] <0.132.0> {shutdown,5000}, my-rabbitmq | 2023-01-05 16:07:03.193079+00:00 [error] <0.132.0> {child_type,worker}] my-rabbitmq | 2023-01-05 16:07:03.193079+00:00 [error] <0.132.0> my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> crasher: my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> initial call: application_master:init/4 my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> pid: <0.130.0> my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> registered_name: [] my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> exception exit: {{shutdown, my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> {failed_to_start_child,prelaunch, my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> failed_to_parse_configuration_file}}, my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> {rabbit_prelaunch_app,start,[normal,[]]}} my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> in function application_master:init/4 (application_master.erl, line 142) my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> ancestors: [<0.129.0>] my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> message_queue_len: 1 my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> messages: [{'EXIT',<0.131.0>,normal}] my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> links: [<0.129.0>,<0.44.0>] my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> dictionary: [] my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> trap_exit: true my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> status: running my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> heap_size: 233 my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> stack_size: 28 my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> reductions: 170 my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> neighbours: my-rabbitmq | 2023-01-05 16:07:03.193840+00:00 [error] <0.130.0> my-rabbitmq | 2023-01-05 16:07:03.210633+00:00 [notice] <0.44.0> Application rabbitmq_prelaunch exited with reason: {{shutdown,{failed_to_start_child,prelaunch,failed_to_parse_configuration_file}},{rabbit_prelaunch_app,start,[normal,[]]}} my-rabbitmq | {"Kernel pid terminated",application_controller,"{application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,failed_to_parse_configuration_file}},{rabbit_prelaunch_app,start,[normal,[]]}}}"} my-rabbitmq | Kernel pid terminated (application_controller) ({application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,failed_to_parse_configuration_file}},{rabbit_prelaunch_app,start,[normal,[]]}}}) my-rabbitmq | my-rabbitmq exited with code 0 ```

Any help would be greatly appreciated!

[lukebakken]

Your problem is not specific to docker, and is not a bug. You should have asked a question in one of these places:

• Mailing list - https://groups.google.com/g/rabbitmq-users
• Discussions - https://github.com/rabbitmq/rabbitmq-server/discussions

Ideally, when you report an issue, provide a git repository that can be cloned rather than file snippets. This ensures that people assisting you have the same data you are working with.

You have multiple issues at hand -

• RabbitMQ versions prior to 3.9 are unsupported, and 3.9 is going out of support soon.
• rabbitmq.conf support was added in version 3.7. RabbitMQ 3.5 has no idea what to do with the file you provide, so it appears to work.
• You are trying to use RabbitMQ stream settings, which means you must use a version of RabbitMQ that supports streams. Ideally this would be the latest version of rabbitmq, so use the rabbitmq:3-management tag.
• Finally, and this is most important, your rabbitmq.conf file is formatted incorrectly. Please read the documentation - https://www.rabbitmq.com/stream.html#configuration

Please see the following repository with a working example:

https://github.com/lukebakken/docker-library_rabbitmq-600

Run make up to start the container.

[tinakurian-pki]

Hi @lukebakken Thanks for the response.

I've tried the example repo you've provided by cloning and running make up to start the container. Here is the resulting error (it appears to be the same as the one i described above).

I also was initially trying with rabbitmq:3-management but it was failing with the same error. I had also tried directly copy/pasting the code snippet found here: https://www.rabbitmq.com/stream.html#configuration into the rabbit.conf file.

Here is the error i see from running make up after cloning https://github.com/lukebakken/docker-library_rabbitmq-600

Output

``` docker compose up [+] Running 2/2 ⠿ Network docker-library_rabbitmq-600_default Created 0.0s ⠿ Container docker-library_rabbitmq-600_rabbitmq_1 Started 0.5s Attaching to rabbitmq_1 rabbitmq_1 | 2023-01-05 17:36:41.722346+00:00 [error] <0.132.0> File operation error: eperm. Target: /etc/rabbitmq/rabbitmq.conf. Function: get_file. Process: rabbit_prelaunch_sup. rabbitmq_1 | 2023-01-05 17:36:41.753903+00:00 [error] <0.132.0> Error parsing configuration: rabbitmq_1 | 2023-01-05 17:36:41.775479+00:00 [error] <0.132.0> - Could not open file (/etc/rabbitmq/rabbitmq.conf) for Reason undefined rabbitmq_1 | 2023-01-05 17:36:41.775591+00:00 [error] <0.132.0> Are these files using the Cuttlefish format? rabbitmq_1 | 2023-01-05 17:36:41.780141+00:00 [error] <0.132.0> rabbitmq_1 | 2023-01-05 17:36:41.780141+00:00 [error] <0.132.0> BOOT FAILED rabbitmq_1 | 2023-01-05 17:36:41.780141+00:00 [error] <0.132.0> =========== rabbitmq_1 | 2023-01-05 17:36:41.780141+00:00 [error] <0.132.0> Error during startup: {error,failed_to_parse_configuration_file} rabbitmq_1 | 2023-01-05 17:36:41.780141+00:00 [error] <0.132.0> rabbitmq_1 | rabbitmq_1 | BOOT FAILED rabbitmq_1 | =========== rabbitmq_1 | Error during startup: {error,failed_to_parse_configuration_file} rabbitmq_1 | rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> supervisor: {local,rabbit_prelaunch_sup} rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> errorContext: start_error rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> reason: failed_to_parse_configuration_file rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> offender: [{pid,undefined}, rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> {id,prelaunch}, rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> {mfargs,{rabbit_prelaunch,run_prelaunch_first_phase,[]}}, rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> {restart_type,transient}, rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> {significant,false}, rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> {shutdown,5000}, rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> {child_type,worker}] rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> crasher: rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> initial call: application_master:init/4 rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> pid: <0.130.0> rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> registered_name: [] rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> exception exit: {{shutdown, rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> {failed_to_start_child,prelaunch, rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> failed_to_parse_configuration_file}}, rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> {rabbit_prelaunch_app,start,[normal,[]]}} rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> in function application_master:init/4 (application_master.erl, line 142) rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> ancestors: [<0.129.0>] rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> message_queue_len: 1 rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> messages: [{'EXIT',<0.131.0>,normal}] rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> links: [<0.129.0>,<0.44.0>] rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> dictionary: [] rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> trap_exit: true rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> status: running rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> heap_size: 233 rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> stack_size: 28 rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> reductions: 170 rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> neighbours: rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> rabbitmq_1 | 2023-01-05 17:36:42.805506+00:00 [notice] <0.44.0> Application rabbitmq_prelaunch exited with reason: {{shutdown,{failed_to_start_child,prelaunch,failed_to_parse_configuration_file}},{rabbit_prelaunch_app,start,[normal,[]]}} rabbitmq_1 | {"Kernel pid terminated",application_controller,"{application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,failed_to_parse_configuration_file}},{rabbit_prelaunch_app,start,[normal,[]]}}}"} rabbitmq_1 | Kernel pid terminated (application_controller) ({application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,failed_to_parse_configuration_file}},{rabbit_prelaunch_app,start,[normal,[]]}}}) rabbitmq_1 | rabbitmq_1 exited with code 0 ```

[lukebakken]

This is the relevant error:

File operation error: eperm

This means that RabbitMQ can't open the file. You must adjust the permissions locally so that the container can read the file. That's why I instructed you to use the make up command to start the container, instead of docker compose up

[tinakurian-pki]

@lukebakken, I did use make up - i just didnt copy/paste that in the result. Here is the full stack trace:

Output

``` make up  ✔  at 12:36:19 pm  sudo chown -R "999:999" /Users/tinakurian/Documents/github-repositories/docker-library_rabbitmq-600/rabbitmq.conf /Users/tinakurian/Documents/github-repositories/docker-library_rabbitmq-600/enabled_plugins Password: docker compose up [+] Running 2/2 ⠿ Network docker-library_rabbitmq-600_default Created 0.0s ⠿ Container docker-library_rabbitmq-600_rabbitmq_1 Started 0.5s Attaching to rabbitmq_1 rabbitmq_1 | 2023-01-05 17:36:41.722346+00:00 [error] <0.132.0> File operation error: eperm. Target: /etc/rabbitmq/rabbitmq.conf. Function: get_file. Process: rabbit_prelaunch_sup. rabbitmq_1 | 2023-01-05 17:36:41.753903+00:00 [error] <0.132.0> Error parsing configuration: rabbitmq_1 | 2023-01-05 17:36:41.775479+00:00 [error] <0.132.0> - Could not open file (/etc/rabbitmq/rabbitmq.conf) for Reason undefined rabbitmq_1 | 2023-01-05 17:36:41.775591+00:00 [error] <0.132.0> Are these files using the Cuttlefish format? rabbitmq_1 | 2023-01-05 17:36:41.780141+00:00 [error] <0.132.0> rabbitmq_1 | 2023-01-05 17:36:41.780141+00:00 [error] <0.132.0> BOOT FAILED rabbitmq_1 | 2023-01-05 17:36:41.780141+00:00 [error] <0.132.0> =========== rabbitmq_1 | 2023-01-05 17:36:41.780141+00:00 [error] <0.132.0> Error during startup: {error,failed_to_parse_configuration_file} rabbitmq_1 | 2023-01-05 17:36:41.780141+00:00 [error] <0.132.0> rabbitmq_1 | rabbitmq_1 | BOOT FAILED rabbitmq_1 | =========== rabbitmq_1 | Error during startup: {error,failed_to_parse_configuration_file} rabbitmq_1 | rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> supervisor: {local,rabbit_prelaunch_sup} rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> errorContext: start_error rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> reason: failed_to_parse_configuration_file rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> offender: [{pid,undefined}, rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> {id,prelaunch}, rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> {mfargs,{rabbit_prelaunch,run_prelaunch_first_phase,[]}}, rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> {restart_type,transient}, rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> {significant,false}, rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> {shutdown,5000}, rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> {child_type,worker}] rabbitmq_1 | 2023-01-05 17:36:42.790617+00:00 [error] <0.132.0> rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> crasher: rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> initial call: application_master:init/4 rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> pid: <0.130.0> rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> registered_name: [] rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> exception exit: {{shutdown, rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> {failed_to_start_child,prelaunch, rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> failed_to_parse_configuration_file}}, rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> {rabbit_prelaunch_app,start,[normal,[]]}} rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> in function application_master:init/4 (application_master.erl, line 142) rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> ancestors: [<0.129.0>] rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> message_queue_len: 1 rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> messages: [{'EXIT',<0.131.0>,normal}] rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> links: [<0.129.0>,<0.44.0>] rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> dictionary: [] rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> trap_exit: true rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> status: running rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> heap_size: 233 rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> stack_size: 28 rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> reductions: 170 rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> neighbours: rabbitmq_1 | 2023-01-05 17:36:42.791009+00:00 [error] <0.130.0> rabbitmq_1 | 2023-01-05 17:36:42.805506+00:00 [notice] <0.44.0> Application rabbitmq_prelaunch exited with reason: {{shutdown,{failed_to_start_child,prelaunch,failed_to_parse_configuration_file}},{rabbit_prelaunch_app,start,[normal,[]]}} rabbitmq_1 | {"Kernel pid terminated",application_controller,"{application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,failed_to_parse_configuration_file}},{rabbit_prelaunch_app,start,[normal,[]]}}}"} rabbitmq_1 | Kernel pid terminated (application_controller) ({application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,failed_to_parse_configuration_file}},{rabbit_prelaunch_app,start,[normal,[]]}}}) rabbitmq_1 | rabbitmq_1 exited with code 0 ```

[lukebakken]

I can't assume anything, so thanks for clarifying.

Please edit your comments so that you are not pasting a giant wall of text. You have two options - attach the output as a file, or surround the output like this:

<details><summary>Output</summary>

` ` `
ACTUAL OUTPUT GOES HERE
` ` `
</details>

Note that I had to insert spaces between the backticks surrounding ACTUAL OUTPUT in order for formatting to work. Do not use those spaces, obviously. Re-formatting your comments will make our discussion MUCH easier to follow.

Please remove :ro from these lines, and re-try: https://github.com/lukebakken/docker-library_rabbitmq-600/blob/main/docker-compose.yaml#L12-L14

Like I said, this works fine in a Linux environment so there may be something different about docker on OS X.

[tinakurian-pki]

@lukebakken Sure, will do that. I have removed :ro from https://github.com/lukebakken/docker-library_rabbitmq-600/blob/main/docker-compose.yaml#L12-L14, the error still persists.

Note: I have also tried adding user: root to the docker-compose file under services-> rabbitmq. This also didn't seem to make any difference.

[lukebakken]

Again, this must be specific to your environment, or to docker on OS X, though I would think we would have heard about it by now.

Give my changes a try here - https://github.com/lukebakken/docker-library_rabbitmq-600

Rather than use volumes, it will build a specific image with those files copied in.

[tinakurian-pki]

@lukebakken, that last change worked! Many thanks.

[lukebakken]

OK great. This still doesn't explain why using volumes resulted in a permission error in your environment. If you want to persist your RabbitMQ data you will have to use a volume.

[tinakurian-pki]

It would be nice to persist rabbit data. I'll keep looking into docker on macos and try to figure out how to get the permissions to work. Thanks again for your help @lukebakken.