You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "jhgoebbert (via GitHub)" <gi...@apache.org> on 2025/10/10 13:23:49 UTC
[I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
jhgoebbert opened a new issue, #56545:
URL: https://github.com/apache/airflow/issues/56545
### Apache Airflow version
3.1.0
### If "Other Airflow 2/3 version" selected, which one?
_No response_
### What happened?
The `@task.kubernetes` decorator fails when used with non-root container images such as the official `apache/airflow` image.
After [PR #28942](https://github.com/apache/airflow/pull/28942), the initialization phase for Kubernetes-decorated tasks creates the directory `/airflow/xcom` (see [providers/cncf/kubernetes/decorators/kubernetes.py#L98](https://github.com/apache/airflow/blob/54bd5d8cd9f6f477cc83445737614dec81c4323c/providers/cncf/kubernetes/src/airflow/providers/cncf/kubernetes/decorators/kubernetes.py#L98)).
However, in the default Airflow image the container runs as the **`airflow` user**, (see [HERE](https://github.com/apache/airflow/blob/54bd5d8cd9f6f477cc83445737614dec81c4323c/Dockerfile#L2058)) which does not have write permissions to `/`. As a result, the attempt to create `/airflow/xcom` fails with a permissions error, and the Kubernetes task cannot start.
### What you think should happen instead?
The Kubernetes-decorated task should run successfully, even when the image runs as a non-root user.
### How to reproduce
1. Use the official Apache Airflow 3 image, e.g.:
```yaml
image: apache/airflow:3.1.0
```
2. Define a DAG:
```
from airflow.decorators import dag, task
from datetime import datetime
@dag(start_date=datetime(2024, 1, 1), schedule=None)
def test_dag():
@task.kubernetes(image="apache/airflow:3.1.0")
def example_task():
print("Hello from Airflow task")
example_task()
test_dag()
```
3. Trigger the DAG.
### Operating System
Kubernetes (Airflow charts)
### Versions of Apache Airflow Providers
Latest
### Deployment
Official Apache Airflow Helm Chart
### Deployment details
Airflow version: 3.1.0
Executor: @task.kubernetes)
Base image: apache/airflow:3.1.0
Kubernetes version: (v1.32)
### Anything else?
The /airflow/xcom directory is currently created unconditionally during initialization, assuming root permissions.
Possible approaches to resolve this:
- Create the directory under a writable path such as /tmp/airflow/xcom, or
- Make the XCom path configurable for Kubernetes-decorated tasks, or
- Check for existence and create the directory only if it’s writable by the current user.
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "jhgoebbert (via GitHub)" <gi...@apache.org>.
jhgoebbert commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3476457729
Hi @Prab-27 , are you planing to work on this? I am just asking because github-actions just marked it as stale.
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "hussein-awala (via GitHub)" <gi...@apache.org>.
hussein-awala commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3393231911
In fact, it’s recommended to use rootless mode, which means this is a bug.
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "Prab-27 (via GitHub)" <gi...@apache.org>.
Prab-27 commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3476473567
@jhgoebbert ,Yes, I just started working on it today. Sorry for the delay!
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "nailo2c (via GitHub)" <gi...@apache.org>.
nailo2c commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3644755421
Hi, my team encountered this issue as well. Since we needed a fix, I've submitted a PR #59347 to address it. Hope this helps!
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "hussein-awala (via GitHub)" <gi...@apache.org>.
hussein-awala commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3403692600
> An easy solution to that is to have "/airflow/xcom" pre-created and owned by airflow:0 in the Airflow PROD image
I think this should be fixed in the provider rather than in the Docker image. For example, we could change the XCom path to one owned by the user `airflow`, or mount an `emptyDir` volume to that path to ensure the folder is created.
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "Prab-27 (via GitHub)" <gi...@apache.org>.
Prab-27 commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3607472905
Still in progress ...
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3407344167
Ah. OK. I think the problem is that in this case "do_xcom_push" was set to False. This will not create sidecar container (`add_xcom_sidecar`) will not run - I guess an easy way to do it is to skip all the mkdir and xcom writing when do_xcom_push is set to False.
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "jhgoebbert (via GitHub)" <gi...@apache.org>.
jhgoebbert commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3393224087
Could it be that it is intended that non-root images have no support?
I might miss something here - but I do not see a reason why 🤔
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk closed issue #56545: `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation
URL: https://github.com/apache/airflow/issues/56545
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "jhgoebbert (via GitHub)" <gi...@apache.org>.
jhgoebbert commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3393222949
You can see from the tests of the kubernetes provider that only images with an entrypoint as root are used:
- ubuntu:16.04
- alpine
- bash:5.2
- perl:5.34.0
- gcr.io/spark-operator/spark:v2.4.4
So the integration tests cannot show this issue.
-------
I have added the links for each image to its layer-details to show the root-style of the image
and the link to the tests where it is used in the kubernetes-provider below.
[image="ubuntu:16.04"](https://hub.docker.com/layers/library/ubuntu/16.04/images/sha256-a3785f78ab8547ae2710c89e627783cfa7ee7824d3468cae6835c9f4eae23ff7?context=explore)
- [example_kubernetes.py#L62](https://github.com/apache/airflow/blob/main/providers/cncf/kubernetes/tests/system/cncf/kubernetes/example_kubernetes.py#L62)
- [example_kubernetes.py#L114](https://github.com/apache/airflow/blob/main/providers/cncf/kubernetes/tests/system/cncf/kubernetes/example_kubernetes.py#L114)
- [example_kubernetes_async.py#L62](https://github.com/apache/airflow/blob/main/providers/cncf/kubernetes/tests/system/cncf/kubernetes/example_kubernetes_async.py#L62)
- [example_kubernetes_async.py#L115](https://github.com/apache/airflow/blob/main/providers/cncf/kubernetes/tests/system/cncf/kubernetes/example_kubernetes_async.py#L115)
- [example_kubernetes_async.py#L140](https://github.com/apache/airflow/blob/main/providers/cncf/kubernetes/tests/system/cncf/kubernetes/example_kubernetes_async.py#L140)
[image="alpine"](https://hub.docker.com/layers/library/alpine/latest/images/sha256-9eec16c5eada75150a82666ba0ad6df76b164a6f8582ba5cb964c0813fa56625)
- [example_kubernetes.py#L152](https://github.com/apache/airflow/blob/main/providers/cncf/kubernetes/tests/system/cncf/kubernetes/example_kubernetes.py#L152)
- [example_kubernetes_async.py#L183](https://github.com/apache/airflow/blob/main/providers/cncf/kubernetes/tests/system/cncf/kubernetes/example_kubernetes_async.py#L183)
[image="bash:5.2"](https://hub.docker.com/layers/library/bash/5.2/images/sha256-da1b3b5c01eb25c82c32cc13303814331aed3105b135456038d6b42017329b50)
- [example_kubernetes_cmd_decorator.py#L41](https://github.com/apache/airflow/blob/main/providers/cncf/kubernetes/tests/system/cncf/kubernetes/example_kubernetes_cmd_decorator.py#L41)
[image="perl:5.34.0"](https://hub.docker.com/layers/library/perl/5.34.0/images/sha256-cc24449e3f32565f971bb9067141faa4f504562b04919597219170044253bfe3)
- [example_kubernetes_job.py#L50C9-L50C28](https://github.com/apache/airflow/blob/main/providers/cncf/kubernetes/tests/system/cncf/kubernetes/example_kubernetes_job.py#L50C9-L50C28)
- [example_kubernetes_job.py#L69](https://github.com/apache/airflow/blob/main/providers/cncf/kubernetes/tests/system/cncf/kubernetes/example_kubernetes_job.py#L69)
- [example_kubernetes_kueue.py#L118](https://github.com/apache/airflow/blob/main/providers/cncf/kubernetes/tests/system/cncf/kubernetes/example_kubernetes_kueue.py#L118)
[image: "gcr.io/spark-operator/spark:v2.4.4"](https://github.com/apache/spark/blob/branch-2.4/resource-managers/kubernetes/docker/src/main/dockerfiles/spark/bindings/python/Dockerfile)
- [example_spark_kubernetes_spark_pi.yaml#L27](https://github.com/apache/airflow/blob/main/providers/cncf/kubernetes/tests/system/cncf/kubernetes/example_spark_kubernetes_spark_pi.yaml#L27)
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "hussein-awala (via GitHub)" <gi...@apache.org>.
hussein-awala commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3393170021
The change you mention was released in `5.2.1` more than 2 years and half ago, I'm surprised no one faced/reported the issue before. This would make sense if we have the folder `/airflow` created in the Docker image and we removed it recently, but according the blame history, it is not the case:
```log
git blame Dockerfile | grep "/airflow"
07fd0d71c8f (Jarek Potiuk 2020-04-02 19:52:11 +0200 43) ARG AIRFLOW_HOME=/opt/airflow
3feb057f0ee (Jarek Potiuk 2022-01-08 20:41:29 +0100 46) ARG AIRFLOW_USER_HOME_DIR=/home/airflow
94b03f6f432 (Jarek Potiuk 2021-08-04 23:32:12 +0200 62) ARG AIRFLOW_IMAGE_REPOSITORY="https://github.com/apache/airflow"
7f02b4718bc (Kamil Breguła 2022-01-23 14:15:45 +0100 63) ARG AIRFLOW_IMAGE_README_URL="https://raw.githubusercontent.com/apache/airflow/main/docs/docker-stack/README.md"
a1717a652b3 (Jarek Potiuk 2024-03-06 01:27:15 +0100 70) # SOURCES_FROM/TO with "." and "/opt/airflow" respectively - so that sources of Airflow (and all providers)
14b00ed5e2c (Josef Šimánek 2025-06-22 11:57:12 +0200 892) echo "${COLOR_YELLOW}See: https://airflow.apache.org/docs/docker-stack/build.html#adding-new-pypi-packages-individually${COLOR_RESET}"
d4473555c0e (Jarek Potiuk 2025-04-02 13:11:13 +0200 1116) --editable ./airflow-core --editable ./task-sdk --editable ./airflow-ctl \
09544966741 (GPK 2025-09-11 20:37:02 +0100 1119) --editable ./airflow-e2e-tests \
9cbab95fd29 (Jarek Potiuk 2022-03-27 19:19:02 +0200 1474) # HOME directory to the /home/airflow so that (for example) the ${HOME}/.local folder where airflow is
14b00ed5e2c (Josef Šimánek 2025-06-22 11:57:12 +0200 1544) >&2 echo " https://airflow.apache.org/docs/docker-stack/entrypoint.html"
14b00ed5e2c (Josef Šimánek 2025-06-22 11:57:12 +0200 1558) >&2 echo " https://airflow.apache.org/docs/docker-stack/entrypoint.html"
9cbab95fd29 (Jarek Potiuk 2022-03-27 19:19:02 +0200 1601) >&2 echo " https://airflow.apache.org/docs/docker-stack/build.html"
9cbab95fd29 (Jarek Potiuk 2022-03-27 19:19:02 +0200 1638) readonly DIRECTORY="${AIRFLOW_HOME:-/usr/local/airflow}"
9cbab95fd29 (Jarek Potiuk 2022-03-27 19:19:02 +0200 1663) # The content below is automatically copied from scripts/docker/airflow-scheduler-autorestart.sh
25b62a72f44 (Jarek Potiuk 2022-03-31 13:39:46 +0200 1664) COPY <<"EOF" /airflow-scheduler-autorestart.sh
9cbab95fd29 (Jarek Potiuk 2022-03-27 19:19:02 +0200 1672) date >> /tmp/airflow_scheduler_errors.txt
7c12a9d4e0b (Jarek Potiuk 2020-06-16 12:36:46 +0200 1756) ARG AIRFLOW_REPO=apache/airflow
d524cec99db (Jarek Potiuk 2021-02-21 18:56:55 +0100 1761) ARG CONSTRAINTS_GITHUB_REPOSITORY="apache/airflow"
acff1296886 (Jarek Potiuk 2022-07-20 19:30:03 +0200 1778) # set to "." and "/opt/airflow" respectively.
8e3d1fcff6c (Jarek Potiuk 2022-03-29 15:03:50 +0200 2015) COPY --from=scripts airflow-scheduler-autorestart.sh /airflow-scheduler-autorestart
cf510a30fb4 (Jarek Potiuk 2020-06-27 14:29:55 +0200 2018) # See https://github.com/apache/airflow/issues/9248
4620770af45 (Jarek Potiuk 2022-01-11 10:38:34 +0100 2037) # See https://airflow.apache.org/docs/docker-stack/entrypoint.html#signal-propagation
2c6c7fdb230 (Jarek Potiuk 2021-01-21 16:16:09 +0100 2082) org.opencontainers.image.url="https://airflow.apache.org" \
94b03f6f432 (Jarek Potiuk 2021-08-04 23:32:12 +0200 2083) org.opencontainers.image.documentation="https://airflow.apache.org/docs/docker-stack/index.html" \
```
Could you try reproduce the issue in the K8S integration tests? That way we can figure out where and how we should fix it.
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "jhgoebbert (via GitHub)" <gi...@apache.org>.
jhgoebbert commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3414264901
> I guess an easy way to do it is to skip all the mkdir and xcom writing when do_xcom_push is set to False.
Yes, that would solve it. If we add `do_xcom_push=True` the task runs.
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3401731313
Feel free.
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3407319039
> > An easy solution to that is to have "/airflow/xcom" pre-created and owned by airflow:0 in the Airflow PROD image
>
> I think this should be fixed in the provider rather than in the Docker image. For example, we could change the XCom path to one owned by the user `airflow`, or mount an `emptyDir` volume to that path to ensure the folder is created.
Actually - that's a good point .
I looked a bit closer and from what I see - xcom should be already mounted from empty volume and shared between the pod and it's sidecar:
```python
class PodDefaults:
"""Static defaults for Pods."""
XCOM_MOUNT_PATH = "/airflow/xcom"
SIDECAR_CONTAINER_NAME = "airflow-xcom-sidecar"
XCOM_CMD = 'trap "exit 0" INT; while true; do sleep 1; done;'
VOLUME_MOUNT = k8s.V1VolumeMount(name="xcom", mount_path=XCOM_MOUNT_PATH)
VOLUME = k8s.V1Volume(name="xcom", empty_dir=k8s.V1EmptyDirVolumeSource())
SIDECAR_CONTAINER = k8s.V1Container(
name=SIDECAR_CONTAINER_NAME,
command=["sh", "-c", XCOM_CMD],
image="alpine",
volume_mounts=[VOLUME_MOUNT],
resources=k8s.V1ResourceRequirements(
requests={
"cpu": "1m",
"memory": "10Mi",
},
),
)
```
So I am actually surprised it fails for you @jhgoebbert
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "Prab-27 (via GitHub)" <gi...@apache.org>.
Prab-27 commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3399522502
@potiuk I'd like to work on this
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3399310064
An easy solution to that is to have "/airflow/xcom" pre-created and owned by `airflow:0` in the Airflow PROD image. Feel free to make such change to the Dockerfile. Also feel fre @jhgoebbert to make a PR adding it, otherwise it will wait for someone who will volunteer.
BTW., You can also run airflow image as root as workaround and then it will work (this is supported in the current image - you can run it with any user id as long as group id = 0.
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "nailo2c (via GitHub)" <gi...@apache.org>.
nailo2c commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3644978042
Hi @Prab-27, please don't apologize! K8s has a steep learning curve and we are all learning here. Taking on an issue is a brave first step, and it is definitely not a mistake. Keep exploring and happy coding! 💪
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3649549732
> Hi @Prab-27, please don't apologize! K8s has a steep learning curve and we are all learning here. Taking on an issue is a brave first step, and it is definitely not a mistake. Keep exploring and happy coding! 💪
Very much so !
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "hussein-awala (via GitHub)" <gi...@apache.org>.
hussein-awala commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3393179375
> Make the XCom path configurable for Kubernetes-decorated tasks, or
This should be the fastest and easiest solution to implement (it's full b/c), feel free to open a PR.
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3537160830
This issue has been automatically marked as stale because it has been open for 14 days with no response from the author. It will be closed in next 7 days if no further activity occurs from the issue author.
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "Prab-27 (via GitHub)" <gi...@apache.org>.
Prab-27 commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3537177787
Apologies for the delay. I was busy, but I assure you I’ll raise the PR today
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "Prab-27 (via GitHub)" <gi...@apache.org>.
Prab-27 commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3644908432
Sorry, I’m still testing with Kubernetes and learning about it, so I couldn’t fix this PR.
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "jhgoebbert (via GitHub)" <gi...@apache.org>.
jhgoebbert commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3397009780
@hussein-awala Is there any additional information I can give or can you remove the `pending-response` tag?
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `@task.kubernetes` fails on non-root images due to `/airflow/xcom` directory creation [airflow]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3475284521
This issue has been automatically marked as stale because it has been open for 14 days with no response from the author. It will be closed in next 7 days if no further activity occurs from the issue author.
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org