Starting fails

[zombor]

When i start a rabbit container under dokku, I get this output and the container exits:

Warning: PID file not written; -detached was passed.
ll_alloc: Cannot allocate 247463936 bytes of memory (of type "port_tab").
Aborted (core dumped)
ll_alloc: Cannot allocate 247463936 bytes of memory (of type "port_tab").
Aborted (core dumped)
ll_alloc: Cannot allocate 247463936 bytes of memory (of type "port_tab").
Aborted (core dumped)
ll_alloc: Cannot allocate 247463936 bytes of memory (of type "port_tab").
Aborted (core dumped)
ll_alloc: Cannot allocate 247463936 bytes of memory (of type "port_tab").
Aborted (core dumped)
ERROR: node with name "rabbit" already running on "23c88f597f33"

If I run the command manually in docker without $RABBITMQ_PASSWORD manually, it seems to work:

docker run --rm -v /tmp/rabbitmq/staging:/opt/rabbitmq -p 5672 -p 15672 jlachowski/rabbitmq:latest /usr/bin/start-rabbitmq.sh                   

              RabbitMQ 3.4.0. Copyright (C) 2007-2014 GoPivotal, Inc.
  ##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
  ##  ##
  ##########  Logs: /var/log/rabbitmq/[email protected]
  ######  ##        /var/log/rabbitmq/[email protected]
  ##########
              Starting broker... completed with 6 plugins.

[lenada]

@zombor which docker version are you running? I have similar issues and wonder wether upgrading from docker 1.0 to 1.3 is related. possibly related to #8 as well? When running dokku rabbitmq:create APP files in the volume directory are owned by root. When redeploying the app, rabbitmq container is not able to read datafiles from mounted volume and therefore creates new ones.. and therefore fails to start at some point.