Rosalind's docker image is quite large at 2.4 GB in size. This results in occasional timeouts during deploy steps when trying to pull it from ecr, for example.
Solution
Optimize the docker image by utilizing the official slim docker image. Using the slim image cuts the size by ~400 mb, or, about 20%. This should be sufficient for limiting timeouts, as other images of this size don't see the same issue.
$ docker image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
rosalind_slim latest 9b9fa8dd1383 5 hours ago 1.93GB
rosalind latest 9e482fe25905 22 hours ago 2.4GB
Considerations
We've moved away from utilizing the shared artsy docker image in order to decouple the work sliming this image from another open question about how to address an edge case of google-chrome-stable not being compatible with arm architectures (ticket to track this issue to be created).
co-authored with: @ovasdi
Problem
Rosalind's docker image is quite large at
2.4 GBin size. This results in occasional timeouts during deploy steps when trying to pull it fromecr, for example.Solution
Optimize the docker image by utilizing the official
slimdocker image. Using the slim image cuts the size by~400 mb, or, about 20%. This should be sufficient for limiting timeouts, as other images of this size don't see the same issue.Considerations
We've moved away from utilizing the shared artsy docker image in order to decouple the work sliming this image from another open question about how to address an edge case of
google-chrome-stablenot being compatible witharmarchitectures (ticket to track this issue to be created).PHIRE-24