DevContainer: BitBake extension does not honor bitbake.pathToBitbakeFolder and looks in wrong path

[yassibeh]

Describe the bug

The BitBake VS Code extension does not respect the bitbake.pathToBitbakeFolder setting from .devcontainer/devcontainer.json. Even though the path is correctly set and the folder structure contains a valid bitbake/bin/bitbake, the extension tries to access /home/yassine/work/mep/bin/bitbake, which doesn't exist, and throws an ENOENT error.

To Reproduce

Steps to reproduce the behavior:

1. Clone a Yocto project inside a DevContainer.
2. Inside .devcontainer/devcontainer.json, set the following:

   "bitbake.pathToBitbakeFolder": "${workspaceFolder}/bitbake"

3. Ensure the folder bitbake/bin/bitbake exists.
4. Open the project in VS Code (using Remote - Containers).
5. Watch the BitBake output during the scan.

Result:

Error: ENOENT: no such file or directory, open '/home/yassine/work/mep/bin/bitbake'

Expected behavior

The extension should follow the value of bitbake.pathToBitbakeFolder and look for bitbake/bin/bitbake inside the folder defined by that setting, not in a hardcoded /bin/bitbake at the root of the workspace.

Desktop

• OS: Ubuntu 20.04 inside container (Docker)
• Host OS: Ubuntu 24.04
• VS Code version: 1.92.2
• Extension version: 2.7.0 (yocto-project.yocto-bitbake)
• Yocto Version: kirkstone / scarthgap compatible base
• Other: using DevContainer with .devcontainer/devcontainer.json in root of the project
• Reason for using DevContainer: To enable the yocto-project.yocto-bitbake extension with my Yocto project .

Debug logs

BitBake output logs:

Executing Bitbake command with /bin/bash in /home/yassine/work/mep: ./cmd_wrapper.sh -f conf-mep/[conf-file.conf] 'which devtool bitbake || true'
/home/yassine/work/mep/scripts/devtool
/home/yassine/work/mep/oe-community/poky/bitbake/bin/bitbake
Bitbake settings are sane, eSDK mode: false
request rescanProject
start rescanProject
scanning of project is aborted: Error: ENOENT: no such file or directory, open '/home/yassine/work/mep/bin/bitbake'
BitBake scan result saved to workspace state

Additional context

• bitbake/ at project root is a valid folder (not a symlink).
• Inside bitbake/, the bin/bitbake executable is present.
• It looks like the extension ignores bitbake.pathToBitbakeFolder completely or doesn't resolve ${workspaceFolder} correctly inside DevContainers.

[deribaucourt]

Looks like the "DevContainer" compatibility is not great. We do support launching containers through bitbake.commandWrapper, but compatibility with the DevContainer extension could have some limits.
It is something we could investigate in the future, but if you need to use the existing features, please have a look at my response on #415