Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [kapua-dev] ip addres in kapua docker containers is hardcoded

Hi Pablo,

you can change that using environment variable (SQL_SERVICE_HOST). There is also H2 image that should start the db, but we still have work to do to populate the db. 

All images are built using maven plugin https://github.com/eclipse/kapua/blob/develop/assembly/pom.xml#L412 and some instructions on how to run it inside openshift https://github.com/eclipse/kapua/blob/develop/paas/openshift/openshift-deploy.sh.

It’s still work in progress, so it’s not fully functional, but it should be in a couple of days.




On Mon, Nov 28, 2016 at 4:23 PM, Pablo Chacin <pablochacin@xxxxxxxxx> wrote:
Hi

I just started playing with the kapua docker containers gracefully provided by Henryk Konsek and  Dejan Bosanac at dockerhub. I started with the kupua broker (https://hub.docker.com/r/hekonsek/kapua-broker/) but I'm getting the following error:

Caused by: org.h2.jdbc.JdbcSQLException: Connection is broken: "java.net.SocketTimeoutException: connect timed out: 192.168.33.10:3306" [90067-192]

The problem is that the address for the sql database seams to be hardcoded to the address used in the vagrant demo machine (https://github.com/eclipse/kapua/blob/develop/dev-tools/src/main/vagrant/demo/demo-Vagrantfile)

Is there a way to change this address? Or even better, are the Dockerfiles for these container available somewhere? 

Regards

--

_______________________________________________
kapua-dev mailing list
kapua-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev




--
Regards
--
Dejan Bosanac
about.me/dejanb

Back to the top