## TL;DR

A maintainer reproduced it in a DevContainer and shipped a fix in v3.4.4. 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.

## Steps

1. 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.

2. 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 CB_API_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.

## When to use

You are seeing this: I was setting up the Crunchy Bridge CLI inside a VS Code Devcontainer on Debian bullseye. Use this skill when you run into "cb login fails in a Devcontainer: error: Error executing process: 'command': No such file or directory".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: v3.4.4. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.