I added a -ignore-installed flagged to the pip3 installation command of the networkbuildercoordinator to ensure a consistent installation procedure across enviroments/infrastructures.
removed the ports specified for the profiler service since they are obsolete in this service and conflict with the elasticsearch service
added the command attribute for the profiler to hold the profiler arguments (since this is appended to the ENTRYPOINT on execution). This will allow to run the profiler by simply running docker-compose up profiler and allows for easy override in docker-compose.override.yml
I added a
-ignore-installed
flagged to the pip3 installation command of the networkbuildercoordinator to ensure a consistent installation procedure across enviroments/infrastructures.removed the ports specified for the
profiler
service since they are obsolete in this service and conflict with theelasticsearch
serviceadded the command attribute for the
profiler
to hold the profiler arguments (since this is appended to theENTRYPOINT
on execution). This will allow to run the profiler by simply runningdocker-compose up profiler
and allows for easy override indocker-compose.override.yml