{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicc7p7sblzisxdsmlowgcx2xwssbdwdniw74kldnuonnmor6veuo4",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mhz7fwzplfe2"
  },
  "path": "/t/spaces-persistent-storage-upgrade-not-accessible/171226#post_14",
  "publishedAt": "2026-03-27T00:59:54.000Z",
  "site": "https://discuss.huggingface.co",
  "tags": [
    "https://docs.argilla.io/latest/getting_started/how-to-deploy-argilla-with-docker/"
  ],
  "textContent": "# Posting this as a follow-up for others facing the same issue.\n\nWe ran into the same problem with an Argilla Space — after the persistent storage upgrade, the Space became inaccessible and we lost the dataset.\nThe core issue seemed to be a disconnect: the small storage tier we had originally configured in Argilla is no longer available, leaving the Space in a broken state with no clear migration path.\n\nWe tried three approaches, none of which fully resolved the problem:\n\n### 1. Requesting the storage upgrade programmatically via the API\n\nFollowing the steps from this forum, we called request_space_storage() with a write-access token:\n\n\n    load_dotenv(Path.cwd() / “.env”)  HF_STORAGE = os.environ.get(“HF_STORAGE”)\n\n    api = HfApi(token=HF_STORAGE)repo_id = “your-username/your-space-name”\n\n    api.request_space_storage(repo_id=repo_id, storage=SpaceStorage.SMALL)print(f\"Storage requested for {repo_id}\")\n\n\nResult:\n\n\n    HfHubHTTPError: Client error ‘404 Not Found’ for url‘https://huggingface.co/api/spaces/your-username/your-space-name/storage’\n\n\nThe endpoint returns 404 — the SMALL storage tier appears to no longer be available for this Space. The upgrade option is also absent from the Space\nSettings UI.\n\n### 2.Uploading the dataset to a Hub dataset repository\n\nWe followed the standard pattern — created a dataset repo, set an HF token with write access as a Space secret, and pushed the data via huggingface_hub. The data transferred fine, but this approach does not reproduce the Argilla-specific configuration: dataset settings, annotation guidelines, label schemas, and field definitions set up in the Argilla UI are not exported with the data. You get the raw records but lose the annotation workspace entirely.\n\n### 3.Self-hosting Argilla on an external VPS (Vultr)\n\nWe deployed Argilla on a Vultr instance (4 GB RAM / 128 GB storage, Ubuntu) using the official Argilla Docker Compose setup:\n\n  1. Provision an Ubuntu instance on Vultr\n  2. Install Docker via the official Docker apt repository: https://docs.argilla.io/latest/getting_started/how-to-deploy-argilla-with-docker/\n  3. Download the Argilla docker-compose.yaml from argilla-io/argilla on GitHub\n  4. Edit credentials in the compose file\n  5. Start with docker compose up -d and open the Argilla port via iptables\n\n\n\nThis worked initially — the instance runs at a custom server IP with no dependency on HF persistent storage. However, data uploaded to Argilla on the VPS is also lost when the server is reset, so this does not fully solve the durability problem either.\n\nWe are still looking for a reliable solution. Has anyone found a way to either recover access to the original persistent storage tier, or set up a durable Argilla deployment that survives resets?",
  "title": "Spaces Persistent Storage Upgrade Not Accessible"
}