I can run the resulting Laravel app image generating with the buildpacks on the Jammy stack.
Current Behavior
When running docker run --rm -p 8080:8080 --env PORT=8080 jammy-laravel on my app image, it fails when I curl the application:
The stream or file "/workspace/storage/logs/laravel.log" could not be opened in append mode: Failed to open stream: Permission denied
The exception occurred while attempting to log: The stream or file "/workspace/storage/logs/laravel.log" could not be opened in append mode: Failed to open stream: Permission denied
...
Run app: docker run --rm -p 8080:8080 --env PORT=8080 jammy-laravel
curl localhost:8080
Motivations
Building and reaching a Laravel app with the same steps works on Bionic, but fails on Jammy. Now that we support Jammy Jellyfish with the PHP buildpack, this experience should work.
Expected Behavior
I can run the resulting Laravel app image generating with the buildpacks on the Jammy stack.
Current Behavior
When running
docker run --rm -p 8080:8080 --env PORT=8080 jammy-laravel
on my app image, it fails when I curl the application:Possible Solution
This may be resolved by https://github.com/paketo-buildpacks/composer-install/issues/46, but the issue is that we are trying to write to
/workspace
at run-time which is not allowed due to https://github.com/paketo-buildpacks/rfcs/issues/188. This may not be fixable at all without a workaround, since PHP wants to stream logsSteps to Reproduce
composer create-project laravel/laravel ./example-laravel-app
), add extensions (fileinfo, curl, openssl) to.php.ini.d/custom.ini
docker run --rm -p 8080:8080 --env PORT=8080 jammy-laravel
curl localhost:8080
Motivations
Building and reaching a Laravel app with the same steps works on Bionic, but fails on Jammy. Now that we support Jammy Jellyfish with the PHP buildpack, this experience should work.