[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#951347: marked as done (cloud.debian.org: Cannot start vagrant LXC box 'debian/buster64)

Your message dated Tue, 31 Mar 2020 02:20:10 -0500
with message-id <11347173.oVUQ2KUMBC@rgb>
and subject line 
has caused the Debian Bug report #951347,
regarding cloud.debian.org: Cannot start vagrant LXC box 'debian/buster64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
951347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951347
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cloud.debian.org
Severity: normal

Dear Maintainer,

I cannot start a vagrant LXC-box for 'debian/buster64', but succeed to
start the 'debian/stretch64' box. The error message leads me to believe
there is something wrong in the LXC config of the buster box.

Vagrant box: debian/buster64 (version 10.1.0)

I'm trying to start a vagrant LXC-box with this config:
-----
Vagrant.configure("2") do |config|
  config.vm.box = "debian/buster64"
end
-----

Trying to start the vagrant box fails like this:
-----
$ VAGRANT_LOG=DEBUG vagrant up --provider=lxc
[...]
There was an error executing ["sudo", "/usr/bin/env", "lxc-start", "-d", "--name", "test-buster_default_1581713879231_84397"]
[...]
-----

Manually trying to start the LXC container fails like this:
-----
$ sudo lxc-start -F --name test-buster_default_1581713879231_84397
lxc-start: test-buster_default_1581713879231_84397: storage/dir.c: dir_mount: 198 No such file or directory - Failed to mount "/var/lib/lxc/buster-base/rootfs" on "/usr/lib/lxc/rootfs"
  lxc-start: test-buster_default_1581713879231_84397: conf.c: lxc_mount_rootfs: 1351 Failed to mount rootfs "/var/lib/lxc/buster-base/rootfs" onto "/usr/lib/lxc/rootfs" with options "(null)"
      lxc-start: test-buster_default_1581713879231_84397: conf.c: lxc_setup_rootfs_prepare_root: 3447 Failed to setup rootfs for
    lxc-start: test-buster_default_1581713879231_84397: conf.c: lxc_setup: 3550 Failed to setup rootfs
[...]
-----

I don't have a folder "/var/lib/lxc/buster-base" that is mentioned in
the error message.
The corresponding LXC config option is not present for the stretch box,
but only for the buster box:
-----
$ diff ~/.vagrant.d/boxes/debian-VAGRANTSLASH-stretch64/9.1.0/lxc/lxc-config ~/.vagrant.d/boxes/debian-VAGRANTSLASH-buster64/10.1.0/lxc/lxc-config  
[...]
9a10,13
> lxc.net.0.type = empty
> lxc.apparmor.profile = generated
> lxc.apparmor.allow_nesting = 1
> lxc.rootfs.path = dir:/var/lib/lxc/buster-base/rootfs
16c20
< lxc.uts.name = stretch-base
---
> lxc.uts.name = buster-base
[...]
-----


Is this 'lxc.rootfs.path' pointing to '/var/lib/lxc/buster-base' expected to be in the config?

Kind regards
Reto 



-- System Information:
Debian Release: 10.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.5.3-arch1-1 (SMP w/12 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

--- End Message ---
--- Begin Message --- 
The images have been removed from Vagrant Cloud for now.

--- End Message ---
Reply to: