Reduce Docker image size

[mfitz]

Before

REPOSITORY               TAG        IMAGE ID       CREATED             SIZE
genet-local-master       latest     3e95afde36e9   30 seconds ago      1.75GB

After

REPOSITORY            TAG        IMAGE ID       CREATED             SIZE
genet-local           latest     61c9395a63bf   26 minutes ago      1.46GB

Still pretty chonky, even after reclaiming 300 megs. Questions @KasiaKoz:

• Do we still need that Node installation? I think it was for something to do with Kepler, right?
• notebooks/7. Visualising Network.ipynb is over 40 MB in size - is that expected? Seems outrageously big for a notebook.

Validating the image

I connected to the container and ran both the unit tests and the notebook smoke tests. The smoke tests all passed, but one unit test failed. However, when I ran the unit tests in the container created from the image in master, I saw the same failure, so this does not seem to have been caused by my changes.

[KasiaKoz]

Awesome, thanks for de-chonkifying genet, doing Gods work here @mfitz

We do still need node, kepler is still a functionality.. and you can generate and save those plots to html so it's possible someone would use that via docker.

Now onto the failing test in docker. Wawaweewa 👀 It looks like the snap and route functionality / maybe the max stable set optimisation gives different results inside---but why and what are the consequences 👀 a bit worried tbh. Should be investigated and I feel like we should have some automatic testing within docker... we do use genet within docker frequently 😰

[mfitz]

Awesome, thanks for de-chonkifying genet, doing Gods work here @mfitz

We do still need node, kepler is still a functionality.. and you can generate and save those plots to html so it's possible someone would use that via docker.

Now onto the failing test in docker. Wawaweewa 👀 It looks like the snap and route functionality / maybe the max stable set optimisation gives different results inside---but why and what are the consequences 👀 a bit worried tbh. Should be investigated and I feel like we should have some automatic testing within docker... we do use genet within docker frequently 😰

We can add testing inside the container to the CodeBuild pipeline, we have a mechanism to do that by just adding a run-tests.sh to the root of the project - see here. This will fail the build right now though, so we should figure out what is going wrong with that test first.