[
https://issues.apache.org/jira/browse/AIRFLOW-6823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038727#comment-17038727
]
Jarek Potiuk commented on AIRFLOW-6823:
---------------------------------------
It wont work [~ash] - > the problem is that the airflow files need to be
accessible (runnable scripts for example) by the logged user. There are a
number of scripts and binaries that are only runnable for the owner, not for
groups or others - similarly the directories are not group executable nor other
executable. That will prevent the new user from accessing them.
We would have to know that user id while we are building Docker (but we can't
as the user might be different on each installation). Another workaround is
changing ownership of all files at entry (but this makes no sense for us). What
could work is user remap feature
[https://www.jujens.eu/posts/en/2017/Jul/02/docker-userns-remap/] but it needs
to be configured at docker engine level.
> Breeze broken on current master on Linux
> ----------------------------------------
>
> Key: AIRFLOW-6823
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6823
> Project: Apache Airflow
> Issue Type: Bug
> Components: breeze
> Affects Versions: 2.0.0
> Reporter: Aleksander Nitecki
> Assignee: Ash Berlin-Taylor
> Priority: Minor
> Attachments: Breeze on current master log.txt
>
>
> See the attachment for log.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
