Store RPM packages in Artifact Registry

This quickstart shows you how to set up a private Artifact Registry Yum repository, add an RPM package to the repository, and install the package on a Compute Engine VM running the CentOS 7 operating system. To learn how to configure Yum repositories that use DNF see Configuring VMs to install RPM packages.

You perform steps in this quickstart using Cloud Shell and in the shell on the VM that you create in this quickstart.

To learn more about managing RPM packages, see Working with RPM packages.

Before you begin

  1. Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.
  2. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

    Go to project selector

  3. Make sure that billing is enabled for your Google Cloud project.

  4. Enable the Artifact Registry API.

    Enable the API

  5. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

    Go to project selector

  6. Make sure that billing is enabled for your Google Cloud project.

  7. Enable the Artifact Registry API.

    Enable the API

Launch Cloud Shell

Cloud Shell comes preinstalled with the Google Cloud CLI. The gcloud CLI provides the primary command-line interface for Google Cloud.

Launch Cloud Shell:

  1. Go to Google Cloud console.

    Google Cloud console

  2. On the Google Cloud console toolbar, click Activate Cloud Shell:

A Cloud Shell session opens inside a frame lower on the console. You'll use this shell to run the gcloud commands to create a VM and a repository.

Create a repository

Create the repository for your artifacts.

  1. Create the repository:

    Console

    1. Open the Repositories page in the Google Cloud console.

      Open the Repositories page

    2. Click Create Repository.

    3. Specify quickstart-yum-repo as the repository name.

    4. Select Yum as the format.

    5. Under Location Type, select Region and then choose the location us-central1.

    6. Click Create.

    The repository is added to the repository list.

    gcloud

    1. In Cloud Shell, run the following command to create a new Yum repository in the current project named quickstart-yum-repo in the location us-central1.

      gcloud artifacts repositories create quickstart-yum-repo \
          --repository-format=yum \
          --location=us-central1 \
          --description="Yum repository"
      
    2. Run the following command to verify that your repository was created:

      gcloud artifacts repositories list
      

You can now add a package to the repository.

Add a package to the repository

You can upload a package to a repository using the Google Cloud CLI, or you can import a package that is stored in Cloud Storage. If you build packages using Cloud Build, the build can store the packages in Cloud Storage for you to import.

For this quickstart, you upload a sample file using the gcloud artifacts yum upload command.

  1. In Cloud Shell, download the nano text editor with the command:

    sudo yum install --downloaddir=. --downloadonly nano
    

    Yum downloads the latest version of the package that is available from your configured CentOS repositories.

    Loaded plugins: fastestmirror
    Loading mirror speeds from cached hostfile
     * base: mirror.dal.nexril.net
     * epel: ord.mirror.rackspace.com
     * extras: centos.mirror.lstn.net
     * updates: ftpmirror.your.org
    Resolving Dependencies
    --> Running transaction check
    ---> Package nano.x86_64 0:2.3.1-10.el7 will be installed
    --> Finished Dependency Resolution
    
    Dependencies Resolved
    
    ================================================================================
     Package        Arch             Version                   Repository      Size
    ================================================================================
    Installing:
     nano           x86_64           2.3.1-10.el7              base           440 k
    
    Transaction Summary
    ================================================================================
    Install  1 Package
    
    Total download size: 440 k
    Installed size: 1.6 M
    Background downloading packages, then exiting:
    nano-2.3.1-10.el7.x86_64.rpm                               | 440 kB   00:00
    exiting because "Download Only" specified
    

    Run ls to get the filename of package. The filename is similar to nano-2.3.1-10.el7.x86_64.rpm.

  2. To simplify gcloud commands, set the default repository to quickstart-yum-repo and the default location to us-central1. After the values are set, you do not need to specify them in gcloud commands that require a repository or a location.

    To set the repository, run the command:

    gcloud config set artifacts/repository quickstart-yum-repo
    

    To set the location, run the command:

    gcloud config set artifacts/location us-central1
    

    For more information about these commands, see the gcloud config set documentation.

  3. Run the gcloud artifacts yum upload to upload the package to the repository:

    gcloud artifacts yum upload quickstart-yum-repo \
        --source=FILE_NAME
    

    Replace FILE_NAME with the path to the nano package.

View the package in the repository

Verify that your package was added to the repository.

Console

  1. Open the Repositories page in the Google Cloud console.

    Open the Repositories page

  2. In the repository list, click the quickstart-yum-repo repository.

    The Packages page lists the packages in the repository.

gcloud

To list the packages in the quickstart-yum-repo repository, run the command:

 gcloud artifacts packages list

To view versions for a package in quickstart-yum-repo, run the command:

gcloud artifacts versions list --package=nano

Create a VM

Create a new Compute Engine VM where you'll install the sample package.

In Cloud Shell, run the following command to create a VM instance named quickstart-yum-vm.

gcloud compute instances create quickstart-yum-vm \
    --image-family=centos-7 \
    --image-project=centos-cloud \
    --scopes=cloud-platform

By default, the VM does not have the required access scopes for working with the repository. The --scopes flag sets the access scope for the VM to cloud-platform.

Configure the package manager

To install a package on the VM, add the repository you created to the Yum file that defines package repositories.

  1. Go to the VM instances page.

    Open the VM instances page

  2. In the row with your VM, click SSH. A new window opens with a terminal session on the VM.

  3. Update Yum:

    sudo yum makecache
    
  4. Install the Yum credential helper on the VM to enable Yum to perform authentication, using the following command:

    sudo yum install yum-plugin-artifact-registry
    
  5. Configure your VM to access Artifact Registry packages using the following command:

    sudo tee -a /etc/yum.repos.d/artifact-registry.repo << EOF
    [yum-quickstart]
    name=My Repository
    baseurl=https://us-central1-yum.pkg.dev/projects/PROJECT/quickstart-yum-repo
    enabled=1
    repo_gpgcheck=0
    gpgcheck=0
    EOF
    

    Replace PROJECT with your Google Cloud project ID.

Install the package

Install the package that you added to the repository.

  1. Update the list of available packages:

    sudo yum makecache
    
  2. Install the package in your repository.

    sudo yum --enablerepo=yum-quickstart install nano
    

    Enter y when prompted.

    The returned installation information looks like the following example:

    Loaded plugins: fastestmirror
    Loading mirror speeds from cached hostfile
     * base: mirrors.cmich.edu
     * epel: ord.mirror.rackspace.com
     * extras: mirror.team-cymru.com
     * updates: mirror.us-midwest-1.nexcess.net
    quickstart-yum-repo                                      | 1.3 kB     00:00
    Resolving Dependencies
    --> Running transaction check
    ---> Package nano.x86_64 0:2.3.1-10.el7 will be installed
    --> Finished Dependency Resolution
    
    Dependencies Resolved
    
    ================================================================================
     Package        Arch             Version                   Repository      Size
    ================================================================================
    Installing:
     nano           x86_64           2.3.1-10.el7              base           440 k
    
    Transaction Summary
    ================================================================================
    Install  1 Package
    
    Total size: 440 k
    Installed size: 1.6 M
    Is this ok [y/d/N]: y
    Downloading packages:
    Running transaction check
    Running transaction test
    Transaction test succeeded
    Running transaction
      Installing : nano-2.3.1-10.el7.x86_64                                     1/1
      Verifying  : nano-2.3.1-10.el7.x86_64                                     1/1
    
    Installed:
      nano.x86_64 0:2.3.1-10.el7
    
    Complete!
    

Clean up

To avoid incurring charges to your Google Cloud account for the resources used on this page, follow these steps.

Before you remove the repository, ensure that any packages you want to keep are available in another location.

To delete the repository:

Console

  1. Open the Repositories page in the Google Cloud console.

    Open the Repositories page

  2. In the repository list, select the quickstart-yum-repo repository.

  3. Click Delete.

gcloud

  1. To delete the quickstart-yum-repo repository, run the following command:

    gcloud artifacts repositories delete quickstart-yum-repo
    
  2. If you want to remove the default repository and location settings that you configured for the active gcloud configuration, run the following commands:

    gcloud config unset artifacts/repository
    gcloud config unset artifacts/location
    

To delete the VM you created, run the following command:

gcloud compute instances delete quickstart-yum-vm

What's next