bug(pip): subprocess.CalledProcessError: Command '('lsb_release', '-a')' returned non-zero exit status 1.

[gaocegege]

We got this issue when:

• running on Lima VM bug: bad permission in current working directory #370 (comment)
• running on low-version Docker daemon. bug: arm64 binaries are not available on PyPI #340 (comment)

[gaocegege]

It can be fixed by:

• run on 20.10.x docker (docker desktop for mac)

[gaocegege]

I haven't encountered any trouble building envd-quick-start with docker in lima on Intel Mac, so I have no idea. 😂

Originally posted by @rudeigerc in #370 (comment)

[aseaday]

It is a cross multi arch problem I had met before.
FYI:

• https://stackoverflow.com/questions/71239969/multi-arch-docker-build-python-arm64-command-lsb-release-a-returned-no
• https://itnext.io/building-multi-cpu-architecture-docker-images-for-arm-and-x86-1-the-basics-2fa97869a99b?gi=95b158eb9975

I think we could close this issue.

[gaocegege]

@aseaday I think we should support different arches and os (e.g. macOS arch64, Linux arch64) Thus maybe we should keep it open?

[aseaday]

The error from this issue's title cames from build amd64 container from arm64 host which could be called build cross (buildx). It would cause lsb_release error because of lsb_release call something from kernel or kernel in vm.

I think this case is some bug related to docker directly rather than envd. The links I mention above is enough for users discovery themselves and in most cases, they could fix it by upgrade their docker client for arm mac.

As for cross arch or multi arch support problem, we'd better open another issue.

[gaocegege]

Thanks for the explanation!

SGTM. Then I think we can close it.