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 Cloud Registry
  • Getting started
    • All guides
        • Configuring APT
        • Pushing a Debian package to a registry
        • Pulling a Debian package from a registry
      • Deleting an artifact from a registry
    • Creating a lifecycle policy
  • Access management
  • Pricing policy
  • Terraform reference
  • Audit Trails events

In this article:

  • Installing from a local registry
  • Installing from a remote registry
  1. Step-by-step guides
  2. Managing artifacts
  3. Debian artifact
  4. Pulling a Debian package from a registry

Pulling a Debian package from a registry

Written by
Yandex Cloud
Updated at July 29, 2026
View in Markdown
  • Installing from a local registry
  • Installing from a remote registry

Follow this guide to install a Debian package from a Yandex Cloud Registry using the APT package manager (Advanced Package Tool).

To pull a Debian package, you need the cloud-registry.artifacts.puller role or higher.

Before you begin, configure APT to work with the registry.

Installing from a local registryInstalling from a local registry

A local registry contains packages created and published within your organization.

  1. Update the list of packages:

    apt-get update
    
  2. Install a package:

    apt-get install <package_name>
    

    Where <package_name> is the name of the package to install.

Installing from a remote registryInstalling from a remote registry

A remote registry acts as a proxy for external Debian repositories. Remote registries cache packages locally after the first request.

Caching is only supported for registries that implement one of the following package storage formats:

  • Standard format: /pool/<component>/<letter>/<package_name>/...deb. This format is used in repositories such as archive.ubuntu.com and deb.debian.org.
  • Cloud Registry format.

Note

Remote registries do not support the Flat Repository Format.

  1. Update the list of packages:

    apt-get update
    
  2. Install a package:

    apt-get install <package_name>
    

    Where <package_name> is the name of the package being installed from an external repository.

    Upon the first request, the package will be pulled from the external repository and stored in the cache. During subsequent installations, the package will be loaded from the cache.

Useful linksUseful links

  • Configuring the APT package manager
  • Pushing a Debian package to a registry

Was the article helpful?

Previous
Pushing a Debian package to a registry
Next
Deleting an artifact from a registry
© 2026 Direct Cursus Technology L.L.C.