Parallel builds failing due to conflicting Jaeger port allocations

[rbreslow]

We should consider migrating port bindings from docker-compose.yml to a new docker-compose.override.yml file so that we do not allocate a port in CI, or consider removing the dependency between the API service and Jaeger.

See: http://jenkins.staging.rasterfoundry.com/job/Granary/job/granary/job/master/1/console

[jisantuc]

Similarly, postgres ports conflict. Overrides seems great.

[rbreslow]

@jisantuc If this is something you want to take on your own (because it's pretty easy) https://github.com/azavea/fieldscope/blob/develop/docker-compose.override.yml is a pretty good model. Then you can just remove the port bindings from the regular docker-compose.yml file.

Otherwise, we can register it on our radar again.

[jisantuc]

I think I can handle it on my own at some point but I don't know the next time I'll be in Granary. I don't think it's urgent. You can keep it off your radar.

[jisantuc]

We play a similar game with https://github.com/raster-foundry/raster-foundry/blob/develop/docker-compose.dev.yml