potiuk commented on issue #14211: URL: https://github.com/apache/airflow/issues/14211#issuecomment-778584810
> I am confused why I need this constraints file to install all these packages that we don't use in our production airflow instance. Maybe I should be starting with empty constraints? Or creating our own requirements.txt for packages we actually install in our prod airflow... Constraints are not requirements. They are simply hint to PIP. They basicaly mean "if you are installing this package, then use this version". No more no less. So it's good to have constraint with ALL possible packages. But then you install only what you need. > OK, got it working by referencing constraints file from path ./docker-context-files/constraints-2.7.txt which is accessible inside docker. Yeah. That was exactly supposed to be like this. > scripts/docker/install_airflow_from_latest_master.sh and scripts/docker/install_airflow.sh having different working path context and yet both try to use relative constraints path. I guess I'll have to modify the scripts for now. Would be great if you contribute those changes back :). happy to review them :) ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
