Rm: command not found

My site name is ekojargon.netlify.app.
The site was built properly without much change until 12 hours ago, but now it fails with strange warnings like rm: command not found.

Here is the log

11:51:44 PM: build-image version: c0621868af5001023389eeaa9dbfbbaf313f67e2 (focal)
11:51:44 PM: buildbot version: c0621868af5001023389eeaa9dbfbbaf313f67e2
11:51:44 PM: Fetching cached dependencies
11:51:44 PM: Starting to download cache of 592.7MB
11:51:49 PM: Finished downloading cache in 4.097s
11:51:49 PM: Starting to extract cache
11:51:51 PM: Finished extracting cache in 2.053s
11:51:51 PM: Finished fetching cache in 6.219s
11:51:51 PM: Starting to prepare the repo for build
11:51:51 PM: Preparing Git Reference refs/heads/main
11:51:52 PM: Parsing package.json dependencies
11:51:53 PM: Starting to install dependencies
11:51:54 PM: Downloading and installing node v18.7.0...
11:51:54 PM: Downloading https://nodejs.org/dist/v18.7.0/node-v18.7.0-linux-x64.tar.xz...
11:51:54 PM: Computing checksum with sha256sum
11:51:55 PM: Checksums matched!
11:51:57 PM: Now using node v18.7.0 (npm v8.15.0)
11:51:57 PM: Enabling Node.js Corepack
11:51:57 PM: Started restoring cached build plugins
11:51:57 PM: Finished restoring cached build plugins
11:51:57 PM: Started restoring cached corepack dependencies
11:51:57 PM: Finished restoring cached corepack dependencies
11:51:57 PM: Started restoring cached yarn cache
11:51:57 PM: Finished restoring cached yarn cache
11:51:57 PM: No yarn workspaces detected
11:51:57 PM: Started restoring cached node modules
11:51:57 PM: Finished restoring cached node modules
11:51:58 PM: Installing npm packages using Yarn version 3.2.2
11:51:58 PM: ➤ YN0050: The cache-folder option has been deprecated; use rc settings instead
11:51:58 PM: ➤ YN0000: ┌ Resolution step
11:51:58 PM: ➤ YN0002: │ @firebase/analytics-compat@npm:0.2.1 [6533b] doesn't provide @firebase/app (p7af35), requested by @firebase/analytics➤ YN0002: │ @firebase/app-check-compat@npm:0.3.1 [6533b] doesn't provide @firebase/app (p146d7), requested by @firebase/app-check➤ YN0002: │ @firebase/auth-compat@npm:0.3.1 [6533b] doesn't provide @firebase/app (p2a9a1), requested by @firebase/auth➤ YN0002: │ @firebase/auth-compat@npm:0.3.1 [6533b] doesn't provide @firebase/app-types (pfbc6d), requested by @firebase/auth-types➤ YN0002: │ @firebase/firestore-compat@npm:0.3.1 [6533b] doesn't provide @firebase/app (p807d3), requested by @firebase/firestore➤ YN0002: │ @firebase/firestore-compat@npm:0.3.1 [6533b] doesn't provide @firebase/app-types (pac12d), requested by @firebase/firestore-types➤ YN0002: │ @firebase/functions-compat@npm:0.3.1 [6533b] doesn't provide @firebase/app (p2e82e), requested by @firebase/functions➤ YN0002: │ @firebase/installations-compat@npm:0.2.1 [6533b] doesn't provide @firebase/app-types (p77438), requested by @firebase/installations-types➤ YN0002: │ @firebase/messaging-compat@npm:0.2.1 [6533b] doesn't provide @firebase/app (p3d41f), requested by @firebase/messaging➤ YN0002: │ @firebase/performance-compat@npm:0.2.1 [6533b] doesn't provide @firebase/app (p733d4), requested by @firebase/performance➤ YN0002: │ @firebase/remote-config-compat@npm:0.2.1 [6533b] doesn't provide @firebase/app (p32e5b), requested by @firebase/remote-config➤ YN0002: │ @firebase/storage-compat@npm:0.2.1 [6533b] doesn't provide @firebase/app (pd1fdd), requested by @firebase/storage➤ YN0002: │ @firebase/storage-compat@npm:0.2.1 [6533b] doesn't provide @firebase/app-types (p0b686), requested by @firebase/storage-types➤ YN0060: │ eko@workspace:. provides react (pf1ee5) with version 18.2.0, which doesn't satisfy what react-firebaseui requests➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
11:51:58 PM: ➤ YN0000: └ Completed
11:51:58 PM: ➤ YN0000: ┌ Fetch step
11:52:02 PM: ➤ YN0013: │ 362 packages were already cached, one had to be fetched (esbuild-linux-64@npm:0.14.54)
11:52:02 PM: ➤ YN0019: │ 4 packages appeared to be unused and were removed
11:52:02 PM: ➤ YN0000: └ Completed in 3s 824ms
11:52:02 PM: ➤ YN0000: ┌ Link step
11:52:07 PM: ➤ YN0007: │ rescript@npm:10.1.1 must be built because it never has been before or the last one failed
11:52:07 PM: ➤ YN0007: │ protobufjs@npm:6.11.3 must be built because it never has been before or the last one failed
11:52:07 PM: ➤ YN0007: │ esbuild@npm:0.14.54 must be built because it never has been before or the last one failed
11:52:07 PM: ➤ YN0007: │ protobufjs@npm:7.0.0 must be built because it never has been before or the last one failed
11:52:07 PM: ➤ YN0000: │ rescript@npm:10.1.1 STDOUT ninja binary is already cached and installed:  /opt/build/repo/node_modules/rescript/linux/ninja.exe
11:52:07 PM: ➤ YN0000: │ rescript@npm:10.1.1 STDOUT checkoutput: ReScript 10.1.1
11:52:07 PM: ➤ YN0000: │ rescript@npm:10.1.1 STDOUT  ocaml version ReScript
11:52:07 PM: ➤ YN0000: │ rescript@npm:10.1.1 STDOUT Prebuilt compiler works good
11:52:07 PM: ➤ YN0000: └ Completed in 5s 563ms
11:52:07 PM: ➤ YN0000: Done with warnings in 9s 507ms
11:52:07 PM: npm packages installed using Yarn
11:52:08 PM: Started restoring cached go cache
11:52:08 PM: /opt/build-bin/install: line 894: rm: command not found
11:52:08 PM: /opt/build-bin/install: line 896: dirname: command not found
11:52:08 PM: /opt/build-bin/install: line 896: mkdir: command not found
11:52:08 PM: /opt/build-bin/install: line 897: mv: command not found
11:52:08 PM: Finished restoring cached go cache
11:52:08 PM: Failed during stage 'Install dependencies': dependency_installation script returned non-zero exit code: 1
11:52:08 PM: /opt/build-bin/install: line 1033: gimme: command not found
11:52:08 PM: Failed to resolve Go version '1.19.5'
11:52:08 PM: Build was terminated: dependency_installation script returned non-zero exit code: 1
11:52:08 PM: Failing build: Failed to install dependencies
11:52:08 PM: Finished processing build request in 23.987s

Manually building and deploying via the netlify cli works fine btw

I’ve also hit this issue today, perhaps a misconfiguration on netlify’s end?

I have no idea. This really put me in to a misfortunate situation, and I really hope they fix this or just roll back what they did.

Hi @Zeta611 and @DanCodes we had an incident earlier and rolled back a change. i’m curious if you are still experiencing this?

It works like charm now :tada:

great thanks for confirming!