You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current AIP docker image is 1.92GB, which begs the question 'is all of this needed?'.
A big component on this docker size can be related to the use of Conda to manage the dependencies and requirements.
The task would be to investigate if this is the case, also if it's possible to not use conda and use virtual environments instead and how much would the size reduction would be.
All in all, the key question is: is this change worth it?
The text was updated successfully, but these errors were encountered:
A complementary approach would be to use multi-stage builds. This would allow to have a base image that can be use for development and a reduced smaller size build with only the required packages for production.
Ongoing tests show that a multi-stage build is what works best, using python-vevn instead of Conda, and removing unwanted requirements. Final size shrinks from 1.92GB to 371M.
The current AIP docker image is 1.92GB, which begs the question 'is all of this needed?'.
A big component on this docker size can be related to the use of Conda to manage the dependencies and requirements.
The task would be to investigate if this is the case, also if it's possible to not use conda and use virtual environments instead and how much would the size reduction would be.
All in all, the key question is: is this change worth it?
The text was updated successfully, but these errors were encountered: