[BUG] Docker registry for new Spaces returns 404 – cannot push image

Description: I 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. Steps to reproduce:

Create a new Space with the following settings:

Name: [agent]

SDK: Docker

Visibility: Public

Wait 2 minutes.

Run the test command: curl -s https://registry.hf.space/v2/username/agent/tags/list

Observed result: {“error”:“not found”,“code”:“NOT_FOUND”}

Expected result: {“errors”:[{“code”:“UNAUTHORIZED”,…}]} (or a valid JSON response), indicating that the registry exists.

Additional context:

A 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.

A docker login registry.hf.space -u username using a valid write User Access Token is successful.

This 404 error has been reproduced with multiple newly created Spaces across different days.

A Factory Rebuild and toggling the SDK in the README.md did not resolve the issue.

System information:

OS: [Windows 10 with WSL2 or Ubuntu 22.04]

Docker version: [Docker version 29.3.1, build c2be9cc]