I am on a Windows 10 machine, have pulled the image down and clone the repo. In the repo folder I run docker build --build-arg AIRFLOW_DEPS="gcp_api,google_auth,slack" -t puckel/docker-airflow . and then in docker-compose-LocalExecutor.yml I change the image name to puckel/docker-airflow:latest and run docker-compose -f docker-compose-LocalExecutor.yml up and there seem to be two problems.
-
I get the following error: env: bash\r: No such file or directory, which seems to be related to running this on Windows. I can resolve this by doing dos2unix entrypoint.sh when in the ./script folder, and then rebuilding the image.
-
After resolving that issue, when I start the container, I get the following error:
ModuleNotFoundError: No module named 'werkzeug.wrappers.json'; 'werkzeug.wrappers' is not a package
When the image builds I see the following errors, which points to package version conflicts:
ERROR: flask 1.1.0 has requirement Jinja2>=2.10.1, but you'll have jinja2 2.10 which is incompatible.
ERROR: flask 1.1.0 has requirement Werkzeug>=0.15, but you'll have werkzeug 0.14.1 which is incompatible.
ERROR: google-cloud-bigquery 1.16.0 has requirement google-cloud-core<2.0dev,>=1.0.0, but you'll have google-cloud-core 0.28.1 which is incompatible.
ERROR: google-cloud-spanner 1.9.0 has requirement google-cloud-core<2.0dev,>=1.0.0, but you'll have google-cloud-core 0.28.1 which is incompatible.
ERROR: google-cloud-translate 1.5.0 has requirement google-cloud-core<2.0dev,>=1.0.0, but you'll have google-cloud-core 0.28.1 which is incompatible.
But I have not been able to figure out how to resolve this.
I am on a Windows 10 machine, have pulled the image down and clone the repo. In the repo folder I run
docker build --build-arg AIRFLOW_DEPS="gcp_api,google_auth,slack" -t puckel/docker-airflow .and then indocker-compose-LocalExecutor.ymlI change the image name topuckel/docker-airflow:latestand rundocker-compose -f docker-compose-LocalExecutor.yml upand there seem to be two problems.I get the following error:
env: bash\r: No such file or directory, which seems to be related to running this on Windows. I can resolve this by doingdos2unix entrypoint.shwhen in the./scriptfolder, and then rebuilding the image.After resolving that issue, when I start the container, I get the following error:
ModuleNotFoundError: No module named 'werkzeug.wrappers.json'; 'werkzeug.wrappers' is not a packageWhen the image builds I see the following errors, which points to package version conflicts:
But I have not been able to figure out how to resolve this.