airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhi Lin (JIRA)" <>
Subject [jira] [Created] (AIRFLOW-3214) [Kubernetes] No logs, hard to debug
Date Tue, 16 Oct 2018 03:27:00 GMT
Zhi Lin created AIRFLOW-3214:

             Summary: [Kubernetes] No logs, hard to debug
                 Key: AIRFLOW-3214
             Project: Apache Airflow
          Issue Type: Bug
          Components: kubernetes
    Affects Versions: 1.10.0
            Reporter: Zhi Lin

I have a fresh install of airflow on Kubernetes, basically running scripts in scripts/ci/kubernetes,
and I fix the flask-appbuilder version so the webserver is running fine. 

But when I try to run the example-kubernetes-executor dag, it fails and shows nothing useful
in the log. Then I try to pull the image airflow/ci manually, and also fails. It says no such
image or login is needed. I try to change the image in the dag to something I already have
locally, but it still fails and this time no log...

And I wonder if I want to use KubernetesPodOperator, I cannot run airflow in a k8s pod?
Because it tries to find the config files of k8s...

So what should I do? What I want to do is to run some machine learning task in a image specified.
Sometimes I need to run a python script in that spawned pod, so I guess I need to put that
file in the dag folder? Any suggestion appreciated.

This message was sent by Atlassian JIRA

View raw message