This page presents some hints for troubleshooting specific problems that you may encounter.
Diagnosing problems in your Kubeflow Pipelines environment
For help diagnosing environment issues that affect Kubeflow Pipelines, run
kfp diagnose_me command-line tool.
kfp diagnose_me CLI reports on the configuration of your local
development environment, Kubernetes cluster, or Google Cloud environment.
Use this command to help resolve issues like the following:
- Python library dependencies
- Trouble accessing resources or APIs using Kubernetes secrets
- Trouble accessing Persistent Volume Claims
To use the
kfp diagnose_me CLI, follow these steps:
- Install the Kubeflow Pipelines SDK.
- Follow the guide to configuring access to Kubernetes clusters, to update your kubeconfig file with appropriate credentials and endpoint information to access your Kubeflow cluster. If your Kubeflow Pipelines cluster is hosted on a cloud provider like Google Cloud, use your cloud provider’s instructions for configuring access to your Kubernetes cluster.
- Run the
- Analyze the results to troubleshoot your environment.
Troubleshooting the Kubeflow Pipelines SDK
The following sections describe how to resolve issues that can occur when installing or using the Kubeflow Pipelines SDK.
Error: Could not find a version that satisfies the requirement kfp
This error indicates that you have not installed the
kfp package in your
Python3 environment. Follow the instructions in the Kubeflow Pipelines SDK
installation guide, if you have not already
installed the SDK.
If you have already installed the Kubeflow Pipelines SDK, check that you have Python 3.5 or higher:
The response should be something like the following:
If you do not have Python 3.5 or higher, you can download Python from the Python Software Foundation.
kfp or dsl-compile command not found
If your install the Kubeflow Pipelines SDK with the
--user flag, you may
get the following error when using the
bash: kfp: command not found
This error occurs because installing the Kubeflow Pipelines SDK with
dsl-compile in your
In some Linux distributions, the
~/.local/bin directory is not part of the
$PATH environment variable.
You can resolve this issue by using one of the following options:
export $PATH=$PATH:~/.local/binto the end of your
~/.bashrcfile. Then restart your terminal session or run
- Run the
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.