potiuk edited a comment on issue #17320:
URL: https://github.com/apache/airflow/issues/17320#issuecomment-889886049
The reason it was closed, because you indicated that you expect that things
will work out-of-the-box even when you indicated yourself you tried to change
users (first 50000 and then 1001) and that it has changed since previous time,
which indicated that you expected more from the docker compose than what it is
intended to.
The "quick start" is really to get you quick-started and if you want to
change anything (like change the user and experiment with the setting), there
is not much we can do to "solve" the issue you raised as bug. From your message
it seems that you had a history of using this setup and that you "expect" it to
work under this different circumstances (one of the problems was that you used
sudo to run the docker compose which is guaranteed not to work).
You also indicated "If I have to create and use a single UID=50000 that will
handle all airflow operations, then my airflow file system within the host
cannot be operated properly with different users, e.g. devs when pulling new
changes from git..." which means that you wanted to make the docker compose
works for many users, but this is definitely not the intention of our docker
compose. It is there to make single user to be able to quick-start and run
airflow on that user's machine. That's it. There are other ways to make airflow
works for multiple users for development environment, but the quick start
docker compose is not one of them. That was the "production" use i was
referring to, which was indeed a bit to narrow, "multi-user" would be more
appropriate. It's not designed to be used by "multiple users". So it is not a
bug that it does not work this way.
The Quick-start documentation is just that - quick-start. No more, no less.
You have to strictly follow it to get it working, if you do any deviation from
that, it might or might not work. When you open an issue indicating "bug" I
think you expect it to be fixed. There is no action anyone can take here to
"fix" the problems you were experiencing. That's why the issue was closed -
because there is no reasonable action anyone can take here to fix the problems
you experienced.
The best thing You can do is to wipe out all your setup and start from
scratch and precisely follow the quick-start with no deviations and see if it
works. If it does not, please report it here with all information that you can
and I will be happy to reopen the issue (if it willl indicate that our quick
start instructions are wrong. Or even better - open a PR fixing it straight
away.
If you want to discuss the usage and results of your experiments you can use
"GitHub discussions" or discuss it in slack. But opening a "bug" in this case
is clearly a mistake resulting from misuse and not following the instructions,
rather than bug in airflow. This is precisely why it was marked as "invalid"
and "closed".
And if you want to propose new feature, change how docker compose works -
feel free. We actually have an open feature to make a more "versatile"
docker-compose setup with more examples and possibly wizard-like generation
https://github.com/apache/airflow/issues/16031 It would be great if you could
contribute to that
--
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]
