To stop the user from breaking the Python environment accidentally if they install packages directly via pip, we would like to completely control the installation of the packages and limit what the user can do to providing a requirements.txt. So, in our entrypoint, after successfully installing the customer requirements, we want to disable or, even better, remove pip somehow so the user cannot use it anymore, e.g. in DAGS.
Acceptance Criteria
Disable/remove pip after successfully installing customer requirements.
This should happen after the custom start up script (for customers who provide a custom start up script.)
Overview
To stop the user from breaking the Python environment accidentally if they install packages directly via pip, we would like to completely control the installation of the packages and limit what the user can do to providing a requirements.txt. So, in our entrypoint, after successfully installing the customer requirements, we want to disable or, even better, remove
pipsomehow so the user cannot use it anymore, e.g. in DAGS.Acceptance Criteria
pipafter successfully installing customer requirements.