When running couchbase-cli cluster-init, the --cluster-ramsize parameter appears to be ignored.

A user has reported a github issue while trying to run Couchbase Server 4.0.0-rc0 under docker, but it does not appear to be a docker issue. He's reporting that it worked fine in enterprise-4.0.0-3508.

Here's a link to the ticket:

https://github.com/couchbase/docker/issues/12

and the relevant excerpt and error message:

corbinu:~/ $ docker run -d -p 8091:8091 couchbase/server:enterprise-4.0.0-rc0
5f978d27397489968c3bb56c082d7881262fa478d1ea29b23e9d5d729838e877
corbinu:~/ $ docker exec -it 5f978d27397489968c3bb56c082d7881262fa478d1ea29b23e9d5d729838e877 /bin/bash

root@5f978d273974:/# couchbase-cli cluster-init -c 127.0.0.1:8091 \
> --cluster-username=Administrator \
> --cluster-password=password \
> --cluster-port=8080 \
> --services=data,index \
> --cluster-ramsize=300 \
> --cluster-index-ramsize=200
ERROR: unable to setup services (400) Bad Request
["insufficient memory to satisfy memory quota for the services (requested quota is 1451MB, maximum allowed quota for the node is 796MB)"]