Hmm, strange as I can’t see anything that looks obviously wrong there.
-Xms14g tells java to assign 14GB of RAM straight away to the java heap, and -Xmx14G tells it that as soon as it can’t fit the heap in 14GB to stop the process and send an out of memory flag. So it should be assigning 14GB. One thing to try would be to set the value lower (e.g. 7GB) as a test case and see if it gets past the initial startup stage. If it does, then it seems that your system can’t assign the 14GB RAM (possibly there is an override in some place that limits how much of the system RAM Docker can use). If it still fails with the lower value then the usual options of clearing Docker cache and images and then rebuilding from scratch would probably be the next option.
For the logs, java can be a bit of a pain in actually informing what is going on. It should get put in the syslog inside the docker container, but often it is the case that Docker containers don’t create that log.