ddev: failed build with nodejs_version:14 and webimage_extra_packages[build_essential, libnotify-bin,python]

Is there an existing issue for this?

I have searched the existing issues

Output of `ddev debug test`

Expand `ddev debug test` diagnostic information

[Output](https://gist.github.com/kazajhodo/a418a89fec49181b5b38b976de3e8bab)

Expected Behavior

Dev starts and builds as normal.

Actual Behavior

Ddev is crashing with:

executor failed running [/bin/sh -c apt-get -qq update && DEBIAN_FRONTEND=noninteractive apt-get -qq install -y -o Dpkg::Options::="--force-confold" --no-install-recommends --no-install-suggests build-essential libnotify-bin make python]: exit code: 100

Due to webimage_extra_packages definition:

webimage_extra_packages:
    - build-essential
    - libnotify-bin
    - make
    - python

If remove and ddev restart, I then run into:

executor failed running [/bin/sh -c bash /tmp/setup_node.sh >/dev/null && apt-get install -y nodejs >/dev/null]: exit code: 1

Due to this line in config.yaml.

nodejs_version: '14'

If I remove all of the above, the project loads. This is since upgrading to 1.22.1.

If I remove the troublesome lines, the container starts with node 18 as the default. Attempted integer or string, didn’t matter, also attempted array syntax vs dash syntax with webimage_extra_packages, didn’t matter.

Current documentation states that 14 may be passed as a nodejs_version.

In previous version of ddev, the nodejs_version and webimage_extra_packages worked with this configuration. I did attempt to restart the project with only ‘build-essential’ in the array, but this also failed. I didn’t try singling out the others.

If I ‘ddev nvm install 14 && ddev nvm use 14’, ‘node -v’ within the container returns 14.

If I ddev delete the project and rebuild, with the error causing mentions above within config.yaml, build fails with same errors. I expected this to be the case, but tried it anyways. Remove them and once again the project starts as expected without issue.

Steps To Reproduce

Within config.yaml, add:

nodejs_version: '14'
webimage_extra_packages:
    - build-essential
    - libnotify-bin
    - make
    - python

Ddev start. Hopefully will return the reported errors.

Either configuration definition alone, will also return errors, as described above. I had just finished running a brew upgrade, so everything should be at its latest versions for docker-compose and so on.

Anything else?

No response

About this issue

Original URL
State: closed
Created a year ago
Comments: 24 (10 by maintainers)

Most upvoted comments

Alright, well I’ll let you know if anyone else hits it. I destroyed everything, so I don’t think I’ll hit it again, haha.

I’ll have the team let me know if we hit the exact same issue. Might just be lucky me, I’d find that surprising though. We’ll find out.

Thanks for guidance and the rapid responses. Kinda over-the-top really, but obviously super helpful. As well the other information about our webimage_extra_packages includes. I took them out of our scaffold. We have a little composer installed module that pulls in ddev and adds all of our custom commands to it. Runs another version of the ddev config as well.

We’re finally all not running and maintaining our own locals. Because we finally have something fast enough to replace them.

Again, thanks.

kazajhodo on Aug 11, 2023

I should have mentioned a couple of things earlier:

You can see the full output with ddev debug refresh
You can see the full build with export DDEV_VERBOSE=true and ddev start
You can see the full set of things that are being attempted in .ddev/.webimageBuild/Dockerfile

rfay on Aug 11, 2023