-
Notifications
You must be signed in to change notification settings - Fork 467
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
Run KFP container as local user/group if local #304
Conversation
Some files and folders in the local repositories (e.g. database, .system TFX directories) are shared between different runs of the same pipeline or of different pipelines. If pipelines are run in the context of different users, such as when switching between KFP and the local orchestrators, this can create problems with permissions. Running the KFP containers with the same UID/GID as the local user maintains permissions consistent across orchestrators. Signed-off-by: Stefan Nica <stefan@zenml.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, just one question: Do you know if the bug also happened on windows in some form? Or do they just not care about any permissions and it already worked before this PR?
I don't think we even support KFP as a local orchestrator on Windows, but even if we did, the Windows host should ignore file permissions set on the KFP side. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, it might be worth checking out how it behaves on windows though
cb9f5d7
to
ee0942d
Compare
looks good to me as well! |
Pre-requisites
Please ensure you have done the following:
Types of changes
Describe changes
Some files and folders in the local repositories (e.g. database,
.system TFX directories) are shared between different runs of the
same pipeline or of different pipelines. If pipelines are run
in the context of different users, such as when switching between
KFP and the local orchestrators, this can create problems with
permissions.
Running the KFP containers with the same UID/GID as the local
user maintains permissions consistent across orchestrators.