Replies: 4 comments
-
Thanks for opening your first issue here! Be sure to follow the issue template! |
Beta Was this translation helpful? Give feedback.
-
Try using the old version of Docker provider and if it works: https://airflow.apache.org/docs/apache-airflow-providers-docker/stable/index.html#id1
|
Beta Was this translation helpful? Give feedback.
-
Thanks @kaxil. I thus successfully installed apache-airflow-providers-docker-1.0.0 (that uninstalls version 1.0.1) while restoring docker version 3.7.3 (which is the version pinned by the CONSTRAINT_URL). Alas I still get the same error message
|
Beta Was this translation helpful? Give feedback.
-
While googling in despair, I discovered the existence of airflowdocker.io that seems loosely related with the official Apache development. Yet their approach seems to consider that "everything is a docker operator". |
Beta Was this translation helpful? Give feedback.
-
Apache Airflow version: 2.0.1
Kubernetes version : not used
Environment: docker engine 20.10.0 (provided by docker-desktop 3.0.1, installed with
brew cask install docker
and then accepting the docker-desktop GUI proposal to upgrade to 3.0.1).What happened:
After installing airflow 2.0.1 with Pypi, I tried to run the docker examples (as provided by the Airflow github repository) from the CLI. This failed (for me).
What you expected to happen:
Apparently the docker example dags seem to be failing because of an API mismatch between the version used in Airflow's docker-examples and the "contemporary" version of Docker Python wrappings.
In turn, could this be due (?) to:
airflow.providers.docker.operators.docker
?How to reproduce it:
Follow Airflow quick Pypi installation that boils down to:
To run the docker-examples, the airflow sources are required
Proceed with running de
docker_sample
where this last command will issue an error of the form
and further suggesting that
airflow/venv/lib/python3.8/site-packages/airflow/providers/docker/operators/docker.py
(line 314, in_get_cli
) is using a deprecated API (with docker version20.10.0
on OSX).If we now manually downgrade the version of the docker python wrapper package starting from 3.7.3 (which is the version pinned by the CONSTRAINT_URL that thus was installed by
pip
, refer above) down to 3.0.0 with e.g.then one consistently gets the same API version error message.
But starting with version 2.7.0 of the docker python wrappers then the connection to the docker daemon seems no longer possible (and should fail with message of the form
requests.exceptions.ConnectionError: HTTPConnectionPool [...]
).Install minikube/kind
The short answer is here: I barely ended up learning docker and I overheard that Kubernetes deployment/usage/fiddling is heavier. The goal was/is thus to only use docker (as opposed to Kubernetes) that should suffice when debugging dags on a desktop.
Anything else we need to know:
Nope. Seems about it.
Beta Was this translation helpful? Give feedback.
All reactions