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 2020/12/17 09:49:37 UTC

[GitHub] [airflow-on-k8s-operator] sundar-cs opened a new issue #31: gcr.io image ImagePullBackOff

sundar-cs opened a new issue #31:
URL: https://github.com/apache/airflow-on-k8s-operator/issues/31


   Hi,
   
   While following the quickstart (or development.md) and deploying the CR, there's an ImagePullBackOff error (Back-off pulling image "gcr.io/airflow-operator/airflow:1.10.2") on an AWS KOPS cluster, with the operator running locally & also on the cluster.
   
   Just FYI there were a couple of other errors too prior to the above, such as:
   (1)
   RBAC related (Required value: resource rules must supply at least one api group) due to apiGroup not specified under Rules for Role and ClusterRole in the YAMLs.
   This was fixed by including the apiGroups under "rules" for these.
   (2)
   Object 'Kind' is missing (for all the YAMLs under template folder due to "---" at the start).
   This was fixed by deleting the line with "---".
   
   With above fixes it was able to proceed further and "make run" (operator running locally for instance) is fine and the mysql-celery base CR is also created successfully.
   But while trying to create the mysql-celery cluster CR, the pods fail with ImagePullBackOff.
   
   Also just a simple "docker pull gcr.io/airflow-operator/airflow:1.10.2" too results in:
   Error response from daemon: Get https://gcr.io/v2/airflow-operator/airflow/manifests/1.10.2: unknown: Project 'project:airflow-operator' not found or deleted.
   
   Trying latest version (i.e. without specifying 1.10.2) etc too fails.
   Has the image path (or version) changed ?
   
   Thanks.
   


----------------------------------------------------------------
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

[GitHub] [airflow-on-k8s-operator] sundar-cs commented on issue #31: gcr.io image ImagePullBackOff

Posted by GitBox <gi...@apache.org>.
sundar-cs commented on issue #31:
URL: https://github.com/apache/airflow-on-k8s-operator/issues/31#issuecomment-768154808


   No I have not ... Please keep me posted if you succeed in getting hold of GCR or other equivalent images for the operator.


----------------------------------------------------------------
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

[GitHub] [airflow-on-k8s-operator] etiennecl commented on issue #31: gcr.io image ImagePullBackOff

Posted by GitBox <gi...@apache.org>.
etiennecl commented on issue #31:
URL: https://github.com/apache/airflow-on-k8s-operator/issues/31#issuecomment-767935238


   Hi, @sundar-cs have you managed to find a suitable docker repository for the airflow image?


----------------------------------------------------------------
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

[GitHub] [airflow-on-k8s-operator] etiennecl commented on issue #31: gcr.io image ImagePullBackOff

Posted by GitBox <gi...@apache.org>.
etiennecl commented on issue #31:
URL: https://github.com/apache/airflow-on-k8s-operator/issues/31#issuecomment-768535996


   @barney-s I've been digging into the repository history and the old one which was maintained by Google. It seems as is they were once using your fork of https://github.com/puckel/docker-airflow. Would you happen to be able to guide us here?


----------------------------------------------------------------
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