LogoLogo
Release notesAPI docsDocs homeEphemeral CloudTonic.ai
  • Tonic Ephemeral guide
  • About Tonic Ephemeral
  • Getting started with the Ephemeral free trial
  • Managing your Ephemeral account
  • Managing Databases
    • Viewing the list of databases
    • Starting a database
    • Changing the database configuration
    • Database configuration settings
      • Setting the required resources for a database
      • Setting the database expiration
      • Providing a custom configuration file
    • Connecting to a database
    • Resetting a database
    • Deactivating and reactivating databases
    • Managing auto snapshots
    • Tracking database activity
    • Deleting a database
  • Managing user snapshots
    • About user snapshots
    • Viewing the user snapshot list
    • Creating a user snapshot from an Ephemeral database
    • Creating a user snapshot from imported data
    • Editing a user snapshot
    • Creating a database from a user snapshot
    • Deleting a user snapshot
  • Installing and configuring Ephemeral
    • Ephemeral architecture
    • Configuring an allowlist for Ephemeral Cloud database connections
    • Installing a self-hosted instance of Ephemeral
      • System requirements
      • Deploying Ephemeral with Helm
    • Configuring database access on a self-hosted instance
    • Configuring tolerations and node selectors
    • Managing access to Ephemeral
      • Managing Ephemeral users
      • Enabling SSO on a self-hosted instance
        • Google
        • Okta
    • Setting the registry location for data volumes
    • Managing custom images
      • Creating, editing, and deleting custom images
      • Oracle image configuration
    • Configuring automatic deletion of snapshots
  • Monitoring and data collection
    • Monitoring your Ephemeral billed usage
    • Monitoring your disk storage
    • Data that Tonic.ai collects
  • Using the Ephemeral API
    • About the Ephemeral API
    • Configuring Ephemeral
    • Getting information about Ephemeral databases
    • Starting a database
    • Managing databases
    • Managing snapshots
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Installing and configuring Ephemeral

Setting the registry location for data volumes

PreviousOktaNextManaging custom images

Last updated 3 months ago

Was this helpful?

For Tonic Ephemeral, the configured container registry is used to store data volumes that are used to create databases. These can include data volumes that Tonic Structural creates when it writes output to a container repository.

If you change the registry location, then when you start a new database, you won't have access to volumes that were in the original location. You must manually move the volumes to the new location.

If you only update the credentials, then you must make sure that the new credentials have the required permissions for the existing repositories.

To change the registry location:

  1. In the Ephemeral navigation bar, click Admin Settings.

  2. On the Admin Settings page, click Registry.

  1. In the Registry URL field, provide the URL to the registry location.

  2. Provide the credentials for Ephemeral to use to read from and write to the registry. On a self-hosted instance, you can either provide a username and access token, or provide a secret.

    On Ephemeral Cloud, you must provide a username and access token.

  3. Click Save.

Registry Settings fields to configure the registry location