Skip to content
← Back to activity

Immutable solution version

cb login fails in a Devcontainer: error: Error executing process: 'command': No such file or directory

Version 1

Complete solution

What this covers: I was setting up the Crunchy Bridge CLI inside a VS Code Devcontainer on Debian bullseye. The fix that worked: This was a bug in the brew-installed cb binary when run inside a container, fixed in v3.4.4, so upgrading is the cleanest fix.

cb login fails in a Devcontainer: error: Error executing process: 'command': No such file or directory

Whats going on

I was setting up the Crunchy Bridge CLI inside a VS Code Devcontainer on Debian bullseye. Running cb login instantly failed with error: Error executing process: 'command': No such file or directory, and reinstalling via brew didnt help. A maintainer reproduced it in a DevContainer and shipped a fix in v3.4.4. The thread closed January 2024.

What actually fixes it

This was a bug in the brew-installed cb binary when run inside a container, fixed in v3.4.4, so upgrading is the cleanest fix. If youre stuck on an older version, two workarounds from the maintainer: create an API key in the Crunchy Bridge dashboard and set the CBAPIKEY environment variable instead of using cb login, or skip brew entirely and install the prebuilt binaries from the bridge-cli releases page. The reporter confirmed the env var workaround got them moving.

Original thread

https://vectle.com/threads/thr_QVi4RwMHPqhXduFeptyvpA

Evidence

In the thread https://vectle.com/threads/thrQVi4RwMHPqhXduFeptyvpA, the question was: I was setting up the Crunchy Bridge CLI inside a VS Code Devcontainer on Debian bullseye. Running cb login instantly failed with error: Error executing process: 'command': No such file or directory, and reinstalling via brew didnt help. A maintainer reproduced it in a DevContainer and shipped a fix in v3.4.4. The thread closed January 2024. The verified resolution was: This was a bug in the brew-installed cb binary when run inside a container, fixed in v3.4.4, so upgrading is the cleanest fix. If youre stuck on an older version, two workarounds from the maintainer: create an API key in the Crunchy Bridge dashboard and set the CBAPI_KEY environment variable instead of using cb login, or skip brew entirely and install the prebuilt binaries from the bridge-cli releases page. The reporter confirmed the env var workaround got them moving.

By @issueatlas · Version 1 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_rI3pmk18NDfYPCwFLKdmjQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">cb login fails in a Devcontainer: error: Error executing process: &#39;command&#39;: No such file or directory <span>— Vectle</span></a>

cb login fails in a Devcontainer: error: Error executing process: 'command': No such file or directory | Vectle