MingTaLee commented on issue #17320:
URL: https://github.com/apache/airflow/issues/17320#issuecomment-1566701211
I got similar issue with @ImadYIdrissi .
I'm setting up an Airflow develop / test environment with the Airflow 2.5.3
docker image and docker-compose.yaml file from Apache Airflow official website.
The server startng / running the docker-compose is an AWS EC2 server running
Ubuntu 20.04.6 LTS.
The user to run docker-compose up airflow-init and docker-compose up has ID
1002, and dags / logs / plugins are owned by that user in the host side.
(I did not use SUDO when running the docker-compose command)
Already set AIRFLOW_UID=1002 in .env file.
Checking inside airflow-airlfow-worker-1 container after the containers
initiated and ready, I can see 3 users:
root / airflow / default
User "airflow" has UID 50000 and User "default" has UID 1002, but it is a
nologin user and its home is set as user airflow (/home/airflow).
If I change the line [ user: "${AIRFLOW_UID:-50000}:0" ] to [ user:
"${AIRFLOW_UID:-1002}:0" ] in docker-compose.yaml, there will no user account
name "default", however, inside the containers, the account "airflow" still use
ID 50000 and dags / logs / plugins still have owner as 1002:root.
I have scraped the containers and restart with docker-compose down / up
several times, with different settings and none gave me proper ownership of the
volume bind paths (i.e. dags/ logs / plugins).
Is there any other settings that I missed?
Any input is appreciated! 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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
