{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicsb36ywjktjfxw42m7myzauyqi5kr7zh4c4ljxvr6a6r4oqjv6eu",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mkigrxdx4gr2"
  },
  "path": "/t/bug-docker-registry-for-new-spaces-returns-404-cannot-push-image/175599#post_1",
  "publishedAt": "2026-04-27T14:22:01.000Z",
  "site": "https://discuss.huggingface.co",
  "tags": [
    "https://registry.hf.space/v2/username/agent/tags/list",
    "http://localhost:7860"
  ],
  "textContent": "Description:\nI have tried every workaround found in the community (setting Space to Public, waiting after creation, Factory Rebuild, SDK toggle, etc.), but I am still unable to push a Docker image to any new Space. The registry endpoint appears to be missing for my user account.\nSteps to reproduce:\n\nCreate a new Space with the following settings:\n\nName: [agent]\n\nSDK: Docker\n\nVisibility: Public\n\nWait 2 minutes.\n\nRun the test command: curl -s https://registry.hf.space/v2/username/agent/tags/list\n\nObserved result:\n{“error”:“not found”,“code”:“NOT_FOUND”}\n\nExpected result:\n{“errors”:[{“code”:“UNAUTHORIZED”,…}]} (or a valid JSON response), indicating that the registry exists.\n\nAdditional context:\n\nA local Docker image (research-agent) builds and runs flawlessly with docker run -p 7860:7860 research-agent, and the app is accessible at http://localhost:7860.\n\nA docker login registry.hf.space -u username using a valid write User Access Token is successful.\n\nThis 404 error has been reproduced with multiple newly created Spaces across different days.\n\nA Factory Rebuild and toggling the SDK in the README.md did not resolve the issue.\n\nSystem information:\n\nOS: [Windows 10 with WSL2 or Ubuntu 22.04]\n\nDocker version: [Docker version 29.3.1, build c2be9cc]",
  "title": "[BUG] Docker registry for new Spaces returns 404 – cannot push image"
}