Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[5.0.6] BuildpackCompileFailed - App staging failed in the buildpack compile phase

Aperta
#1,291 0 commenti 3 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
php
Ambito
build-system

Direzione di ricerca

Inizia da manifest.yml e .bp-config/options.json, quindi ispeziona la fase Compile dell’estensione del PHP buildpack, in particolare l’estensione sessions e il caricamento di php.ini mostrato nel log. Riproduci il problema con cf push usando buildpack 5.0.6 e conferma che lo staging venga completato senza l’errore relativo alla mancanza di php/etc/php.ini.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

I try to push a Symfony app (cf push ok with buildpack 4.6.28) with new buildpack 5.0.6
I have only changed buildpack version in manifest.yml

  • Use a mariadb service
  • Use a Redis service

What version of Cloud Foundry and CF CLI are you using? (i.e. What is the output of running cf curl /v2/info && cf version?

cf curl /v2/info

{
  "name": "...",
  "build": "v53.8.0",
  "support": "",
  "version": 53,
  "description": "",
  "authorization_endpoint": "...",
  "token_endpoint": "...",
  "min_cli_version": null,
  "min_recommended_cli_version": null,
  "app_ssh_endpoint": "...",
  "app_ssh_host_key_fingerprint": "...",
  "app_ssh_oauth_client": "...",
  "doppler_logging_endpoint": "...",
  "api_version": "2.272.0",
  "osbapi_version": "2.15",
  "routing_endpoint": "...",
  "user": "..."
}

cf version: Testé avec 7.5.0+0ad1d63.2022-06-04 and 8.18.3+83ce51d.2026-04-16

What version of the buildpack you are using? 5.0.6

If you were attempting to accomplish a task, what was it you were attempting to do?

cf push

What did you expect to happen?

Instances starting... and app deployed

What was the actual behavior?

BuildpackCompileFailed - App staging failed in the buildpack compile phase
FAILED

Please confirm where necessary:

  • I have included a log output
  • My log includes an error message
  • I have included steps for reproduction

Logs

Running with gitlab-runner 18.11.3 (ad1797b3)
[...]
$ cf --version
cf version 7.5.0+0ad1d63.2022-06-04
Authenticating...
OK
Targeted org [...]
Targeted space [...]
API endpoint:   [...]
API version:    3.207.0
user:           [...]
org:            [...]
space:          [...]
[...]
Downloading app package...
Downloading build artifacts cache...
Downloaded app package (3.9M)
Downloaded build artifacts cache (55.7M)
-----> Php Buildpack version 5.0.6
**WARNING** buildpack version changed from 4.6.28 to 5.0.6
-----> Supplying PHP
Loading user configuration from .bp-config/options.json
Running extension Configure phase
-----> Composer requires PHP 8.3.*
Selected PHP version: 8.3.30
Installing PHP 8.3.30
-----> Installing php 8.3.30
Copy [[...]/php_8.3.30_linux_x64_cflinuxfs4_bac0bfc1.tgz]
Applying user PHP configuration overrides
Enabling fpm.d config includes
Web server: httpd
Installing HTTPD 2.4.66
-----> Installing httpd 2.4.66
Copy [[...]/httpd_2.4.66_linux_x64_cflinuxfs4_f5966450.tgz]
Applying user httpd configuration overrides
HTTPD installed successfully
Running extension Compile phase
**ERROR** Extension compilation failed: extension sessions compile failed: failed to load PHP config: failed to load php.ini: failed to read config file php/etc/php.ini: open php/etc/php.ini: no such file or directory
Failed to compile droplet: Failed to run all supply scripts: exit status 14
Exit status 223
[...]
BuildpackCompileFailed - App staging failed in the buildpack compile phase
FAILED

Lingua principale
Go
Stelle
141
Fork
345
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cloudfoundry/php-buildpack

Tutte le issue di cloudfoundry/php-buildpack

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.