rcampos87 commented on issue #57431:
URL: https://github.com/apache/airflow/issues/57431#issuecomment-3457396550
@AntoineAugusti We have been using a custom airflow image:
```
FROM apache/airflow:slim-3.1.1-python3.10
USER root
WORKDIR /opt/airflow
RUN apt-get update && apt-get install -y --no-install-recommends git
build-essential \
gcc python3-dev pkg-config default-libmysqlclient-dev
COPY --from=ghcr.io/astral-sh/uv:0.9.5 /uv /uvx /bin/
COPY requirements.txt .
RUN uv pip install --no-cache-dir -r requirements.txt
USER airflow
```
requirements.txt:
```
apache-airflow==3.1.1
apache-airflow-core==3.1.1
apache-airflow-providers-amazon==9.16.0
apache-airflow-providers-celery==3.13.0
apache-airflow-providers-cncf-kubernetes==10.8.0
apache-airflow-providers-common-compat==1.8.0
apache-airflow-providers-redis==4.3.1
apache-airflow-providers-fab==2.4.3
apache-airflow-providers-git==0.0.8
apache-airflow-providers-standard==1.9.1
kubernetes==32.0.1
aiohttp==3.9.5
aiohttp-cors==0.8.1
aiohttp-retry==2.9.1
aioitertools==0.12.0
aiomysql==0.2.0
```
When I first opened the ticket, I did not have
```
apache-airflow==3.1.1
apache-airflow-core==3.1.1
```
set. So, upon inspecting one of the pods and doing `pip freeze`, i noticed
that apache-airflow 3.1.0 was still installed. Then when I pinned it and
rebuilt the image, it began working.
In the webserver, I have the s3 connection `s3Minio` already setup. I have
tested this image both with Minio and AWS S3.
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
