Skip to main content
GitLabCustomer feedback

A GitLab Omnibus customer running a separate container registry holding 6 TB of data is planning and seeking guidance on migrating metadata to the bundled PostgreSQL registry database.

What happened

Post: "Planning a container registry metadata database migration with a separate registry VM"

Source

RedditOct 7, 2026By u/rotten_grocery

r/gitlab

Planning a container registry metadata database migration with a separate registry VM

upvotes
3
comments
5

Post

Highlighted: the lines this signal was extracted from

We run a GitLab 19.3 using an Omnibus installation on a single VM. Our container registry runs separately, in a docker container using the GitLab provided registry image. Registry data is stored on NFS, and metadata currently uses the legacy filesystem based storage. The registry holds about 6 TB of data. We’re planning a migration to the registry database and would appreciate any advice on the architecture. My understanding is that GitLab already has a separate logical DB for registry metadata in its bundled postgres instance. Could our separate registry node use that DB? If so, we would need to enable TCP access to Postgres on the gitlab VM and restrict access only to the registry VM. Is that a recommended and secure setup? We’re especially interested in how others have handled the migration at this scale, including downtime, security and ongoing maintenance. Thanks for any guidance or experience you can share

reddit.com/r/gitlab/comments/1wzxk2a/planning_a_container_registry_me...Read the full source

Comments on the post

2 of 5 comments
  • “pointing it at the bundled postgres over tcp works fine, just set listen_address and add only the registry vm ip to md5_auth_cidr_addresses. at 6tb i'd do the three step import so only the last blob step needs the registry in read only”

    u/Torutofu_Raeva0 points · Oct 7, 2026View

  • “why a separate gitlab? why not use a container hosting tool designed for containers like Harbor”

    u/pwkye0 points · Oct 7, 2026View

Extracted by Autobound

From the Signal API record
Signal
Customer feedback

What this signalsUser posts often show product pain before it reaches reviews or churn.

Subreddit
r/gitlab
Event date
Oct 2026

Companies

  • HarborAlso named

The full record

From the Signal API record

Numbers

Mentions
2

Details

Timing
In progress
Category
Implementation
Virality
Low
Post kind
Text
Prominence
Core
Company's role
Vendor

Topics and mentions

Topics

  • container registry
  • database migration
  • devops
  • omnibus

Flair

  • support

Products named

  • GitLab
  • GitLab Omnibus
  • GitLab Container Registry

Extraction

Sentiment
Neutral
Detected
Oct 7, 2026
signal_type
reddit-company
signal_subtype
customerFeedback

Use this data

Get every Reddit signal for GitLab and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at GitLab this week?”

  2. Send it to your own tools

    The Signal API returns Reddit signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full reddit-company record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/9680e963-00ca-5e45-a371-eb5aa401eec2 returns this record as JSON. POST /v1/companies/enrich returns every signal for gitlab.com.

{
  "signal_id": "9680e963-00ca-5e45-a371-eb5aa401eec2",
  "signal_type": "reddit-company",
  "signal_subtype": "customerFeedback",
  "detected_at": "2026-10-07T14:10:47+00:00",
  "company": {
    "name": "GitLab",
    "domain": "gitlab.com"
  },
  "data": {
    "nsfw": false,
    "stage": "none",
    "awards": 0,
    "timing": "in_progress",
    "topics": [
      "devops",
      "container registry",
      "database migration",
      "omnibus"
    ],
    "post_id": "1wzxk2a",
    "summary": "A GitLab Omnibus customer running a separate container registry holding 6 TB of data is planning and seeking guidance on migrating metadata to the bundled PostgreSQL registry database.",
    "category": "implementation",
    "comments": [
      {
        "url": "https://www.reddit.com/r/gitlab/comments/1wzxk2a/comment/pefzj2d/",
        "depth": 0,
        "score": 0,
        "author": "Torutofu_Raeva",
        "excerpt": "pointing it at the bundled postgres over tcp works fine, just set listen_address and add only the registry vm ip to md5_auth_cidr_addresses. at 6tb i'd do the three step import so only the last blob step needs the registry in read only",
        "posted_at": "2026-10-07T15:03:39.000Z",
        "author_url": "https://www.reddit.com/user/Torutofu_Raeva/"
      },
      {
        "url": "https://www.reddit.com/r/gitlab/comments/1wzxk2a/comment/peipn4o/",
        "depth": 0,
        "score": 0,
        "author": "pwkye",
        "excerpt": "why a separate gitlab?\n\n why not use a container hosting tool designed for containers like Harbor",
        "posted_at": "2026-10-07T21:57:50.000Z",
        "author_url": "https://www.reddit.com/user/pwkye/"
      }
    ],
    "evidence": [
      "[post] We run a GitLab 19.3 using an Omnibus installation on a single VM. Our container registry runs separately, in a docker container using the GitLab provided registry image.",
      "[post] The registry holds about 6 TB of data. We’re planning a migration to the registry database and would appreciate any advice on the architecture."
    ],
    "virality": "low",
    "post_date": "2026-10-07T14:10:47.000Z",
    "post_kind": "text",
    "post_text": "We run a GitLab 19.3 using an Omnibus installation on a single VM. Our container registry runs separately, in a docker container using the GitLab provided registry image. Registry data is stored on NFS, and metadata currently uses the legacy filesystem based storage. The registry holds about 6 TB of data.\n\nWe’re planning a migration to the registry database and would appreciate any advice on the architecture. My understanding is that GitLab already has a separate logical DB for registry metadata in its bundled postgres instance. Could our separate registry node use that DB?\n\nIf so, we would need to enable TCP access to Postgres on the gitlab VM and restrict access only to the registry VM. Is that a recommended and secure setup?\n\nWe’re especially interested in how others have handled the migration at this scale, including downtime, security and ongoing maintenance. Thanks for any guidance or experience you can share",
    "sentiment": "neutral",
    "subreddit": "gitlab",
    "event_date": "2026-10",
    "post_flair": [
      "support"
    ],
    "post_title": "Planning a container registry metadata database migration with a separate registry VM",
    "prominence": "core",
    "source_url": "https://www.reddit.com/r/gitlab/comments/1wzxk2a/planning_a_container_registry_metadata_database/",
    "entity_role": "vendor",
    "post_author": "rotten_grocery",
    "upvote_ratio": 0.8,
    "mention_count": 2,
    "mention_surge": false,
    "subreddit_url": "https://www.reddit.com/r/gitlab/",
    "total_upvotes": 3,
    "comments_total": 5,
    "total_comments": 5,
    "other_companies": [
      {
        "name": "Harbor",
        "role": "alternative"
      }
    ],
    "post_author_url": "https://www.reddit.com/user/rotten_grocery/",
    "signal_category": "feedback",
    "comments_included": 2,
    "products_mentioned": [
      "GitLab",
      "GitLab Omnibus",
      "GitLab Container Registry"
    ]
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.