On 18-02-17 21:10, Stéphane Graber wrote:
On Sat, Feb 18, 2017 at 08:33:12PM +0100, Sjoerd wrote:
On 18-02-17 20:18, Stéphane Graber wrote:
Copy between varying LXD versions seems to not have been as tested as it
should have been... We'll look into this next week and get it sorted out.
Until then, assuming your storage pool is called "default" (see "lxc storage
list"):
lxc config device set vpn root pool default
That should fix the pool issue you got.
Thanks for the quick response, but sadly I get the same error:
# lxc config device set vpn root pool default
error: No storage pool specified.
Hmm, that's more annoying than I thought it'd be...
Do you know if your container uses any profile?
yes. With the name priv, but can't edit this profile since it's in use :(
If it does, then chances are that you can fix the situation by adding
the root device to the profile.
lxc profile device add PROFILE root disk path=/ pool=default
No joy:
# lxc profile device add priv root disk path=/ pool=default
error: Cannot change root disk device of a profile if containers are
still using it.
If I try to edit it with "lxc profile edit priv" I get the same error.
I'll try to move the working container back to the other host tomorrow
and see if I then can clean
the profile up by removing the lines following "used by:".
Editing the container config doesn't work either.
Maybe moving/copying all working containers to the other host again,
start from scratch again (and checking the profiles before transferring)
and transfer back might be faster ;)
If it tells you that you already have a "disk" device in the profile,
then just add the missing pool property to it:
lxc profile device set PROFILE root pool default
Anyway thanks for your help so far...
Cheers,
Sjoerd
_______________________________________________
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
