Hello OMH Dev Group,
I'm exploring the possibility of deploying the [Authorization and Resource Servers] for omh-dsu-ri and the Resource Server for shimmer on the same VM, using mHealth's Docker images. As expected, in doing so, I have a conflict on port 8083.
Error message:
Creating
shimmer_console_1 ...
error
ERROR: for
shimmer_console_1 Cannot start service console: b'driver failed
programming external connectivity on endpoint shimmer_console_1 (c21e5cc7c3b9055c8d229c68053da2f5afbc91c70472691292dbc7455927ba99):
Bind for 0.0.0.0:8083 failed: port is already allocated'
ERROR: for console Cannot
start service console: b'driver failed programming external connectivity on
endpoint shimmer_console_1 (c21e5cc7c3b9055c8d229c68053da2f5afbc91c70472691292dbc7455927ba99):
Bind for 0.0.0.0:8083 failed: port is already allocated'
ERROR: Encountered errors while
bringing up the project.
To avoid this, even though I explicitly set port 8085 for shimmer-console (instead of 8083) in the 'docker-compose-build.yml' and 'docker-compose.yml' files, and skip installing the Console for shimmer, the Jetty still starts on port 8083 at the end of installation. There are no errors thrown at this time. But, the Resource Server of DSU which had already been published at port 8083 with the installation of omh-dsu-ri becomes dysfunctional.
Could you suggest., if there is a way to deploy both omh-dsu-ri and Shimmer on the same VM, or is it recommended to have them operating on two different VMs? If latter, how do they communicate with each other?
I've been waiting for help on this problem for a long time. Therefore, I'll appreciate your help and support. Thank you!
Best,
Divya