Installing the #vscode #Python (or Pylance) extension in a #devcontainer will crash the remote extension host without any useful log message if my #colima container is on `aarch64` (a.k.a `arch: host` in colima config). Switched to `x86_64`, and the problem seems to have resolved.
Glad I noticed the architecture and guessed about the fix. Couldn’t find any useful info from the logs. I did find this after resolving it myself: https://github.com/microsoft/vscode-python/issues/8758#issuecomment-558353708
Maybe this will help you…
#vscode #python #devcontainer #colima #yakshave
Spent WAY too much time getting #GitHub compatible #VSCode devcontainers working on my M2 MBP, using Lima + colima for Docker approximation.
Couldn’t write to workspace q9-mounted files (VM UID differed from the mounted files which had the UID of my host/laptop’s user).
Eventual solution:
- install lima from the distribution packages instead of Nix
- vmType: vz + images + mountType: virtiofs in Lima config
- colima start --arch aarch64 --vm-type=vz
Bonus: goodbye to qemu.
#github #vscode #devops #yakshave