-
Notifications
You must be signed in to change notification settings - Fork 31
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
RFE: Support for moving LXC containers #5
Comments
Nobody has LXC in PVE, right? |
What does "nobody has LXC in PVE, right?" mean? It is ? Whenever possible we prefer to use LXC over KVM, simply because it's so much more efficient. The original comment is from 2017, which is 4 years ago, so has anything changed? |
There are certainly valid use cases for LXC. But it does not fit in our PVE/VM workflow nor security model. Perhaps I should've written "nobody at OSSO". |
Ah, yes, that makes more sense :-)
…On Wed, 10 Nov 2021 at 11:50, Walter Doekes ***@***.***> wrote:
There are certainly valid use cases for LXC. But it does not fit in our
PVE/VM workflow nor security model.
Perhaps I should've written "nobody at OSSO".
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABEZPJ4CWHHFZ3GVA6YRTEDULI57NANCNFSM4C4XJGXA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
[edited by wdoekes]
Moving LXC containers is PARTIALLY implemented:
8fc9e94
Right now we cannot:
The text was updated successfully, but these errors were encountered: