To include the OpenJDK & Teradata driver into the final docker image, we need to add some steps into the Dockerfile. airflow[crypto,celery,postgres,hive,jdbc. The existing Dockerfile already includes a step for jdbc airflow hooks, so you’ll see something similar to the below in the file. In my case, that location is C:\docker-airflow. The latest driver at this point in time is 16.20.00.13 and can be downloaded from here.ĭownload the zip file and extract it to the root location of your cloned repo. Resolving deltas: 100% (420/420), done.īefore we can start the build of the docker image with support for Teradata/JBDC connectivity, we’ll need to make some changes to the existing Dockerfile and download the Teradata JDBC driver. My focus for now is to get up and running so an airflow instance using LocalExecutor mode will suffice.įirst step is to clone the git repo (latest version as of now is: ) using: PS C:\> git clone Cloning into 'docker-airflow'. To get a base airflow docker running, I went back to the puckel/docker-airflow repo and sure enough, it’s still there.Īirflow can be run in a couple of different modes with some allowing for architecture/system scaling. This post describes my recent experiment to get it (mostly) working. I didn’t get a chance at the time to get the environment working with the Teradata JDBC driver but some things are better late than never. ![]() At the time, I leveraged off an existing airflow Dockerfile, which I came across in github. ![]() I knew nothing back then about docker and airflow but eventually it all ran well. It’s been well over a year since I did a proof-of-concept for getting airflow up and running in docker. Getting these 3 muppets to communicate was a bit of challenge.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |