New Builds failing for old site. Python runtime not found

Support
1

I am using mkdocs to build a site which has worked fine until this morning:

10:15:53 AM: Installing dependencies

10:15:53 AM: /usr/local/bin/run-build-functions.sh: line 168: /opt/buildhome/python3.7/bin/activate: No such file or directory

10:15:53 AM: Error setting python version from runtime.txt

10:15:53 AM: failed during stage ‘building site’: Build script returned non-zero exit code: 1

10:15:53 AM: Please see GitHub - netlify/build-image: This is the build image used for running automated builds for current versions

10:15:53 AM: Error running command: Build script returned non-zero exit code: 1

10:15:53 AM: Failing build: Failed to build site

I have a runtime.txt file in my root with 3.7 specified but it won’t accept it?

2

Hi @mojowill and welcome to our community!

Sorry to hear about the trouble. I see you got a recent build to work, and I can’t understand why it wouldn’t have been before unless you changed some settings around. Could you tell us what you did to get the latest build to work? I note that it uses python 3.7…

3

Turned out that it was using an older build image (Ubuntu 14) so Python 3 wasn’t there. All fixed now.

1 Like