-
-
Notifications
You must be signed in to change notification settings - Fork 225
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
Migration fails to run due to target being empty, despite Incus being freshly installed #479
Comments
Let's check the basics:
|
Actually based on the debug output above, it looks like the issue is with |
config/list is empty. Looks like it automatically creates a btrfs storage somehow? |
Right, so your You should be able to delete all that stuff with:
At which point Incus should be back to being empty and allow the migration. |
Normally ctrl+c during the interactive |
Yep, that seems to have done it (will do the actual migration soonish™, just need to check what the snapd workaround is, it's past midnight here) |
Restarting |
Ah yeah, that'd explain that. Though |
Closes lxc#479 Signed-off-by: Stéphane Graber <[email protected]>
Sent #480 to give a slightly clearer error |
I have apparently ran To delegate container creation to users, enable/start the user service incus-user.socket I have fixed the wiki to not be ambiguous. Thanks for the PR, that'll hopefully help a bunch! |
incus info
Attempting migration fails successfully.
Would be nice if the tool said why exactly it thinks target isn't empty
Repro:
incus.socket
,incus.service
,incus-user.socket
incus admin init
but immediately exited out of it with ^Clxd-to-incus
AppArmor support has been disabled because of lack of kernel support
incus monitor --pretty
while reproducing the issue)The text was updated successfully, but these errors were encountered: