-
Notifications
You must be signed in to change notification settings - Fork 13.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running Airflow in Docker - Tutorial dags backfill tutorial example fails with TypeError: cannot serialize '_io.TextIOWrapper' object #14379
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
I updated the docker-compose.yaml default airflow image which fixed the problem. - image: ${AIRFLOW_IMAGE_NAME:-apache/airflow:2.0.1}
+ image: ${AIRFLOW_IMAGE_NAME:-apache/airflow:master-python3.8} Output above shows container was running python3.6. The comments in the docker-compose.yaml state the default should be Created pull request for v2-0-stable. Changes are consistent with master branch. |
Master and v2-0-stable are fair bit different in terms of the actual code. And users shouldn't be using images from Master in their Prod clusters |
Thanks for the response I wasn't aware there was a large difference. I can confirm that the image |
Awesome, glad that it worked :) |
+1 I am having this problem. Glad to see a solution here. |
+1 Ran into the same issue when doing the tutorial using the docker install. Updated docker-compose and added |
So just to double-check - you were also running on Windows 10 and apache/airflow:2.1.2 caused the same problem @etadelta222? |
Hello, Apologizes in advance if this is a newbie mistake. I'm working through the tutorial using Docker Desktop for Mac locally using the docker-compose from the Running Airflow in Docker. I'm copying the tutorial code as is as except for replacing
airflow
with./airflow.sh
to run in docker. All the commands work as expected except for the backfill example, which fails withTypeError: cannot serialize '_io.TextIOWrapper' object
. Please advise.The text was updated successfully, but these errors were encountered: