-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 Wrong biome build used for musl guest devcontainer on arm64 host #223
Comments
When installing biome in the guest, it also installs cli-linux-arm64 although correctly detecting musl base.
|
Maybe these need tweaking: Lines 465 to 469 in d9ca2b7
Lines 488 to 492 in d9ca2b7
Maybe this const { execSync } = require('child_process');
function isMusl() {
try {
const output = execSync('ldd --version 2>&1', { encoding: 'utf-8' });
return output.includes('musl');
} catch (error) {
return false;
}
} |
Thanks, I'll take a look. |
Should be fixed in v2.2.3 |
Fantastic thanks, seems to work |
VS Code version
1.89.1
Extension version
2.2.2
Biome version
1.7.3
Operating system
Description
When using a musl based linux dev container on a MacOS host (arm64) the wrong biome binary is used.
Steps to reproduce
Init a new project and install biome., then set up dev container.
.devcontainer/devcontainer.json
.devcontainer/Dockerfile
Biome finds
cli-linux-arm64
Expected behavior
Biome should find
cli-linux-arm64-musl
"biome.lspBin": "./node_modules/@biomejs/cli-linux-arm64-musl/biome"
makes it workDoes this issue occur when using the CLI directly?
No
Logs
The text was updated successfully, but these errors were encountered: