fix: [BUG] Devcontainer does not produce a working environment on a clean set... - #8001
Conversation
vitormattos
left a comment
There was a problem hiding this comment.
Thanks for working on this!
Changing PHP 8.2 to 8.3 fixes the current problem with Nextcloud master.
As a follow-up, we can create an issue in nextcloud-docker-development to review the image/tag naming so Dependabot can help keep the devcontainer PHP version updated in the future.
About setup.sh, I'm not sure we should make every setup error fatal because is a development environment, the developer may need the container running to investigate and fix the problem.
I would prefer to keep the setup.sh behavior unchanged in this PR and handle error reporting separately if needed.
|
Reverted the setup.sh changes so the PR only bumps the devcontainer default PHP image to 83, and checked the restored script with bash -n. |
Reference the new ghcr.io/librecodecoop/nextcloud-dev:8.3 image (published by LibreCodeCoop/nextcloud-docker-development#124) with a literal tag instead of interpolating PHP_VERSION into the image name, and add a docker ecosystem entry for /.devcontainer to dependabot.yml. Dependabot only updates version-like tags, never image names, and cannot parse interpolated references — so with the old scheme the devcontainer PHP version could only be bumped by hand (as in LibreSign#8001). Now Dependabot opens the bump PR when a new PHP version image is published. To run the devcontainer with a different PHP version, edit the image tag locally. Ref LibreCodeCoop/nextcloud-docker-development#123 Assisted-by: Claude Code:claude-fable-5 Signed-off-by: André Maia <andrefnkmm@gmail.com>
Fixes #7985
Root cause
Devcontainer defaults to PHP 8.2 and setup.sh swallows step failures
Changes