Rebuilding an app in Dokku results in 'ERROR: Failed to download minimal PHP for bootstrapping!'
I'm using Dokku for over a year now, most of the programs are written in node.js. But for a Wordpress blog we use the default heroku PHP buildpack.
After a system upgrade and subsequent reboot our blog failed to rebuild.
Right now I'm greeted with the following error
-----> PHP app detected
-----> Bootstrapping...
! ERROR: Failed to download minimal PHP for bootstrapping!
!
! This is most likely a temporary internal error. If the problem
! persists, make sure that you are not running a custom or forked
! version of the Heroku PHP buildpack which may need updating.
I've tried to use dokku trace on
but this does not give extra output near this error. I don't get why the error occurs, it seems as if it's just the curl command that fails. But the S3 bucket itself is available from the host machine and Dokku does not show me the actual URL it's trying to fetch.
What's the best way to find why this is failing and how do I resolve it?
php heroku
add a comment |
I'm using Dokku for over a year now, most of the programs are written in node.js. But for a Wordpress blog we use the default heroku PHP buildpack.
After a system upgrade and subsequent reboot our blog failed to rebuild.
Right now I'm greeted with the following error
-----> PHP app detected
-----> Bootstrapping...
! ERROR: Failed to download minimal PHP for bootstrapping!
!
! This is most likely a temporary internal error. If the problem
! persists, make sure that you are not running a custom or forked
! version of the Heroku PHP buildpack which may need updating.
I've tried to use dokku trace on
but this does not give extra output near this error. I don't get why the error occurs, it seems as if it's just the curl command that fails. But the S3 bucket itself is available from the host machine and Dokku does not show me the actual URL it's trying to fetch.
What's the best way to find why this is failing and how do I resolve it?
php heroku
add a comment |
I'm using Dokku for over a year now, most of the programs are written in node.js. But for a Wordpress blog we use the default heroku PHP buildpack.
After a system upgrade and subsequent reboot our blog failed to rebuild.
Right now I'm greeted with the following error
-----> PHP app detected
-----> Bootstrapping...
! ERROR: Failed to download minimal PHP for bootstrapping!
!
! This is most likely a temporary internal error. If the problem
! persists, make sure that you are not running a custom or forked
! version of the Heroku PHP buildpack which may need updating.
I've tried to use dokku trace on
but this does not give extra output near this error. I don't get why the error occurs, it seems as if it's just the curl command that fails. But the S3 bucket itself is available from the host machine and Dokku does not show me the actual URL it's trying to fetch.
What's the best way to find why this is failing and how do I resolve it?
php heroku
I'm using Dokku for over a year now, most of the programs are written in node.js. But for a Wordpress blog we use the default heroku PHP buildpack.
After a system upgrade and subsequent reboot our blog failed to rebuild.
Right now I'm greeted with the following error
-----> PHP app detected
-----> Bootstrapping...
! ERROR: Failed to download minimal PHP for bootstrapping!
!
! This is most likely a temporary internal error. If the problem
! persists, make sure that you are not running a custom or forked
! version of the Heroku PHP buildpack which may need updating.
I've tried to use dokku trace on
but this does not give extra output near this error. I don't get why the error occurs, it seems as if it's just the curl command that fails. But the S3 bucket itself is available from the host machine and Dokku does not show me the actual URL it's trying to fetch.
What's the best way to find why this is failing and how do I resolve it?
php heroku
php heroku
asked 20 hours ago
Wouter Vandenneucker
212
212
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
So after another day of tinkering the following became clear:
- After the update to the latest Ubuntu version, the file
/etc/apt/sources.list.d/dokku.list
had it's only line (referring to the dokku repository) commented. - I uncommented the line without reading properly.
After careful readying the line in the dokku.list
file read:
deb https://packagecloud.io/dokku/dokku/ubuntu/ trusty main
instead of:
deb https://packagecloud.io/dokku/dokku/ubuntu/ xenial main
or:
deb https://packagecloud.io/dokku/dokku/ubuntu/ bionic main
Presumably it failed to change after I updated from trusty to xenial. And since it wasn't up-to-date in xenial it failed to update itself when upgrading to byonic.
After fixing this the apt update
command gave me 1 package that could be upgraded: herokuish
Upgrading this package pulled the latest docker image and enabled me to rebuild the wordpress without issues.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1390418%2frebuilding-an-app-in-dokku-results-in-error-failed-to-download-minimal-php-for%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
So after another day of tinkering the following became clear:
- After the update to the latest Ubuntu version, the file
/etc/apt/sources.list.d/dokku.list
had it's only line (referring to the dokku repository) commented. - I uncommented the line without reading properly.
After careful readying the line in the dokku.list
file read:
deb https://packagecloud.io/dokku/dokku/ubuntu/ trusty main
instead of:
deb https://packagecloud.io/dokku/dokku/ubuntu/ xenial main
or:
deb https://packagecloud.io/dokku/dokku/ubuntu/ bionic main
Presumably it failed to change after I updated from trusty to xenial. And since it wasn't up-to-date in xenial it failed to update itself when upgrading to byonic.
After fixing this the apt update
command gave me 1 package that could be upgraded: herokuish
Upgrading this package pulled the latest docker image and enabled me to rebuild the wordpress without issues.
add a comment |
So after another day of tinkering the following became clear:
- After the update to the latest Ubuntu version, the file
/etc/apt/sources.list.d/dokku.list
had it's only line (referring to the dokku repository) commented. - I uncommented the line without reading properly.
After careful readying the line in the dokku.list
file read:
deb https://packagecloud.io/dokku/dokku/ubuntu/ trusty main
instead of:
deb https://packagecloud.io/dokku/dokku/ubuntu/ xenial main
or:
deb https://packagecloud.io/dokku/dokku/ubuntu/ bionic main
Presumably it failed to change after I updated from trusty to xenial. And since it wasn't up-to-date in xenial it failed to update itself when upgrading to byonic.
After fixing this the apt update
command gave me 1 package that could be upgraded: herokuish
Upgrading this package pulled the latest docker image and enabled me to rebuild the wordpress without issues.
add a comment |
So after another day of tinkering the following became clear:
- After the update to the latest Ubuntu version, the file
/etc/apt/sources.list.d/dokku.list
had it's only line (referring to the dokku repository) commented. - I uncommented the line without reading properly.
After careful readying the line in the dokku.list
file read:
deb https://packagecloud.io/dokku/dokku/ubuntu/ trusty main
instead of:
deb https://packagecloud.io/dokku/dokku/ubuntu/ xenial main
or:
deb https://packagecloud.io/dokku/dokku/ubuntu/ bionic main
Presumably it failed to change after I updated from trusty to xenial. And since it wasn't up-to-date in xenial it failed to update itself when upgrading to byonic.
After fixing this the apt update
command gave me 1 package that could be upgraded: herokuish
Upgrading this package pulled the latest docker image and enabled me to rebuild the wordpress without issues.
So after another day of tinkering the following became clear:
- After the update to the latest Ubuntu version, the file
/etc/apt/sources.list.d/dokku.list
had it's only line (referring to the dokku repository) commented. - I uncommented the line without reading properly.
After careful readying the line in the dokku.list
file read:
deb https://packagecloud.io/dokku/dokku/ubuntu/ trusty main
instead of:
deb https://packagecloud.io/dokku/dokku/ubuntu/ xenial main
or:
deb https://packagecloud.io/dokku/dokku/ubuntu/ bionic main
Presumably it failed to change after I updated from trusty to xenial. And since it wasn't up-to-date in xenial it failed to update itself when upgrading to byonic.
After fixing this the apt update
command gave me 1 package that could be upgraded: herokuish
Upgrading this package pulled the latest docker image and enabled me to rebuild the wordpress without issues.
answered 15 hours ago
Wouter Vandenneucker
212
212
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1390418%2frebuilding-an-app-in-dokku-results-in-error-failed-to-download-minimal-php-for%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown