Docker Community Forums

Share and learn in the Docker community.

Error when issuing Docker-compose up


(Thinhduckhoi) #1

Hi everyone,
I just followed this tutorial related to Docker-compose annd got stuck when issuing Docker-compose up.


Here’s the output of it:
ce_1 | 2016-03-03 08:26:17,115 [localhost-startStop-1] INFO core.StandardContext - Unable to set the web application class loader property [clearReferencesStatic] to [false] as the property does not exist. ice_1 | 2016-03-03 08:26:17,116 [localhost-startStop-1] INFO core.StandardContext - Unable to set the web application class loader property [clearReferencesStopThreads] to [false] as the property does not exist. ice_1 | 2016-03-03 08:26:17,116 [localhost-startStop-1] INFO core.StandardContext - Unable to set the web application class loader property [clearReferencesStopTimerThreads] to [false] as the property does not exist. ice_1 | 2016-03-03 08:26:17,116 [localhost-startStop-1] INFO core.StandardContext - Unable to set the web application class loader property [clearReferencesHttpClientKeepAliveThread] to [true] as the property does not exist. ice_1 | 2016-03-03 08:26:17,129 [localhost-startStop-1] INFO startup.ContextConfig - No global web.xml found ice_1 | 2016-03-03 08:26:17,369 [localhost-startStop-1] INFO [localhost].[/ice] - No Spring WebApplicationInitializer types detected on classpath ice_1 | 2016-03-03 08:26:17,385 [localhost-startStop-1] INFO [localhost].[/ice] - Initializing Spring root WebApplicationContext ice_1 | Java HotSpot™ 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000d9b47000, 30011392, 0) failed; error=‘Cannot allocate memory’ (errno=12) ice_1 | # ice_1 | # There is insufficient memory for the Java Runtime Environment to continue. ice_1 | # Native memory allocation (malloc) failed to allocate 30011392 bytes for committing reserved memory. ice_1 | # An error report file with more information is saved as: ice_1 | # /opt/ice/hs_err_pid1.log dockerice_ice_1 exited with code 1.

Any idea what the error was about? I mean do docker took that much of memory?


(Nathan Le Claire) #2

Any idea what the error was about? I mean do docker took that much of memory?

Docker doesn’t, but Java does, and Ice (from a quick glance) seems to boot at least one JVM-based application. Probably you’re trying to boot the application on VM with less than 2GB or so of memory.

Whatever environment you’re running in, give it more memory. Java simply won’t work without a decent amount of memory to chew on. If you’re running Docker in a VM on Mac or Windows, try docker-machine stop, go into the VirtualBox GUI and bump the memory allocated to the VM in its settings. Then docker-machine start again and you’re on your way.


(Thinhduckhoi) #3

Thank you so much for replying.
The system i used to test Ice-docker had just 1 GB ram, so that’s why it was not be able to run.
So i changed to another test-system featuring 8GB RAM, the memory error never happened anymore but something related to nginx.
Here’s the screenshot when i was executing the command “docker-compose up”. Could you please take a look at it and tell me how to fix it? I guess it could be configuration file of nginx but i didn’t know how to change or edit it in docker.
http://www.upsieutoc.com/images/2016/03/08/error.jpg


(Nathan Le Claire) #4

Looks like nginx is expecting to be able to proxy to some upstream (e.g. 172.17.0.2:8080/ice/dashboard/summary) which isn’t available (indeed, a quick glance at the code can enlighten you to where this rule originates). You need to figure out why ice (referenced as a now-deprecated link in the Compose YAML) is not resolving or responding properly in DNS (ice domain name is resolved to 172.17.0.2 by Docker built-in resolver).

My guess : That maven build for the ice container simply isn’t finished yet. Give it time to download all of the payloads (and hopefully display a log indicating the server is running), then hit the endpoint. If that doesn’t work, you’re in for libnetwork spelunking.


(Thinhduckhoi) #5

I checked all the file inside folder docker-ice and didn’t find anything related to 172.17.0.2 and i was kind of confused about that.
(My server’s IP is absolutely different )
A little bit information: I used the private cloud server of my company for the test. So i opened all the port as well as permit accessing from any I` address.
And i think something was wrong with that docker just as your guess.
I also installed this Ice (not by Docker) but the same error happened.