>From the error message it looks like port 9042 is already allocated on your computer. Do you have a cassandra running on it ? Have you tried removing the binding of port 9042 in the doecker-compose ?
(We bind port 9042 for querying more easily elasticsearch to know what's happening when we deploy James) Regards, Benoit Le 23/10/2016 à 03:19, Marc Chamberlin a écrit : > On 10/4/2016 2:59 PM, Marc Chamberlin wrote: >> On 10/4/2016 3:07 AM, Matthieu Baechler wrote: >>> >>> Ok, let's talk about the easy solution now : on master, the >>> README.adoc contains everything you need to start a james server >>> using docker-compose. >>> >>> Here is an excerpt : >>> >>> First, you need to build the image: >>> $ docker-compose -f dockerfiles/run/docker-compose.yml build >>> >>> Then, you just have to start the services: >>> $ docker-compose -f dockerfiles/run/docker-compose.yml up >>> >>> It should just work, let us know if it's not the case. >>> >> UH well no... Looks like something stepped on itself, probably an >> easy fix? >> >>> docker-compose -f dockerfiles/run/docker-compose.yml up >>> run_elasticsearch_1 is up-to-date >>> Starting run_cassandra_1 >>> ERROR: driver failed programming external connectivity on endpoint >>> run_cassandra_1 >>> (e788b9729497516191dca524a3848390468c8e0cccfb86aaebf548e9c3c75726): >>> Bind for 0.0.0.0:9042 failed: port is already allocated >> >> Marc... >> >> > Hi - I haven't heard back from Matthieu about this problem, if he still > around? If not, does anyone got an idea on how to solve this issue? > > Thanks in advance, Marc... > > --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
