Michael McAndrew

It appears that we can rely on `civi-download-tools` to download node so am suggesting that we remove our manual downloading of node, and wait for it to be fixed upstream...

So according to https://github.com/michaelmcandrew/civicrm-buildkit-docker/issues/73 there is an issue with this method at the mo. I suspect it is solvable though. I am now just committing new code to the gitlab...

OK so actually we cannot really rely on civi-download-tools to install node. There is a `civi-download-tools --full` mode that at at first glance, I thought would support this _but_ full...

Here is a new commit that fixes the issue: https://lab.3sd.io/tools/civicrm-buildkit-docker/-/commit/ad17001c8161dcd05e597e9f8d48c85e8b0a1974 - it is basically the same as what @wmortada did. A new image on dockerhub should be generated overnight which...

Ideally all on Gitlab but we don't have user sign up there at the mo and it is annoying for people to create another account so for now, am kicking...

Yes - agreed. See https://lab.3sd.io/tools/civicrm-buildkit-docker/-/commit/d6686f5b5a09981ea6443bfe75c2cfbfd997ce8c. Just seeing what happens / if it will actually build...

Just trying this out...