potiuk commented on issue #17320:
URL: https://github.com/apache/airflow/issues/17320#issuecomment-1567827777
This is your problem to solve. I am not reading all the details, but if you
wish to continue this dicussion, then pleas opem a new one - you are
piggybacking on someone's different error and different case. You are hijacking
this closed issue for somewhat related but different issue.
And please do not add even more issues. You seem to have an issue with
designing a company wide solution based on docker-compose that is quite a bit
of beyond of "why the quick-start docker compose does not work as advertised".
You seem to need a professional paid help on solving the problems if you won't
be able to design it on your own.
I am not goiing to have time (in my free time) to solve the problem you have
and design a solution that will work for your company and team but can tell you
some assumptions of the image we have and point you to the right docs you can
read to understand thoroughly what's going on so that you can solve it - and
if you want to map into company wide solution for you, you need to map it to
those assumptions as you see fit.
If you are trying to use the docker compose ("quick start") of ours to be
able to do your "company wide" deployment you are mostly on your own to make it
works well for your case (this is how docker-compose works) and you shoudl
modify it to fit your needs. Our quick-start docker-compose is just a starting
point and reference for someone to write their own (if they wish) and (as
indicated in the docker-compose) it has plenthy of things that you will likely
have to modify and design your own docker-compose that you need to do to make
it works.
I think (but I will have no time to dive-deep into your solution - we are
all here helping in our free time, so I can give at most some generic advice.
The image of airlfow works with the assumption that either you have
"airflow" owned files and folders or "0" group owned ones (this is for
open-shift compatibility). See all the details about it in the docs:
https://airflow.apache.org/docs/docker-stack/entrypoint.html . What you
happanes when you use different uid the entrypoint (and it is all described in
the docs) creates a new user, makes it belongs to "0" group and sets it home to
same as "airflow" user. And all the files and folders etc should be owned and
created by the "0" group and read/write works for them to make it works. So if
you wish to do it and share files and folders somehow you need make sure "0"
group owns it. If you are using "airflow" user by default, you should just make
sure that your volumes are read/write for "airflow" users.
How to do it exactly if you build some kind of sharing and git based on the
docker compose is primarily your job to figure out, depends what you want to
do. I have no ready-recipes here I am afrais.
--
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]
