Running pip as root warning in v1.8 function-based component logs

[ypitrey]

I'm in the process of migrating an older pipeline running on kubeflow v1.8 from containerised components to python function-based components, as I hear it's the accepted best practice. I've got a very simple component defined as follows:

from kfp.components import create_component_from_func
check_readiness_op = create_component_from_func(
    func=check_readiness,
    base_image="python:3.10",
    packages_to_install=['requests'],
    output_component_file="check_readiness.yaml",  # Optional
)

And here's the call to that component in the pipeline:

check_readiness_task = check_readiness_op(param1=value1, param2=value2)

And in the component logs, one of the very first lines I see is this:

WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead

How can I solve this? I saw some examples in the kubeflow/examples repository where people did something like:

subprocess.check_call(["pip3", "install", "--user", "-r", "requirements.txt"])

but I was wondering if there's a less hacky way to do it. After all if I need to run pip manually I might just keep my containerised components where the separation of concerns looks cleaner with the Dockerfile running pip. Is there a way to work around that warning without adding any manual subprocess command runs?