-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Deploying on a Stack that's not supported by this buildpack" #87
Comments
We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/98397482. |
See here for troubleshooting steps and a likely explanation: #86 |
Downgrading to version 3.2.2 worked for me too. Thanks 👍 |
Excellent! Just to be clear, downgrading is on a temporary solution. By downgrading, you're running a few risks: 1.) The 2.) The build packs are not producing new binaries for Ultimately you need to migrate to the |
I didn't know it was that easy to change the stack. I did it and it's working fine for me now on Bluemix. 👍 |
Is there a way to to default to |
@jsloyer - It's not up to the build pack to pick the stack. It just works with the stack it's given. If you're an application developer, you can use the default stack or set one with cf cli or via manifest.yml. It's up to the CF operator to set the default stack. I don't know how to do that offhand. You could ask on the cf-dev list, I'm sure someone there can point you in the right direction. |
I am getting this error while deploying this service on bluemix. This error was not their about a week ago. Don't know what's wrong.
Cloning into '/tmp/buildpacks/php-buildpack'...
Submodule 'compile-extensions' (https://github.com/cloudfoundry-incubator/compile-extensions) registered for path 'compile-extensions'
Cloning into 'compile-extensions'...
Submodule path 'compile-extensions': checked out '1f260464c156bddfb654adb14298344797d030a1'
It looks like you're deploying on a stack that's not supported by this buildpack.
That could be because you're using a recent buildpack release on a deprecated stack.
If you're using the buildpack installed by your CF admin, please let your admin know you saw this error message.
If you at one point specified a buildpack that's at git URL, please make sure you're pointed at a version that supports this stack.
The text was updated successfully, but these errors were encountered: