[Launcher] support non-root containers in v2 compatible mode
See original GitHub issueCurrently, because the launcher writes input artifacts to paths like:
/gcs/xxx
/minio/xxx
/s3/xxxx
These paths are not accessible by non-Root users by default.
When using a component with non-Root image, launcher fails when preparing input/output artifacts.
Because /gcs/xxx
is currently a contract for KFP v2 python component wrappers, we cannot change to a different path like /tmp/gcs/xxx
etc.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Run the Docker daemon as a non-root user (Rootless mode)
Rootless mode allows running the Docker daemon and containers as a non-root user to mitigate potential vulnerabilities in the daemon and the container ......
Read more >[APP][ROOT] LMT Launcher v3.2 | XDA Forums
LMT is a tool for Android (tested already on multiple devices but should run on nearly all) that launches a command when perform...
Read more >Get started with Package Support Framework - MSIX
In this article. Understand what is inside a Package Support Framework; Step 1: Identify packaged application compatibility issues; Step 2: Find ...
Read more >Enabling GPUs in the Container Runtime Ecosystem
It is compatible with the Open Containers Initiative (OCI) specification ... Tight integration with Docker did not allow support of other ...
Read more >Release notes for IBM Transformation Extender, V10.0.0
0.0 does not support the Launcher Hypervisor Edition. A Launcher Docker image for Linux platforms is available as an alternative. IBM Runtime ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
hey folks, is there any update on this? I’m guessing current state is that due to 2.0 coming along soon V2_COMPATIBLE wont be worked on? There are several companies running containers in rootless mode - Is. #6530 still up for consideration?
If we can remove restriction on Component container to be root it will be good. kfp-laucher init container can be root as we control that.