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?
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
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
> Output of "lxc storage list" :
> +---------+--------+-----------------------+---------+
> | NAME | DRIVER | SOURCE | USED BY |
> +---------+--------+-----------------------+---------+
> | default | zfs | data/asterix/lxd/data | 12 |
> +---------+--------+-----------------------+---------+
>
>
> The weird thing is that I can't find anything related to it in the
> /var/lib/lxd directory and beyond.
> It only seems to exist as an entry in the lxd database.
>
> Cheers,
> Sjoerd
--
Stéphane Graber
Ubuntu developer
http://www.ubuntu.com
signature.asc
Description: PGP signature
_______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
