ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref b3885d73-93eb-42e5-a3f9-fd284603e5ac::r95xgp99ofxmf5cbb2x992vz4: “/scripts/copy-node-modules.sh”: not found
Error: Command failed with status 1: docker buildx build --tag=openedx-dev:18.1.3 --output=type=docker --target=development --build-arg=APP_USER_ID=1000 --cache-from=type=registry,ref=openedx-dev:18.1.3-cache --build-context=edx-platform=/home/pqdinh/.local/share/tutor/edx-platform /home/pqdinh/.local/share/tutor/env/build/openedx
==================================================
As you are not running this platform in production, we automatically set the following configuration values:
LMS_HOST = local.edly.io
CMS_HOST = studio.local.edly.io
ENABLE_HTTPS = False
Your platform name/title [Al Nafi]
Your public contact email address [contact@local.edly.io]
The default language code for the platform [en]
Configuration saved to /home/devapi/.local/share/tutor/config.yml
Environment generated in /home/devapi/.local/share/tutor/env
I am also encountering this on using both Tutor 18.1.3 and 18.1.4 released last week. I did not have this issue when I first upgraded to 18.1.3 about two weeks ago, but when I tried rebuilding my environment today this started happening.
I have tried running docker system prune -a and docker builder prune -a with no luck getting past this step again.
It does not appear any of the mounts in this line from the dockerfile are working as expected
While troubleshooting I attempted to split the npm clean-install --no-audit --registry=$NPM_REGISTRY into its own step, but clean-install fails due to package-lock.json not existing either.
In case it helps others, we realized that even after we upgraded to redwood we had forgotten to set the tutor config values for EDX_PLATFORM_VERSION and DOCKER_IMAGE_OPENEDX. I believe that updating those values to align with redwood resolved the errors @emartus had reported. The copy-node-modules.sh file did not exist in Palm.4 which we were upgrading from. So as long as we were using that docker image, the file was not found. It was not an issuing with the mounting mechanism itself.