Rethink docker-compose container dependencies

[reubano]

Overview

As a follow-up to #199, we may need to re-evaluate the container structure. Currently, all services benefit from the caching, but only the docs service benefits from the added python requirements. Both the interface and prediction services wind up bloated with extra requirements they don't need.

Expected Behavior

The docs service should use caches provided by the interface and prediction services. However, neither the interface nor prediction services should have unnecessary python requirements.

Technical details

• Make the docker-compose documentation service reuse the caches from prediction and interface #159
• #159 Docker: Reuse Caches #199

Acceptance criteria

• when running docker-compose -f local.yml build on a clean system, the python requirements files should not be downloaded by documentation service.
• when running docker-compose -f local.yml build on a clean system, the documentation service should use the caches provided by the prediction and interface services.
• when running docker-compose -f local.yml build on a clean system, the prediction service should not install unnecessary interface python requirements such as Django.
• when running docker-compose -f local.yml build on a clean system, the interface service should not install unnecessary prediction python requirements such as pytorch.

NOTE: All PRs must follow the standard PR checklist.

[WGierke]

I guess the docs service should still use the cache that was built by the interface service (instead of re-downloading all the Python dependencies)? Do you have any ideas how to accomplish that?

[reubano]

@WGierke so after thinking about this some more, we may need to re-evaluate the entire structure. Currently, all services benefit from the caching, but only the docs service benefits from the added python requirements. Both the interface and prediction services wind up bloated with extra requirements they don't need.

And I'm not sure if it's possible to satisfy both optimizations at once.

[isms]

@reubano Is there something specific we can change this issue to? As currently posed it seems overly broad and not actionable.

[reubano]

@isms still thinking this over... is there anything in particular that is too broad/not well explained? cc @pjbull