You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/03/11 17:52:51 UTC

[GitHub] [airflow] pl77 edited a comment on issue #14266: Azure Provider related WARNING in webserver (version 2.0.1)

pl77 edited a comment on issue #14266:
URL: https://github.com/apache/airflow/issues/14266#issuecomment-796923376


   For those who might be looking for a simple way to implement these suggestions, I tried solutions from both @omarish and @potiuk and they both worked fine.  Easiest way to try them was create a blank text file named, as an example, `Dockerfile-karaknb` and inside place the commands:
   
   ```
   FROM apache/airflow:2.0.1
   RUN pip install apache-airflow-providers-microsoft-azure==1.2.0rc1
   ```
   
   Then, in the same directory you saved that file, run:
   
   ```bash
   docker build -f ./Dockerfile-potiuk -t apache/airflow:2.0.1 .
   ```
   
   If you save with the same tag as the existing file you don't have to change your `docker-compose.yml` files and when 2.0.2 is released it'll supersede this monkey patch when you do your regular `docker-compose pull` when upgrading (of course, that's if your image is specified as `:latest` in your compose file). 
   
   I'm sure everyone using airflow is advanced enough to know this already but figured I'd post it just in case someone was struggling.
   
   @potiuk :  the rc1 candidate seemed to install just fine but I didn't have an azure instance to test it against, unfortunately. 


----------------------------------------------------------------
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:
users@infra.apache.org