Cesar Talledo

Hi @EddieX64, thanks for reporting the issue and all the detailed info you provided. I was able to easily repro, but I don't have an explanation yet, other than I...

Hi @EddieX64, thanks for the reminder. I don't yet have a meaningful update, other than I am working with our main `docker buildx` expert to figure out why `/sys` is...

Suspect the problem is coming from this buildkit code, where it's not mounting sysfs in "rootless" environments, such as inside a Sysbox container: https://github.com/moby/buildkit/blob/master/util/rootless/specconv/specconv_linux.go#L15-L32

Hi @EddieX64, yes it's not a Sysbox issue per-se, but I am working with the buildx developers to see if we can make a fix there. It may take a...

@thaJeztah: I noticed the following integration test fails with this PR: ``` === Failed === FAIL: amd64.integration-cli TestDockerCLIPsSuite/TestPsListContainersBase (1.10s) docker_cli_ps_test.go:56: assertion failed: false (bool) != true (true bool): ALL: Container...

Thanks @thaJeztah and @vvoland for the feedback regarding "ordering does matter" in the container list. I've re-worked the solution to ensure the ordering is kept in the container list result,...

Thanks @vvoland and @thaJeztah. I suspect the `TestList` integration test is failing because prior tests create containers but don't always remove them (i.e., they don't always cleanup). When I run...

> I've modified the TestList test to remove any existing containers prior to doing it's thing. Let's see how that goes. Interesting: after this change, the `TestList` test now passes,...

Thanks @thaJeztah, that could be it ... I'll do some experiments to confirm.

> I have some vague recollection of Windows time precision and nanoseconds; could it be that the timestamp is rounded, and we now end up with multiple containers created in...