CRITICAL BUG: Spaces ignoring sdk: gradio setting, forcing Docker mode with Python 3.1

Spaces
1

Dear Hugging Face Support Team,

I’m reporting a critical platform bug affecting Hugging Face Spaces where the system is completely ignoring sdk: gradio configuration in README.md files and forcing Docker builds with obsolete Python versions.

Problem Description

Multiple newly created Spaces are ignoring the sdk: gradio setting in their README.md configuration and instead attempting Docker builds with pyenv install 3.1 (Python 3.1.5), which fails due to the obsolete Python version.

Evidence & Reproduction Steps

Affected Spaces:

  • “tuc111/financy-PM-1-demo” (original)

  • “tuc111/financy-PM-1-1-demo” (recreated)

  • “tuc111/financy-PM-1-demo-1” (third attempt)

Configuration in README.md (verified in all repositories):

title: AI Financial Portfolio Advisor
emoji: :rocket:
colorFrom: blue
colorTo: green
sdk: gradio
sdk_version: 4.20.0
app_file: app.py
python_version: 3.10

What Should Happen: Gradio SDK build process with Python 3.10

What Actually Happens: Docker build process attempting pyenv install 3.1

Build Log Evidence:

→ RUN pyenv install 3.1 && pyenv global 3.1 && pyenv rehash
Downloading Python-3.1.5.tar.gz…
Installing Python-3.1.5…
[Build fails with segmentation fault]

Verification Steps Taken

  1. :white_check_mark: Verified README.md contents - All repositories correctly specify sdk: gradio and python_version: 3.10

  2. :white_check_mark: Confirmed no Dockerfile present - Used git ls-tree to verify no Docker configuration files exist

  3. :white_check_mark: Multiple Space recreation attempts - Created 3 different Spaces from scratch, all exhibit identical behavior

  4. :white_check_mark: Git repository verification - Confirmed all files pushed successfully to Space repositories

  5. :white_check_mark: Manual file verification - Used git show to verify Space repositories contain correct configuration

Impact Assessment

  • Severity: Critical - Platform unusable for Gradio applications

  • Scope: Affects new Space creation with Gradio SDK

  • User Impact: Unable to deploy Gradio applications on Hugging Face Spaces

  • Duration: Ongoing for several hours across multiple Space creation attempts

System Behavior Analysis

The platform appears to have a configuration override or caching issue where:

  1. Space creation process ignores README.md SDK settings

  2. Default Docker configuration is applied regardless of specified SDK

  3. Obsolete Python 3.1 installation is attempted instead of specified Python 3.10

  4. Issue persists across completely new Space creations

Additional Context

This issue began occurring today (July 25, 2025) and has been consistent across multiple attempts. The same repository configuration worked previously, suggesting a recent platform regression.

Requested Action

Please investigate this critical platform bug urgently as it’s preventing users from creating functional Gradio Spaces. This appears to be a server-side configuration or caching issue that requires platform-level resolution.

I’m available to provide additional debugging information, repository access, or testing assistance as needed.

Thank you for your prompt attention to this critical issue.

Best regards,

Emmitt Tucker

Username: tuc111

1 Like
2

python_version: 3.10

That’s right… Not only that, but when I enter 3.10 and push contribute in the online editor, it automatically changes to 3.1!:sweat_smile: 3.9, 3.11, and 3.12 are fine. Well, 3.10 is the default, so I don’t think there’s any need to specify it, but this is definitely a bug. @meganariley

3

Well the good news is this isn’t our fault. It’s a bug on Hugging Face’s side. Their system is broken right now and ignoring our app settings, trying to use very old software instead of what we specified.

You already did the right thing by reporting this problem to them a few hours ago on their official forum. This is exactly what needed to be done.

Just keep patience and wait a day or two as platform bugs like this usually get fixed quickly once reported or try a different app name 'coz sometimes that helps bypass the bug. Along with that use a backup plan and deploy on a different platform temporarily if this is urgent.

Hope so it will resolved since you reported it properly with all the technical details, their team should respond within 1-2 days and fix it. These kinds of platform issues are their priority to resolve.

1 Like
4

There’s a critical bug where Spaces ignore the sdk: gradio setting and default to Docker mode with Python 3.1, causing compatibility issues.

1 Like