Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex DataSphere
  • Getting started
  • Terraform reference
  • Audit Trails events
  • Access management
  • Pricing policy
  • Public materials
  • Release notes
    • Library installation issues
    • Errors when using a Spark connector
    • FAQ

In this article:

  • What are problems with dependencies?
  • Installing, deleting, or updating packages
  • Using dependency files
  • Using external repositories
  • Building your own Docker image
  • Known issues
  • ModuleNotFoundError
  • VersionConflict
  • Could not find a version that satisfies the requirement
  • What else you can do
  1. Troubleshooting
  2. Library installation issues

Troubleshooting issues with dependencies in Yandex DataSphere

Written by
Yandex Cloud
Updated at July 16, 2026
View in Markdown
  • What are problems with dependencies?
  • Installing, deleting, or updating packages
  • Using dependency files
  • Using external repositories
  • Building your own Docker image
  • Known issues
    • ModuleNotFoundError
    • VersionConflict
    • Could not find a version that satisfies the requirement
    • What else you can do

By default, DataSphere already contains popular machine learning packages and libraries. Library versions depend on the system image specified in the project settings. For the full list of installed packages, see List of pre-installed software.

Tip

If your project uses multiple libraries, and you have conflicts with pre-installed libraries, see Building your own Docker image. In DataSphere, usage of the virtual environment and console is limited.

What are problems with dependencies?What are problems with dependencies?

Conflicts of library versions occur when two packages require different versions of the same library. Non-matching library versions make package installation more difficult and may cause errors when running the code.

If the packages you need are missing in the standard DataSphere image, install them manually.

Some packages depend on system libraries which you cannot install in DataSphere due to the restriction on the use of sudo and apt. If this is your case, you will need a workaround.

If you get errors when installing or using packages, this may be due to conflicting versions of dependent libraries. Such errors come with messages like ModuleNotFoundError (module not found) or VersionConflict (incompatible version).

If there is an error during package installation, pip usually gives you a message detailing the cause. For example, in case of a version conflict, pip will specify the package and version that have caused the problem. Analyze these messages to understand the root cause of the problem.

Installing, deleting, or updating packagesInstalling, deleting, or updating packages

To avoid conflicts, you can install a specific version of a package. For example, to install seaborn 0.11.1, use the following command:

%pip install seaborn==0.11.1

Updating packages to the latest versions may sometimes help you solve problems with dependencies. To update a package, use this command:

%pip install --upgrade <package_name>

If you do not need the conflicting package, you can delete it:

%pip uninstall <package_name>

To avoid conflicts, specify the minimum required versions of the packages:

%pip install <package_name>>=<minimum_version>

Note

After installing, updating, or deleting a package, restart the JupyterLab kernel. To do this, click Kernel → Restart Kernel in the top panel of the project window.

Using dependency filesUsing dependency files

By using the requirements.txt dependency file, you can create a list of all required packages and their versions for a project. Doing so will simplify dependency installation on other systems and help you avoid issues when running a cross-system environment migration.

To install the packages and libraries from the requirements.txt file residing in the project root, run this command:

%pip install -r requirements.txt

To save a list of installed libraries to requirements.txt, run this command:

%pip freeze > requirements.txt

Note

If you want to deploy the environment from a dependency file created in DataSphere on another platform, delete the system packages installed via @.

Using external repositoriesUsing external repositories

If the package you need is not available in PyPI, you can install it directly from a repository, e.g., GitHub:

%pip install git+https://github.com/username/repository

You can specify a particular branch or commit to install:

%pip install git+https://github.com/username/repository@branch_name

Building your own Docker imageBuilding your own Docker image

Your own Docker image will allow you to set up an environment with the dependencies and tools you need, accelerate setting up new projects, and ensure stability of the environment. When creating your own Docker image, you can:

  • Use your own image prepared in advance.
  • Use clean Python images without pre-installed dependencies.
  • Install tools via apt.
  • Use library and driver versions that are different from the versions pre-installed in DataSphere, e.g., install another CUDA version.
  • Quickly install large libraries or download files.

To learn how to build your own image, see Working with Docker images.

Known issuesKnown issues

ModuleNotFoundErrorModuleNotFoundError

ModuleNotFoundError occurs when a package is not installed. To make sure the package is installed, run %pip install <package_name>. If you have just installed the package, restart the JupyterLab kernel.

VersionConflictVersionConflict

The VersionConflict error occurs when incompatible package versions are installed in the system. Check packages and install compatible versions:

%pip install <package_name>==<required_version>

After reinstalling the package, restart the JupyterLab kernel.

Could not find a version that satisfies the requirementCould not find a version that satisfies the requirement

The Could not find a version that satisfies the requirement error may occur if you specify a non-existing package version or the package is not available in the repository. Make sure the package name and version are correct and try installing another version.

What else you can doWhat else you can do

If you encounter an error you cannot fix, contact support.

Was the article helpful?

Previous
Release notes
Next
Errors when using a Spark connector
© 2026 Direct Cursus Technology L.L.C.