-
Notifications
You must be signed in to change notification settings - Fork 624
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
nerdctl rename broken (with --network host
, none
)
#3341
Labels
bug
Something isn't working
Comments
AkihiroSuda
added
bug
Something isn't working
and removed
kind/unconfirmed-bug-claim
Unconfirmed bug claim
labels
Aug 22, 2024
Debugging notes:
|
In summary, when network=host, if we are to mimic docker behavior:
I find the exception on number 2 to be ridiculous, and would rather treat it as a bug on Docker side rather than implementing it. |
apostasie
changed the title
nerdctl rename broken (with
nerdctl rename broken (with Aug 22, 2024
--network host
)--network host
, none
)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Futhermore, this will leave the system in a broken state, where the destination name is locked.
This is likely related to #2613 which I was debugging before hitting this.
Steps to reproduce the issue
na
Describe the results you received and expected
na
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: