Skip to content

WSL machine fails to boot when LIMA_CIDATA_UID=1000 #5089

@arixmkii

Description

@arixmkii

Description

There is code which reads UID using id tool on Windows

idu, err := call(ctx, []string{"id", "-u"})
, which normally maps to cygwin/msys2 version of the utility, which in turn outputs some number outside of regular Linux user range. If id utility is missing in path, then fallback takes place and sets uid to 1000
fallbackUid = 1000
and WSL machine fails to boot.

This is a regression in 2.1.2 and was working for 2.1.1 (I haven't rechecked 2.1.1 now, but it was working around time the release was cut) - machine was able to boot when uid/gid were 1000/1000.

I believe I found that it failed at least once with 2.1.1 and additional detail would be that it started with WSL 2.7.3. So it might be a regression caused by WSL version bump.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions