Troubleshooting

Out of date

This guide contains outdated information pertaining to Kubeflow 1.0. This guide needs to be updated for Kubeflow 1.1.

This page presents some hints for troubleshooting specific problems that you may encounter.

For help diagnosing environment issues that affect Kubeflow Pipelines, run the command-line tool.

The 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
  1. Install the .
  2. Run the kfp diagnose_me command.
  3. 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.

This error indicates that you have not installed the kfp package in your Python3 environment. Follow the instructions in the , 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:

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 or dsl-compile command-line tools.

This error occurs because installing the Kubeflow Pipelines SDK with --user stores kfp and dsl-compile in your ~/.local/bin directory. In some Linux distributions, the directory is not part of the $PATH environment variable.

You can resolve this issue by using one of the following options:

  • Add export $PATH=$PATH:~/.local/bin to the end of your ~/.bashrc file. Then restart your terminal session or run source ~/.bashrc.
  • Run the kfp and dsl-compile commands as and ~/.local/bin/dsl-compile.