-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to configure the running user inside the docker container #701
base: master
Are you sure you want to change the base?
Allow to configure the running user inside the docker container #701
Conversation
… able to match volume owners to host owners on unix like systems
Thanks for the PR and for spending time on this, but
So thanks again, and I will close this PR |
@petefoth Oh, I am a bit surprised by your reaction. Your last comment in #407:
suggested to me you would be happy about this PR. May I ask what changed your mind? Why does the project from your point of view does not want or need this feature? I implemented this PR not only because of the OP of #407. I certainly also need this functionality. It is otherwise a pain to develop and port for lineagos / microg in linux. One would need to change permissions of the mounted volume files and folders all the time if this functionality is missing (this means changing ownership of alot of files ... the whole Lineagos source tree). So I am very interested why you don't think this is needed and do not want it anymore. Maybe the whole thing is just a misunderstanding? About the wording 'fix', well sure, I can certainly change that in the merge request description. I just used it as then the PR automatically gets referenced in the issue. best |
OK. Firstly my apologies for my previous response: I shouldn't respond to PRs late at night without spending enough time thinking about them. Secondly,
We don't need it, because
We (I) don't particularly want it because:
However, I will reopen the PR. But before I would consider merging it, I would need to know what testing of the changes has been carried out. In particular I need to know that as, well as allowing the functionality it implements, it does not break the existing functionality of
I don't have time or resources to do that testing, so I would need to know that the testing has been done and has succeeded. |
Re-opening the PR causes some checks to be run automatically. These checks have failed - running ShellCheck failed
See https://github.com/lineageos4microg/docker-lineage-cicd/actions/runs/11549112512/job/32141609648 |
implements #407