Docker Space Build Fails: "Build Queued" then "exit code 1" with no detailed logs

Beginners
1

Hi Hugging Face Community,

I’m encountering a persistent issue with deploying Docker SDK Spaces. Both my main project Space and a very minimal test Space are failing in the same way: the build log only shows “Build Queued at [timestamp] / Commit SHA: [SHA]” and then immediately a “Build error. Job failed with exit code: 1”. No detailed Docker build step logs (like FROM..., RUN..., COPY... etc.) are visible.

Here are the details:

Affected Spaces:

  • Main Project Space (complex): https://huggingface.co/spaces/kimseonghyeonyeah/my-midjourney-api
  • Minimal Docker Test Space: https://huggingface.co/spaces/kimseonghyeonyeah/space_test (This uses a very simple Dockerfile: FROM python:3.10-slim \n CMD ["python3", "-m", "http.server", "7860"])

Key Observation:

  • I was able to successfully deploy a Streamlit SDK Space from the same network environment just yesterday. This current issue seems specific to Docker SDK Spaces.

Troubleshooting Steps Taken (for both Spaces where applicable):

  1. Verified README.md YAML Configuration: Ensured sdk: docker and app_port: 7860 are correctly set. The YAML appears valid.
  2. Resolved Git LFS Issues: All Git LFS configurations are now correct, and git push operations (including LFS file uploads if any were pending) complete successfully to the Space repository. The current issue is with the subsequent build process.
  3. Factory Reboots: Tried “Factory Reboot” multiple times on the Spaces.
  4. Triggered Rebuilds: Made minor changes to files (e.g., README.md) and pushed new commits to trigger fresh builds.
  5. Python Version Specification (for the main project Space): Tried adding python_version: 3.9 and subsequently python_version: 3.9.13 to the README.md YAML header of the my-midjourney-api Space, based on suggestions from similar forum posts.
  6. Minimal Test Case: The space_test mentioned above was created with a barebones Dockerfile and README.md. It fails identically to the main project Space (no detailed build logs, just “Build Queued” then “exit code 1”).

Environment Context:

  • I am currently operating from an institutional network.
  • Unfortunately, testing from a completely different network environment (e.g., mobile hotspot, home network) is not feasible for me at this moment.

Given that even an extremely minimal Docker Space fails in the same way from my current environment, while a Streamlit Space worked, I suspect this might be an issue related to how the Docker SDK build process interacts with my network, or a platform-side issue specific to Docker builds (perhaps for my account or region).

Could anyone provide insights or suggestions on what might be causing Docker builds to fail at such an early stage without producing detailed logs, and why this might differ from my experience with the Streamlit SDK? Any help in diagnosing this would be greatly appreciated.

Thank you!

1 Like
2

kimseonghyeonyeah/space_test with:

FROM python:3.10-slim
CMD ["python3", "-m", "http.server", "7860"]

works.

I suspect this might be an issue related to how the Docker SDK build process interacts with my network, or a platform-side issue specific to Docker builds (perhaps for my account or region).

Seems so.