Closed uessrodriguez closed 1 year ago
Hello!
Could you solve the issue, or the issue is still relevant?
Yes, it's solved compiling and using the jar created in docker.
Thanks
If I understand correctly, did you build your own docker image?
Really we change the Jar in the docker image, but yes, we build a new docker image changing a bit the docker compose.
Thanks.
If your docker compose is public, could you please share it, so I can update the images?
HI, its not public :( sorry, but the only change was: add another entry in volumen section with link to our compiled JAR.
As you see is a fix to use our compiled JAR, I Think that Service JAR SERVICEREGISTRY in docker image is wrong or something...
I have run into the same problem. Recompiling the jar and recreating the Docker image with the new asset was the solution for me.
@dorinelfilip Would you mind giving a more detailed description on how you did it? I have the same issue and am new to docker so I don't understand the steps you took to solve it
@esen96 I managed to resolve this issue by changing the core_system_config/serviceregistry.properties file from
core_system_name=SERVICEREGISTRY
into
core_system_name=SERVICE_REGISTRY
Seems to be a typo in the properties file. Hope this helps.
Hello,
we have just released the v4.6.1, where a more flexible docker approach has been taken and bug fixes were managed. Take a look and please open a new issue if you still runs into some error.
Hello
Trying deploy a docker enviroment from docker path directory https://github.com/eclipse-arrowhead/core-java-spring/tree/master/docker
Following the steps.
Plus: I've removed a space at the end, in file https://github.com/eclipse-arrowhead/core-java-spring/blob/master/docker/core_system_config/serviceregistry.properties in line core_system_name=SERVICEREGISTRY
With all AMD versions, with database created and filled
I can't start the SERVICEREGISTRY
Others container runs well, ORCHESTRATOR as example
But all infraestructure depends of SERVICEREGISTRY :(
What I can be doing wrong?
TIA