Public bug reported:
As per documentation, the `-B best` option should automatically select
the best backingstore, falling back all the way to dir.
But apparently it doesn't, at least not in artful's 2.1.0-0ubuntu1:
$ sudo lxc-create -B best --name=autopkgtest-xenial -t ubuntu -- -r xenial
lxc-create: autopkgtest-xenial: storage/btrfs.c: btrfs_create: 860
Inappropriate ioctl for device - Failed to create btrfs subvolume
"/var/lib/lxc/autopkgtest-xenial/rootfs"
lxc-create: autopkgtest-xenial: storage/zfs.c: zfs_create: 758 Failed to create
zfs dataset "zfs:lxc/autopkgtest-xenial": lxc-create: autopkgtest-xenial:
utils.c: run_command: 2326 failed to exec command
lxc-create: autopkgtest-xenial: storage/zfs.c: zfs_mount: 256 No such file or
directory - Failed to mount "lxc/autopkgtest-xenial" on
"/usr/lib/x86_64-linux-gnu/lxc"
lxc-create: autopkgtest-xenial: lxccontainer.c: create_run_template: 1294
Failed to mount rootfs
lxc-create: autopkgtest-xenial: lxccontainer.c: create_run_template: 1473
container creation template for autopkgtest-xenial failed
lxc-create: autopkgtest-xenial: storage/zfs.c: zfs_destroy: 613 Failed to
detect zfs dataset "lxc/autopkgtest-xenial": lxc-create: autopkgtest-xenial:
lxc-create: autopkgtest-xenial: lxccontainer.c: container_destroy: 2653 Error
destroying rootfs for autopkgtest-xenial
lxc-create: autopkgtest-xenial: tools/lxc_create.c: main: 326 Error creating
container autopkgtest-xenial
Moreover, it creates cruft which is hard to clean up again:
$ sudo lxc-ls -f
NAME STATE AUTOSTART GROUPS IPV4 IPV6
autopkgtest-xenial STOPPED 0 - - -
$ sudo lxc-destroy -n autopkgtest-xenial
lxc-destroy: autopkgtest-xenial: storage/zfs.c: zfs_destroy: 613 Failed to
detect zfs dataset "lxc/autopkgtest-xenial": lxc-destroy: autopkgtest-xenial:
utils.c: run_command: 2326 failed to exec command
lxc-destroy: autopkgtest-xenial: lxccontainer.c: container_destroy: 2653 Error
destroying rootfs for autopkgtest-xenial
Destroying autopkgtest-xenial failed
$ sudo ls -lR /var/lib/lxc/autopkgtest-xenial
/var/lib/lxc/autopkgtest-xenial:
total 8
-rw-r--r-- 1 root root 149 Feb 20 20:41 config
drwxr-xr-x 2 root root 4096 Feb 20 20:41 rootfs
/var/lib/lxc/autopkgtest-xenial/rootfs:
total 0
This can only be cleaned up with `sudo rm -r`.
autopkgtest-build-lxc uses this option to get performant containers out
of the box. Arguably `-B best` is a sort of "unbreak my containers"
option and should always implicitly be used, but is there something else
that I should do here?
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: lxc 2.1.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Tue Feb 20 20:38:55 2018
JournalErrors:
Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000']
failed with exit code 1: Hint: You are currently not seeing messages from other
users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
No journal files were opened due to insufficient permissions.
PackageArchitecture: all
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
lxc.net.0.type = veth
lxc.net.0.link = lxcbr0
lxc.net.0.flags = up
lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx
lxcsyslog:
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apparmor apport-bug artful
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1750654
Title:
"lxc-create -B best" fails on non-btrfs/zfs system
Status in lxc package in Ubuntu:
New
Bug description:
As per documentation, the `-B best` option should automatically select
the best backingstore, falling back all the way to dir.
But apparently it doesn't, at least not in artful's 2.1.0-0ubuntu1:
$ sudo lxc-create -B best --name=autopkgtest-xenial -t ubuntu -- -r xenial
lxc-create: autopkgtest-xenial: storage/btrfs.c: btrfs_create: 860
Inappropriate ioctl for device - Failed to create btrfs subvolume
"/var/lib/lxc/autopkgtest-xenial/rootfs"
lxc-create: autopkgtest-xenial: storage/zfs.c: zfs_create: 758 Failed to
create zfs dataset "zfs:lxc/autopkgtest-xenial": lxc-create:
autopkgtest-xenial: utils.c: run_command: 2326 failed to exec command
lxc-create: autopkgtest-xenial: storage/zfs.c: zfs_mount: 256 No such file or
directory - Failed to mount "lxc/autopkgtest-xenial" on
"/usr/lib/x86_64-linux-gnu/lxc"
lxc-create: autopkgtest-xenial: lxccontainer.c: create_run_template: 1294
Failed to mount rootfs
lxc-create: autopkgtest-xenial: lxccontainer.c: create_run_template: 1473
container creation template for autopkgtest-xenial failed
lxc-create: autopkgtest-xenial: storage/zfs.c: zfs_destroy: 613 Failed to
detect zfs dataset "lxc/autopkgtest-xenial": lxc-create: autopkgtest-xenial:
lxc-create: autopkgtest-xenial: lxccontainer.c: container_destroy: 2653 Error
destroying rootfs for autopkgtest-xenial
lxc-create: autopkgtest-xenial: tools/lxc_create.c: main: 326 Error creating
container autopkgtest-xenial
Moreover, it creates cruft which is hard to clean up again:
$ sudo lxc-ls -f
NAME STATE AUTOSTART GROUPS IPV4 IPV6
autopkgtest-xenial STOPPED 0 - - -
$ sudo lxc-destroy -n autopkgtest-xenial
lxc-destroy: autopkgtest-xenial: storage/zfs.c: zfs_destroy: 613 Failed to
detect zfs dataset "lxc/autopkgtest-xenial": lxc-destroy: autopkgtest-xenial:
utils.c: run_command: 2326 failed to exec command
lxc-destroy: autopkgtest-xenial: lxccontainer.c: container_destroy: 2653
Error destroying rootfs for autopkgtest-xenial
Destroying autopkgtest-xenial failed
$ sudo ls -lR /var/lib/lxc/autopkgtest-xenial
/var/lib/lxc/autopkgtest-xenial:
total 8
-rw-r--r-- 1 root root 149 Feb 20 20:41 config
drwxr-xr-x 2 root root 4096 Feb 20 20:41 rootfs
/var/lib/lxc/autopkgtest-xenial/rootfs:
total 0
This can only be cleaned up with `sudo rm -r`.
autopkgtest-build-lxc uses this option to get performant containers
out of the box. Arguably `-B best` is a sort of "unbreak my
containers" option and should always implicitly be used, but is there
something else that I should do here?
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: lxc 2.1.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Tue Feb 20 20:38:55 2018
JournalErrors:
Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000']
failed with exit code 1: Hint: You are currently not seeing messages from other
users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
No journal files were opened due to insufficient permissions.
PackageArchitecture: all
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
lxc.net.0.type = veth
lxc.net.0.link = lxcbr0
lxc.net.0.flags = up
lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx
lxcsyslog:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1750654/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
