-
Notifications
You must be signed in to change notification settings - Fork 601
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
Windows failure on pull: UtilityVM: Incorrect function.: unknown
#3524
Labels
kind/unconfirmed-bug-claim
Unconfirmed bug claim
Comments
@AkihiroSuda this is clearly endemic and is happening very often (on the tests that do NOT retry). I will keep manually marking the tests as flaky (for Windows only), but windows folks might want to have a look at this given how often it happens.
|
apostasie
added a commit
to apostasie/nerdctl
that referenced
this issue
Oct 17, 2024
- containerd#3512 is likely fixed, so, deflaking test - a couple of other circumstances failed the build (one of them with Docker) - commenting in-line - marking another instance of containerd#3524 Signed-off-by: apostasie <[email protected]>
apostasie
added a commit
to apostasie/nerdctl
that referenced
this issue
Oct 17, 2024
- containerd#3512 is likely fixed, so, deflaking test - a couple of other circumstances failed the build (one of them with Docker) - commenting in-line - marking another instance of containerd#3524 Signed-off-by: apostasie <[email protected]>
Hi @apostasie Will look into this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
On occasions, windows nerdctl pull will fail with
UtilityVM: Incorrect function.: unknown
Windows people, do you have a clue what that means / why it happens?
@sondavidb @jsturtevant @TinaMor
Steps to reproduce the issue
Seen on CI.
Describe the results you received and expected
What version of nerdctl are you using?
main
Are you using a variant of nerdctl? (e.g., Rancher Desktop)
None
Host information
No response
The text was updated successfully, but these errors were encountered: