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

Tried to use vagrant lxc on debian wheezy- can not boot machine :( #117

Closed
kaystrobach opened this Issue Jul 27, 2013 · 29 comments

Comments

Projects
None yet
2 participants
@kaystrobach

kaystrobach commented Jul 27, 2013

Steps to repoduce:

Install Debian Wheezy x686 64bit amd

Install vagrant 1.2.6
Install vagrant lxc with vagrant plugin install vagrant-lxc
I used the VM from:

  config.vm.provider :lxc do |lxc, override|
    # Same effect as as 'customize ["modifyvm", :id, "--memory", "1024"]' for VirtualBox
    # lxc.customize 'cgroup.memory.limit_in_bytes', '1024M'
    config.vm.box     = "lxc-wheezy-amd64-2013-05-08"
    override.vm.box_url = "http://dl.dropbox.com/u/13510779/lxc-wheezy-amd64-2013-05-08.box"
  end

vagrant up

default] Starting container...
/root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/driver/cli.rb:106:in `transition_to': Target state 'running' not reached, currently on 'stopped' (Vagrant::LXC::Driver::CLI::TargetStateNotReached)
    from /root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/driver.rb:69:in `start'
    from /root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/action/boot.rb:17:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
    from /root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/action/forward_ports.rb:14:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/builtin/set_hostname.rb:16:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
    from /root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/action/share_folders.rb:13:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/builtin/env_set.rb:19:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/builtin/provision.rb:45:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/runner.rb:61:in `block in run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/util/busy.rb:19:in `busy'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/runner.rb:61:in `run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/builtin/call.rb:51:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/builtin/call.rb:57:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/builder.rb:116:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/runner.rb:61:in `block in run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/util/busy.rb:19:in `busy'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/runner.rb:61:in `run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/machine.rb:147:in `action'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/batch_action.rb:63:in `block (2 levels) in run'

@kaystrobach

This comment has been minimized.

Show comment
Hide comment
@kaystrobach

kaystrobach Jul 27, 2013

seems to be an debian wheezy (7.0) issue
downgrading to squeeze (6.0) stops at

[default] Importing base box 'lxc-wheezy-amd64-2013-05-08' ...

kaystrobach commented Jul 27, 2013

seems to be an debian wheezy (7.0) issue
downgrading to squeeze (6.0) stops at

[default] Importing base box 'lxc-wheezy-amd64-2013-05-08' ...
@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Jul 28, 2013

Owner

@kaystrobach sorry but I've only been using the plugin on Ubuntu hosts, I do have plans to investigate how to make things work on other distros but haven't had the chance to look into it so far. If you have plans to dig into this feel free to use this issue to share your findings :)

Owner

fgrehm commented Jul 28, 2013

@kaystrobach sorry but I've only been using the plugin on Ubuntu hosts, I do have plans to investigate how to make things work on other distros but haven't had the chance to look into it so far. If you have plans to dig into this feel free to use this issue to share your findings :)

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Jul 29, 2013

Owner

@kaystrobach BTW, would u mind sending a gist with the output of running a VAGRANT_LOG=debug vagrant up --provider=lxc over there?

Owner

fgrehm commented Jul 29, 2013

@kaystrobach BTW, would u mind sending a gist with the output of running a VAGRANT_LOG=debug vagrant up --provider=lxc over there?

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Jul 29, 2013

Owner

@kaystrobach sorry for the noise. I'm closing this in favor of #121 just to keep things organized but please use this issue to share your findings / debug output :)

Owner

fgrehm commented Jul 29, 2013

@kaystrobach sorry for the noise. I'm closing this in favor of #121 just to keep things organized but please use this issue to share your findings / debug output :)

@fgrehm fgrehm closed this Jul 29, 2013

@kaystrobach

This comment has been minimized.

Show comment
Hide comment
@kaystrobach

kaystrobach Jul 29, 2013

sure, here is the dump, which version of ubuntu are you using, my provider bounds mit to either debian 6.0 with a 2.6 kernel or ubuntu 10.04 ... grrr

The vagrantfile can be obtained from github here: https://github.com/typo3-themes/Vagrant.Themes

Thanks a lot

Last login: Sat Jul 27 19:46:22 on ttys003
Kays-MacBook-Pro:~ kay$ ssh root@<hostname>
user@lvps:~# cd vagrant/
user@lvps:~/vagrant# cd Vagrant.Themes/
user@lvps:~/vagrant/Vagrant.Themes# VAGRANT_LOG=debug vagrant up --provider=lxc
 INFO global: Vagrant version: 1.2.6
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/providers/virtualbox/plugin.rb
 INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/communicators/ssh/plugin.rb
 INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/provisioners/shell/plugin.rb
 INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/provisioners/puppet/plugin.rb
 INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/provisioners/cfengine/plugin.rb
 INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/provisioners/ansible/plugin.rb
 INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/provisioners/chef/plugin.rb
 INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/hosts/opensuse/plugin.rb
 INFO manager: Registered plugin: OpenSUSE host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/hosts/bsd/plugin.rb
 INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/hosts/gentoo/plugin.rb
 INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/hosts/windows/plugin.rb
 INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/hosts/arch/plugin.rb
 INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/hosts/linux/plugin.rb
 INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/hosts/fedora/plugin.rb
 INFO manager: Registered plugin: Fedora host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/hosts/freebsd/plugin.rb
 INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/kernel_v1/plugin.rb
 INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/openbsd/plugin.rb
 INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/omnios/plugin.rb
 INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/gentoo/plugin.rb
 INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/pld/plugin.rb
 INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/arch/plugin.rb
 INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/linux/plugin.rb
 INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/debian/plugin.rb
 INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/suse/plugin.rb
 INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/fedora/plugin.rb
 INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/redhat/plugin.rb
 INFO manager: Registered plugin: RedHat guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/freebsd/plugin.rb
 INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/ubuntu/plugin.rb
 INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/solaris/plugin.rb
 INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/kernel_v2/plugin.rb
 INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/box/plugin.rb
 INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/halt/plugin.rb
 INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/init/plugin.rb
 INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/reload/plugin.rb
 INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/help/plugin.rb
 INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/ssh/plugin.rb
 INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/plugin/plugin.rb
 INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/ssh_config/plugin.rb
 INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/suspend/plugin.rb
 INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/destroy/plugin.rb
 INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/up/plugin.rb
 INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/provision/plugin.rb
 INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/resume/plugin.rb
 INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/status/plugin.rb
 INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/package/plugin.rb
 INFO manager: Registered plugin: package command
 INFO vagrant: `vagrant` invoked: ["up", "--provider=lxc"]
DEBUG vagrant: Creating Vagrant environment
 INFO environment: Environment initialized (#<Vagrant::Environment:0x000000123c8810>)
 INFO environment:   - cwd: /root/vagrant/Vagrant.Themes
 INFO environment: Home path: /root/.vagrant.d
 INFO environment: Local data path: /root/vagrant/Vagrant.Themes/.vagrant
DEBUG environment: Creating: /root/vagrant/Vagrant.Themes/.vagrant
DEBUG environment: Loading plugins from: /root/.vagrant.d/plugins.json
 INFO environment: Loading plugin from JSON: vagrant-lxc
 INFO manager: Registered plugin: Linux Containers (LXC) provider
 INFO environment: Running hook: environment_load
 INFO environment: Initializing config...
 INFO loader: Set :default = "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/config/default.rb"
DEBUG loader: Populating proc cache for "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/config/default.rb"
DEBUG loader: Load procs for pathname: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/config/default.rb
 INFO loader: Set :root = #<Pathname:/root/vagrant/Vagrant.Themes/Vagrantfile>
DEBUG loader: Populating proc cache for #<Pathname:/root/vagrant/Vagrant.Themes/Vagrantfile>
DEBUG loader: Load procs for pathname: /root/vagrant/Vagrant.Themes/Vagrantfile
 INFO loader: Loading configuration in order: [:default, :home, :root]
DEBUG loader: Loading from: default (evaluating)
DEBUG loader: Loading from: root (evaluating)
DEBUG provisioner: Provisioner defined: puppet
DEBUG provisioner: Provisioner defined: shell
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG hosts: Host path search classes: [VagrantPlugins::HostFreeBSD::Host, VagrantPlugins::HostFedora::Host, VagrantPlugins::HostOpenSUSE::Host, VagrantPlugins::HostGentoo::Host, VagrantPlugins::HostWindows::Host, VagrantPlugins::HostArch::Host, VagrantPlugins::HostLinux::Host, VagrantPlugins::HostBSD::Host]
 INFO hosts: Host class: VagrantPlugins::HostLinux::Host
 INFO runner: Running action: #<Vagrant::Action::Builder:0x0000001292c1d0>
 INFO cli: CLI: [] "up" ["--provider=lxc"]
DEBUG cli: Invoking command class: VagrantPlugins::CommandUp::Command ["--provider=lxc"]
DEBUG command: 'Up' each target VM...
DEBUG command: Getting target VMs for command. Arguments:
DEBUG command:  -- names: []
DEBUG command:  -- options: {:provider=>"lxc"}
DEBUG command: Loading all machines...
 INFO environment: Getting machine: default (lxc)
 INFO environment: Uncached load of machine.
 INFO loader: Set :vm_default = []
 INFO loader: Loading configuration in order: [:default, :home, :root, :vm_default]
DEBUG loader: Loading from: default (cache)
DEBUG loader: Loading from: root (cache)
DEBUG loader: Configuration loaded successfully, finalizing and returning
 INFO box_collection: Searching for box: lxcquantalamd6420130712 (lxc) in /root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/metadata.json
 INFO box_collection: Box found: lxcquantalamd6420130712 (lxc)
 INFO environment: Applying 1 provider overrides. Reloading config.
 INFO loader: Set :vm_default_lxcquantalamd6420130712_lxc = [["2", #<Proc:0x000000130a0718>]]
DEBUG loader: Populating proc cache for ["2", #<Proc:0x000000130a0718>]
 INFO loader: Loading configuration in order: [:default, nil, :home, :root, :vm_default, :vm_default_lxcquantalamd6420130712_lxc]
DEBUG loader: Loading from: default (cache)
DEBUG loader: Loading from: root (cache)
DEBUG loader: Loading from: vm_default_lxcquantalamd6420130712_lxc (evaluating)
DEBUG loader: Configuration loaded successfully, finalizing and returning
 INFO machine: Initializing machine: default
 INFO machine:   - Provider: Vagrant::LXC::Provider
 INFO machine:   - Box: #<Vagrant::Box:0x00000012e6cd48>
 INFO machine:   - Data dir: /root/vagrant/Vagrant.Themes/.vagrant/machines/default/lxc
DEBUG lxc: Instantiating the container for: nil
 INFO subprocess: Starting process: ["/usr/bin/sudo", "lxc-version"]
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: lxc version: 0.7.2
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
 INFO command: With machine: default (LXC (new VM))
 INFO interface: info: Bringing machine 'default' up with 'lxc' provider...
Bringing machine 'default' up with 'lxc' provider...
 INFO batch_action: Enabling parallelization by default.
 INFO batch_action: Disabling parallelization because provider doesn't support it: lxc
 INFO batch_action: Batch action will parallelize: false
 INFO batch_action: Starting action: #<Vagrant::Machine:0x0000001302a338> up {:parallel=>true, :provision_enabled=>true, :provision_types=>nil, :provider=>"lxc"}
 INFO machine: Calling action: up on provider LXC (new VM)
 INFO runner: Running action: #<Vagrant::Action::Builder:0x0000001261d7c8>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000013193cd8>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::Call:0x00000013193c88>
 INFO runner: Running action: #<Vagrant::Action::Builder:0x000000133755d8>
 INFO warden: Calling action: #<Vagrant::LXC::Action::Created:0x000000133743e0>
 INFO runner: Running action: #<Vagrant::Action::Warden:0x000000130e6a88>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::HandleBoxUrl:0x000000130e6970>
 INFO warden: Calling action: #<Vagrant::LXC::Action::HandleBoxMetadata:0x000000131932b0>
 INFO interface: info: Importing base box 'lxcquantalamd6420130712'...
[default] Importing base box 'lxcquantalamd6420130712'...
DEBUG handle_box_metadata: Validating box contents
DEBUG handle_box_metadata: Setting box options on environment
 INFO warden: Calling action: #<Vagrant::LXC::Action::Create:0x00000012fd7480>
DEBUG driver: Copying LXC template into place
DEBUG driver: Creating container...
 INFO subprocess: Starting process: ["/usr/bin/sudo", "lxc-create", "--template", "vagrant-tmp-VagrantThemes-1375105942", "--name", "VagrantThemes-1375105942", "-f", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/lxc.conf", "--", "--tarball", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/keys/vagrant.pub"]
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: Extracting amd64 ...
DEBUG subprocess: stderr: dirname: 
DEBUG subprocess: stderr: fehlender Operand
DEBUG subprocess: stderr: 
DEBUG subprocess: stderr: „dirname --help“ gibt weitere Informationen.
DEBUG subprocess: stderr: mkdir: 
DEBUG subprocess: stderr: fehlender Operand
DEBUG subprocess: stderr: 
DEBUG subprocess: stderr: „mkdir --help“ gibt weitere Informationen.
DEBUG subprocess: stdout: failed to execute template 'vagrant-tmp-VagrantThemes-1375105942'
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
ERROR warden: Error occurred: There was an error executing ["sudo", "lxc-create", "--template", "vagrant-tmp-VagrantThemes-1375105942", "--name", "VagrantThemes-1375105942", "-f", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/lxc.conf", "--", "--tarball", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/keys/vagrant.pub"]

For more information on the failure, enable detailed logging by setting
the environment variable VAGRANT_LOG to DEBUG.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: There was an error executing ["sudo", "lxc-create", "--template", "vagrant-tmp-VagrantThemes-1375105942", "--name", "VagrantThemes-1375105942", "-f", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/lxc.conf", "--", "--tarball", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/keys/vagrant.pub"]

For more information on the failure, enable detailed logging by setting
the environment variable VAGRANT_LOG to DEBUG.
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00000013193c88>
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO environment: Running hook: environment_unload
 INFO runner: Running action: #<Vagrant::Action::Builder:0x00000013029848>
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::LXC::Errors::ExecuteError: There was an error executing ["sudo", "lxc-create", "--template", "vagrant-tmp-VagrantThemes-1375105942", "--name", "VagrantThemes-1375105942", "-f", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/lxc.conf", "--", "--tarball", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/keys/vagrant.pub"]

For more information on the failure, enable detailed logging by setting
the environment variable VAGRANT_LOG to DEBUG.>
ERROR vagrant: There was an error executing ["sudo", "lxc-create", "--template", "vagrant-tmp-VagrantThemes-1375105942", "--name", "VagrantThemes-1375105942", "-f", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/lxc.conf", "--", "--tarball", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/keys/vagrant.pub"]

For more information on the failure, enable detailed logging by setting
the environment variable VAGRANT_LOG to DEBUG.
ERROR vagrant: /root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/driver/cli.rb:141:in `block in execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/util/retryable.rb:17:in `retryable'
/root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/driver/cli.rb:131:in `execute'
/root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/driver/cli.rb:113:in `run'
/root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/driver/cli.rb:61:in `create'
/root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/driver.rb:41:in `block in create'
/root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/driver.rb:126:in `import_template'
/root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/driver.rb:39:in `create'
/root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/action/create.rb:14:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
/root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/action/handle_box_metadata.rb:30:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/builtin/handle_box_url.rb:81:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/runner.rb:61:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/runner.rb:61:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/builtin/call.rb:51:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/runner.rb:61:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/runner.rb:61:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/machine.rb:147:in `action'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/batch_action.rb:63:in `block (2 levels) in run'
 INFO interface: error: There was an error executing ["sudo", "lxc-create", "--template", "vagrant-tmp-VagrantThemes-1375105942", "--name", "VagrantThemes-1375105942", "-f", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/lxc.conf", "--", "--tarball", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/keys/vagrant.pub"]

For more information on the failure, enable detailed logging by setting
the environment variable VAGRANT_LOG to DEBUG.
There was an error executing ["sudo", "lxc-create", "--template", "vagrant-tmp-VagrantThemes-1375105942", "--name", "VagrantThemes-1375105942", "-f", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/lxc.conf", "--", "--tarball", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/keys/vagrant.pub"]

For more information on the failure, enable detailed logging by setting
the environment variable VAGRANT_LOG to DEBUG.
user@lvps:~/vagrant/Vagrant.Themes# 

kaystrobach commented Jul 29, 2013

sure, here is the dump, which version of ubuntu are you using, my provider bounds mit to either debian 6.0 with a 2.6 kernel or ubuntu 10.04 ... grrr

The vagrantfile can be obtained from github here: https://github.com/typo3-themes/Vagrant.Themes

Thanks a lot

Last login: Sat Jul 27 19:46:22 on ttys003
Kays-MacBook-Pro:~ kay$ ssh root@<hostname>
user@lvps:~# cd vagrant/
user@lvps:~/vagrant# cd Vagrant.Themes/
user@lvps:~/vagrant/Vagrant.Themes# VAGRANT_LOG=debug vagrant up --provider=lxc
 INFO global: Vagrant version: 1.2.6
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/providers/virtualbox/plugin.rb
 INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/communicators/ssh/plugin.rb
 INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/provisioners/shell/plugin.rb
 INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/provisioners/puppet/plugin.rb
 INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/provisioners/cfengine/plugin.rb
 INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/provisioners/ansible/plugin.rb
 INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/provisioners/chef/plugin.rb
 INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/hosts/opensuse/plugin.rb
 INFO manager: Registered plugin: OpenSUSE host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/hosts/bsd/plugin.rb
 INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/hosts/gentoo/plugin.rb
 INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/hosts/windows/plugin.rb
 INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/hosts/arch/plugin.rb
 INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/hosts/linux/plugin.rb
 INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/hosts/fedora/plugin.rb
 INFO manager: Registered plugin: Fedora host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/hosts/freebsd/plugin.rb
 INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/kernel_v1/plugin.rb
 INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/openbsd/plugin.rb
 INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/omnios/plugin.rb
 INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/gentoo/plugin.rb
 INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/pld/plugin.rb
 INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/arch/plugin.rb
 INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/linux/plugin.rb
 INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/debian/plugin.rb
 INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/suse/plugin.rb
 INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/fedora/plugin.rb
 INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/redhat/plugin.rb
 INFO manager: Registered plugin: RedHat guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/freebsd/plugin.rb
 INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/ubuntu/plugin.rb
 INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/guests/solaris/plugin.rb
 INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/kernel_v2/plugin.rb
 INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/box/plugin.rb
 INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/halt/plugin.rb
 INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/init/plugin.rb
 INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/reload/plugin.rb
 INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/help/plugin.rb
 INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/ssh/plugin.rb
 INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/plugin/plugin.rb
 INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/ssh_config/plugin.rb
 INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/suspend/plugin.rb
 INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/destroy/plugin.rb
 INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/up/plugin.rb
 INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/provision/plugin.rb
 INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/resume/plugin.rb
 INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/status/plugin.rb
 INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/plugins/commands/package/plugin.rb
 INFO manager: Registered plugin: package command
 INFO vagrant: `vagrant` invoked: ["up", "--provider=lxc"]
DEBUG vagrant: Creating Vagrant environment
 INFO environment: Environment initialized (#<Vagrant::Environment:0x000000123c8810>)
 INFO environment:   - cwd: /root/vagrant/Vagrant.Themes
 INFO environment: Home path: /root/.vagrant.d
 INFO environment: Local data path: /root/vagrant/Vagrant.Themes/.vagrant
DEBUG environment: Creating: /root/vagrant/Vagrant.Themes/.vagrant
DEBUG environment: Loading plugins from: /root/.vagrant.d/plugins.json
 INFO environment: Loading plugin from JSON: vagrant-lxc
 INFO manager: Registered plugin: Linux Containers (LXC) provider
 INFO environment: Running hook: environment_load
 INFO environment: Initializing config...
 INFO loader: Set :default = "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/config/default.rb"
DEBUG loader: Populating proc cache for "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/config/default.rb"
DEBUG loader: Load procs for pathname: /opt/vagrant/embedded/gems/gems/vagrant-1.2.6/config/default.rb
 INFO loader: Set :root = #<Pathname:/root/vagrant/Vagrant.Themes/Vagrantfile>
DEBUG loader: Populating proc cache for #<Pathname:/root/vagrant/Vagrant.Themes/Vagrantfile>
DEBUG loader: Load procs for pathname: /root/vagrant/Vagrant.Themes/Vagrantfile
 INFO loader: Loading configuration in order: [:default, :home, :root]
DEBUG loader: Loading from: default (evaluating)
DEBUG loader: Loading from: root (evaluating)
DEBUG provisioner: Provisioner defined: puppet
DEBUG provisioner: Provisioner defined: shell
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG hosts: Host path search classes: [VagrantPlugins::HostFreeBSD::Host, VagrantPlugins::HostFedora::Host, VagrantPlugins::HostOpenSUSE::Host, VagrantPlugins::HostGentoo::Host, VagrantPlugins::HostWindows::Host, VagrantPlugins::HostArch::Host, VagrantPlugins::HostLinux::Host, VagrantPlugins::HostBSD::Host]
 INFO hosts: Host class: VagrantPlugins::HostLinux::Host
 INFO runner: Running action: #<Vagrant::Action::Builder:0x0000001292c1d0>
 INFO cli: CLI: [] "up" ["--provider=lxc"]
DEBUG cli: Invoking command class: VagrantPlugins::CommandUp::Command ["--provider=lxc"]
DEBUG command: 'Up' each target VM...
DEBUG command: Getting target VMs for command. Arguments:
DEBUG command:  -- names: []
DEBUG command:  -- options: {:provider=>"lxc"}
DEBUG command: Loading all machines...
 INFO environment: Getting machine: default (lxc)
 INFO environment: Uncached load of machine.
 INFO loader: Set :vm_default = []
 INFO loader: Loading configuration in order: [:default, :home, :root, :vm_default]
DEBUG loader: Loading from: default (cache)
DEBUG loader: Loading from: root (cache)
DEBUG loader: Configuration loaded successfully, finalizing and returning
 INFO box_collection: Searching for box: lxcquantalamd6420130712 (lxc) in /root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/metadata.json
 INFO box_collection: Box found: lxcquantalamd6420130712 (lxc)
 INFO environment: Applying 1 provider overrides. Reloading config.
 INFO loader: Set :vm_default_lxcquantalamd6420130712_lxc = [["2", #<Proc:0x000000130a0718>]]
DEBUG loader: Populating proc cache for ["2", #<Proc:0x000000130a0718>]
 INFO loader: Loading configuration in order: [:default, nil, :home, :root, :vm_default, :vm_default_lxcquantalamd6420130712_lxc]
DEBUG loader: Loading from: default (cache)
DEBUG loader: Loading from: root (cache)
DEBUG loader: Loading from: vm_default_lxcquantalamd6420130712_lxc (evaluating)
DEBUG loader: Configuration loaded successfully, finalizing and returning
 INFO machine: Initializing machine: default
 INFO machine:   - Provider: Vagrant::LXC::Provider
 INFO machine:   - Box: #<Vagrant::Box:0x00000012e6cd48>
 INFO machine:   - Data dir: /root/vagrant/Vagrant.Themes/.vagrant/machines/default/lxc
DEBUG lxc: Instantiating the container for: nil
 INFO subprocess: Starting process: ["/usr/bin/sudo", "lxc-version"]
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: lxc version: 0.7.2
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
 INFO command: With machine: default (LXC (new VM))
 INFO interface: info: Bringing machine 'default' up with 'lxc' provider...
Bringing machine 'default' up with 'lxc' provider...
 INFO batch_action: Enabling parallelization by default.
 INFO batch_action: Disabling parallelization because provider doesn't support it: lxc
 INFO batch_action: Batch action will parallelize: false
 INFO batch_action: Starting action: #<Vagrant::Machine:0x0000001302a338> up {:parallel=>true, :provision_enabled=>true, :provision_types=>nil, :provider=>"lxc"}
 INFO machine: Calling action: up on provider LXC (new VM)
 INFO runner: Running action: #<Vagrant::Action::Builder:0x0000001261d7c8>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000013193cd8>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::Call:0x00000013193c88>
 INFO runner: Running action: #<Vagrant::Action::Builder:0x000000133755d8>
 INFO warden: Calling action: #<Vagrant::LXC::Action::Created:0x000000133743e0>
 INFO runner: Running action: #<Vagrant::Action::Warden:0x000000130e6a88>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::HandleBoxUrl:0x000000130e6970>
 INFO warden: Calling action: #<Vagrant::LXC::Action::HandleBoxMetadata:0x000000131932b0>
 INFO interface: info: Importing base box 'lxcquantalamd6420130712'...
[default] Importing base box 'lxcquantalamd6420130712'...
DEBUG handle_box_metadata: Validating box contents
DEBUG handle_box_metadata: Setting box options on environment
 INFO warden: Calling action: #<Vagrant::LXC::Action::Create:0x00000012fd7480>
DEBUG driver: Copying LXC template into place
DEBUG driver: Creating container...
 INFO subprocess: Starting process: ["/usr/bin/sudo", "lxc-create", "--template", "vagrant-tmp-VagrantThemes-1375105942", "--name", "VagrantThemes-1375105942", "-f", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/lxc.conf", "--", "--tarball", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/keys/vagrant.pub"]
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: Extracting amd64 ...
DEBUG subprocess: stderr: dirname: 
DEBUG subprocess: stderr: fehlender Operand
DEBUG subprocess: stderr: 
DEBUG subprocess: stderr: „dirname --help“ gibt weitere Informationen.
DEBUG subprocess: stderr: mkdir: 
DEBUG subprocess: stderr: fehlender Operand
DEBUG subprocess: stderr: 
DEBUG subprocess: stderr: „mkdir --help“ gibt weitere Informationen.
DEBUG subprocess: stdout: failed to execute template 'vagrant-tmp-VagrantThemes-1375105942'
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
ERROR warden: Error occurred: There was an error executing ["sudo", "lxc-create", "--template", "vagrant-tmp-VagrantThemes-1375105942", "--name", "VagrantThemes-1375105942", "-f", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/lxc.conf", "--", "--tarball", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/keys/vagrant.pub"]

For more information on the failure, enable detailed logging by setting
the environment variable VAGRANT_LOG to DEBUG.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: There was an error executing ["sudo", "lxc-create", "--template", "vagrant-tmp-VagrantThemes-1375105942", "--name", "VagrantThemes-1375105942", "-f", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/lxc.conf", "--", "--tarball", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/keys/vagrant.pub"]

For more information on the failure, enable detailed logging by setting
the environment variable VAGRANT_LOG to DEBUG.
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00000013193c88>
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO environment: Running hook: environment_unload
 INFO runner: Running action: #<Vagrant::Action::Builder:0x00000013029848>
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::LXC::Errors::ExecuteError: There was an error executing ["sudo", "lxc-create", "--template", "vagrant-tmp-VagrantThemes-1375105942", "--name", "VagrantThemes-1375105942", "-f", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/lxc.conf", "--", "--tarball", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/keys/vagrant.pub"]

For more information on the failure, enable detailed logging by setting
the environment variable VAGRANT_LOG to DEBUG.>
ERROR vagrant: There was an error executing ["sudo", "lxc-create", "--template", "vagrant-tmp-VagrantThemes-1375105942", "--name", "VagrantThemes-1375105942", "-f", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/lxc.conf", "--", "--tarball", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/keys/vagrant.pub"]

For more information on the failure, enable detailed logging by setting
the environment variable VAGRANT_LOG to DEBUG.
ERROR vagrant: /root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/driver/cli.rb:141:in `block in execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/util/retryable.rb:17:in `retryable'
/root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/driver/cli.rb:131:in `execute'
/root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/driver/cli.rb:113:in `run'
/root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/driver/cli.rb:61:in `create'
/root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/driver.rb:41:in `block in create'
/root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/driver.rb:126:in `import_template'
/root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/driver.rb:39:in `create'
/root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/action/create.rb:14:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
/root/.vagrant.d/gems/gems/vagrant-lxc-0.4.0/lib/vagrant-lxc/action/handle_box_metadata.rb:30:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/builtin/handle_box_url.rb:81:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/runner.rb:61:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/runner.rb:61:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/builtin/call.rb:51:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/runner.rb:61:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/action/runner.rb:61:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/machine.rb:147:in `action'
/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/lib/vagrant/batch_action.rb:63:in `block (2 levels) in run'
 INFO interface: error: There was an error executing ["sudo", "lxc-create", "--template", "vagrant-tmp-VagrantThemes-1375105942", "--name", "VagrantThemes-1375105942", "-f", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/lxc.conf", "--", "--tarball", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/keys/vagrant.pub"]

For more information on the failure, enable detailed logging by setting
the environment variable VAGRANT_LOG to DEBUG.
There was an error executing ["sudo", "lxc-create", "--template", "vagrant-tmp-VagrantThemes-1375105942", "--name", "VagrantThemes-1375105942", "-f", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/lxc.conf", "--", "--tarball", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/keys/vagrant.pub"]

For more information on the failure, enable detailed logging by setting
the environment variable VAGRANT_LOG to DEBUG.
user@lvps:~/vagrant/Vagrant.Themes# 
@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Jul 29, 2013

Owner

@kaystrobach tks for the info :) I'm currently using Ubuntu 13.04 but I frequently run a set of sanity checks on 12.04 and 12.10 so it should work fine on those versions too

So according to the output below it seems that this is the offending line on the template:

 INFO subprocess: Starting process: ["/usr/bin/sudo", "lxc-create", "--template", "vagrant-tmp-VagrantThemes-1375105942", "--name", "VagrantThemes-1375105942", "-f", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/lxc.conf", "--", "--tarball", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/keys/vagrant.pub"]
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: Extracting amd64 ...
DEBUG subprocess: stderr: dirname: 
DEBUG subprocess: stderr: fehlender Operand
DEBUG subprocess: stderr: 
DEBUG subprocess: stderr: „dirname --help“ gibt weitere Informationen.
DEBUG subprocess: stderr: mkdir: 
DEBUG subprocess: stderr: fehlender Operand
DEBUG subprocess: stderr: 
DEBUG subprocess: stderr: „mkdir --help“ gibt weitere Informationen.
DEBUG subprocess: stdout: failed to execute template 'vagrant-tmp-VagrantThemes-1375105942'

Are you able to track down what's going on over there? You can edit the template locally and try to bring the container up again ;) If you are interested on digging this further the template is kept on ~/.vagrant.d/boxes/<BOXNAME>/lxc/lxc-template

Owner

fgrehm commented Jul 29, 2013

@kaystrobach tks for the info :) I'm currently using Ubuntu 13.04 but I frequently run a set of sanity checks on 12.04 and 12.10 so it should work fine on those versions too

So according to the output below it seems that this is the offending line on the template:

 INFO subprocess: Starting process: ["/usr/bin/sudo", "lxc-create", "--template", "vagrant-tmp-VagrantThemes-1375105942", "--name", "VagrantThemes-1375105942", "-f", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/lxc.conf", "--", "--tarball", "/root/.vagrant.d/boxes/lxcquantalamd6420130712/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/keys/vagrant.pub"]
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: Extracting amd64 ...
DEBUG subprocess: stderr: dirname: 
DEBUG subprocess: stderr: fehlender Operand
DEBUG subprocess: stderr: 
DEBUG subprocess: stderr: „dirname --help“ gibt weitere Informationen.
DEBUG subprocess: stderr: mkdir: 
DEBUG subprocess: stderr: fehlender Operand
DEBUG subprocess: stderr: 
DEBUG subprocess: stderr: „mkdir --help“ gibt weitere Informationen.
DEBUG subprocess: stdout: failed to execute template 'vagrant-tmp-VagrantThemes-1375105942'

Are you able to track down what's going on over there? You can edit the template locally and try to bring the container up again ;) If you are interested on digging this further the template is kept on ~/.vagrant.d/boxes/<BOXNAME>/lxc/lxc-template

@kaystrobach

This comment has been minimized.

Show comment
Hide comment
@kaystrobach

kaystrobach Jul 29, 2013

mhmm, i just added some debugs.

the rootfs param is empty!

extract_rootfs()
{
    tarball=$1
    arch=$2
    rootfs=$3

    echo "---------- $1 ----- $2 ---- $3 ---"

    echo "Extracting $tarball ..."
    mkdir -p $(dirname $rootfs)
    (cd `dirname $rootfs` && tar xfz $tarball)
    return 0
}

output:
---------- amd64 ----- /var/lib/lxc/VagrantThemes-1375108363/rootfs ----  ---
                                                                        $3 missing.
install_ubuntu()
{
    rootfs=$1
    release=$2
    tarball=$3
    mkdir -p /var/lock/subsys/

    echo ">>>>>> $1 "

    (
        flock -x 200
        if [ $? -ne 0 ]; then
            echo "Cache repository is busy."
            return 1
        fi

        extract_rootfs $tarball $arch $rootfs
        if [ $? -ne 0 ]; then
            echo "Failed to copy rootfs"
            return 1
        fi

        return 0

    ) 200>/var/lock/subsys/lxc

    return $?
}

But at the >>> the rootfs param is available ?! -> scary!

kaystrobach commented Jul 29, 2013

mhmm, i just added some debugs.

the rootfs param is empty!

extract_rootfs()
{
    tarball=$1
    arch=$2
    rootfs=$3

    echo "---------- $1 ----- $2 ---- $3 ---"

    echo "Extracting $tarball ..."
    mkdir -p $(dirname $rootfs)
    (cd `dirname $rootfs` && tar xfz $tarball)
    return 0
}

output:
---------- amd64 ----- /var/lib/lxc/VagrantThemes-1375108363/rootfs ----  ---
                                                                        $3 missing.
install_ubuntu()
{
    rootfs=$1
    release=$2
    tarball=$3
    mkdir -p /var/lock/subsys/

    echo ">>>>>> $1 "

    (
        flock -x 200
        if [ $? -ne 0 ]; then
            echo "Cache repository is busy."
            return 1
        fi

        extract_rootfs $tarball $arch $rootfs
        if [ $? -ne 0 ]; then
            echo "Failed to copy rootfs"
            return 1
        fi

        return 0

    ) 200>/var/lock/subsys/lxc

    return $?
}

But at the >>> the rootfs param is available ?! -> scary!

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Jul 29, 2013

Owner

@kaystrobach yup, that's pretty weird and I believe I've hit this before when trying to use the plugin on Debian hosts but wasn't able to work around =/

I think that the problem is actually a blank $tarball parameter since the parameters were "shifted" according to your debugging:

---------- amd64 ----- /var/lib/lxc/VagrantThemes-1375108363/rootfs ----  ---
  $1 = arch (should be tarball)    $2 = rootfs (should be arch)    $3 should be the rootfs

I'll try to get my hands on a wheezy VM again to see if I'm able to track it down, if you are able to find out any other info please LMK :)

Owner

fgrehm commented Jul 29, 2013

@kaystrobach yup, that's pretty weird and I believe I've hit this before when trying to use the plugin on Debian hosts but wasn't able to work around =/

I think that the problem is actually a blank $tarball parameter since the parameters were "shifted" according to your debugging:

---------- amd64 ----- /var/lib/lxc/VagrantThemes-1375108363/rootfs ----  ---
  $1 = arch (should be tarball)    $2 = rootfs (should be arch)    $3 should be the rootfs

I'll try to get my hands on a wheezy VM again to see if I'm able to track it down, if you are able to find out any other info please LMK :)

@kaystrobach

This comment has been minimized.

Show comment
Hide comment
@kaystrobach

kaystrobach Jul 29, 2013

I will try lateron

kaystrobach commented Jul 29, 2013

I will try lateron

@kaystrobach

This comment has been minimized.

Show comment
Hide comment
@kaystrobach

kaystrobach Jul 30, 2013

@fgrehm mhmm also $3 is empty - it seems, that the $tarball variable is not set on debian - scary or not?
could you try to bring the maschine up on your dev. environment?

https://github.com/typo3-themes

I really would like to use debian 6.0 and lxc, as my hoster does not provide an suitable alternative :(
I could also give you access to the maschine for a limited time (but that won't be possible via github ...)

kaystrobach commented Jul 30, 2013

@fgrehm mhmm also $3 is empty - it seems, that the $tarball variable is not set on debian - scary or not?
could you try to bring the maschine up on your dev. environment?

https://github.com/typo3-themes

I really would like to use debian 6.0 and lxc, as my hoster does not provide an suitable alternative :(
I could also give you access to the maschine for a limited time (but that won't be possible via github ...)

@kaystrobach

This comment has been minimized.

Show comment
Hide comment
@kaystrobach

kaystrobach Jul 30, 2013

if i output the params for the install function i get this:

!!!!!!!!!!!!!!!!!!!!!! --path
!!!!!!!!!!!!!!!!!!!!!! --name
!!!!!!!!!!!!!!!!!!!!!! --

changes for debugging around line 165 in lxctemplate

while true
do
    echo "!!!!!!!!!!!!!!!!!!!!!! $1"
    case "$1" in
    -h|--help)      usage $0 && exit 0;;
    -p|--path)      path=$2; shift 2;;
    -n|--name)      name=$2; shift 2;;
    -T|--tarball)   tarball=$2; shift 2;;
    -r|--release)   release=$2; shift 2;;
    -a|--arch)      arch=$2; shift 2;;
    -x|--trim)      trim_container=1; shift 1;;
    -S|--auth-key)  auth_key=$2; shift 2;;
    -d|--debug)     debug=1; shift 1;;
    --)             shift 1; break ;;
        *)              break ;;
    esac
done

so i would assume, that there is simply no $tarball set from debian. Can this variable be calculated somehow (perhaps a dumb question, but i'm relativly new to lxc vagrant, currently mostly using vagrant with fusion and vbox)

kaystrobach commented Jul 30, 2013

if i output the params for the install function i get this:

!!!!!!!!!!!!!!!!!!!!!! --path
!!!!!!!!!!!!!!!!!!!!!! --name
!!!!!!!!!!!!!!!!!!!!!! --

changes for debugging around line 165 in lxctemplate

while true
do
    echo "!!!!!!!!!!!!!!!!!!!!!! $1"
    case "$1" in
    -h|--help)      usage $0 && exit 0;;
    -p|--path)      path=$2; shift 2;;
    -n|--name)      name=$2; shift 2;;
    -T|--tarball)   tarball=$2; shift 2;;
    -r|--release)   release=$2; shift 2;;
    -a|--arch)      arch=$2; shift 2;;
    -x|--trim)      trim_container=1; shift 1;;
    -S|--auth-key)  auth_key=$2; shift 2;;
    -d|--debug)     debug=1; shift 1;;
    --)             shift 1; break ;;
        *)              break ;;
    esac
done

so i would assume, that there is simply no $tarball set from debian. Can this variable be calculated somehow (perhaps a dumb question, but i'm relativly new to lxc vagrant, currently mostly using vagrant with fusion and vbox)

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Jul 30, 2013

Owner

@kaystrobach oh man, last night I spent some time working on this and was able to boot a vagrant-lxc container on a wheezy host as you mentioned wheezy on the issue title, but I just realized that need to run it on a squeeze host :P I'll give a try on a squeeze VM later on but here's my notes for setting things up on wheezy https://gist.github.com/fgrehm/68fa349251d70dfe8470

Regarding the tarball parameter, that's something I introduced on the template, originally there is no such thing and I have no idea why Squeeze would omit that =/

Owner

fgrehm commented Jul 30, 2013

@kaystrobach oh man, last night I spent some time working on this and was able to boot a vagrant-lxc container on a wheezy host as you mentioned wheezy on the issue title, but I just realized that need to run it on a squeeze host :P I'll give a try on a squeeze VM later on but here's my notes for setting things up on wheezy https://gist.github.com/fgrehm/68fa349251d70dfe8470

Regarding the tarball parameter, that's something I introduced on the template, originally there is no such thing and I have no idea why Squeeze would omit that =/

@kaystrobach

This comment has been minimized.

Show comment
Hide comment
@kaystrobach

kaystrobach Jul 30, 2013

hello @fgrehm sry for that, i started on wheezy (illigaly upgraded my root server ...) but my hosting provider told me, that i should downgrade, as their parallels virtuozzo just provided a 2.6 kernel - HAHA

i know the guide mentioned in the gist and setup lxc that way. sadly the tarball stuff is the show stoppper - have no idea as well :(

kaystrobach commented Jul 30, 2013

hello @fgrehm sry for that, i started on wheezy (illigaly upgraded my root server ...) but my hosting provider told me, that i should downgrade, as their parallels virtuozzo just provided a 2.6 kernel - HAHA

i know the guide mentioned in the gist and setup lxc that way. sadly the tarball stuff is the show stoppper - have no idea as well :(

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Jul 30, 2013

Owner

@kaystrobach no worries :)
I'll see if I can track it down later on since I really want to see this happen, my goal for 1.0 is to have at least the documentation for setting things up on major distros (and set things up automatically from within vagrant-lxc if possible ;)

Owner

fgrehm commented Jul 30, 2013

@kaystrobach no worries :)
I'll see if I can track it down later on since I really want to see this happen, my goal for 1.0 is to have at least the documentation for setting things up on major distros (and set things up automatically from within vagrant-lxc if possible ;)

@kaystrobach

This comment has been minimized.

Show comment
Hide comment
@kaystrobach

kaystrobach Jul 30, 2013

if it helps you may get access to my maschine as mentioned before :D

kaystrobach commented Jul 30, 2013

if it helps you may get access to my maschine as mentioned before :D

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Jul 31, 2013

Owner

@kaystrobach I did some testing last night, got some bad and good news for you :P

$ lxc-version
lxc version: 0.7.2

$ lxc-create --help
usage: lxc-create -n <name> [-f configuration] [-t template] [-h]

creates a lxc system object.

Options:
name         : name of the container
configuration: lxc configuration
template     : lxc-template is an accessible template script

As you can see there is no support for TEMPLATE_OPTIONS as we have on later versions:

$ lxc-version 
lxc version: 0.9.0

$ lxc-create --help
usage: lxc-create -n NAME [-f CONFIG_FILE] [-t TEMPLATE] [FS_OPTIONS] --
         [-P lxcpath] [TEMPLATE_OPTIONS]

where FS_OPTIONS is one of:
  -B none
  -B dir [--dir rootfs_dir]
  -B lvm [--lvname LV_NAME] [--vgname VG_NAME] [--fstype FS_TYPE]
    [--fssize FS_SIZE]
  -B btrfs

Create a new container on the system.

Options:
  -n NAME            specify the name of the container
  -f CONFIG_FILE     use an existing configuration file
  -t TEMPLATE        use an accessible template script
  -B BACKING_STORE   alter the container backing store (default: none)
  --lxcpath path     specify an alternate container patch (default: /var/lib/lxc)
  --lvname LV_NAME   specify the LVM logical volume name
                      (default: container name)
  --dir ROOTFS_DIR   specify path for custom rootfs directory location
  --vgname VG_NAME   specify the LVM volume group name (default: lxc)
  --fstype FS_TYPE   specify the filesystem type (default: ext4)
  --fssize FS_SIZE   specify the filesystem size (default: 500M)

To see template-specific options, specify a template. For example:
  lxc-create -t ubuntu -h

Because we pass in the path to the rootfs tarball as a template parameter there is no way to make vagrant-lxc (on its current state and using the available boxes) to work under Deban Squeeze with 0.7.2. I also tried installing 0.8.0-rc1 from backports but ended up hitting this bug.

Now for the good news, I gave a shot at using the built in ubuntu template available on wheezy and things went just fine. So I went ahead and tweaked the vagrant-lxc config file to look like the builtin one, patched some vagrant-lxc code and changed the lxc-template to not rely on the aditional template parameters by hard coding in the path to the tarball. After bringing up the lxcbr0 bridge I was able to boot the container \o/

I've found a couple limitations and I'm not sure you'll hit them as well:

  • vagrant halt only works if forced with -f as a parameter
  • The container takes way too long to get an IP lease. By keeping another SSH connection open with the VBox VM with sudo tail -f /var/log/syslog running I noticed that it consistently takes 2 minutes for the container to be accessible. I have no idea why this is happening but I hope you won't experience that over there.

Here's a gist with the tweaks I've done to the plugin and to the templates / configs on a configured Squeeze VBox VM while I tried things out so you can reproduce over there. I hope you are able to get it to work on the machine you've been trying things as well.

Please LMK if the stuff on the gist works for you so that I can update the Wiki with the information and think about changes to vagrant-lxc as there is a lot of hacking involved :)

/cc @rcarmo

Owner

fgrehm commented Jul 31, 2013

@kaystrobach I did some testing last night, got some bad and good news for you :P

$ lxc-version
lxc version: 0.7.2

$ lxc-create --help
usage: lxc-create -n <name> [-f configuration] [-t template] [-h]

creates a lxc system object.

Options:
name         : name of the container
configuration: lxc configuration
template     : lxc-template is an accessible template script

As you can see there is no support for TEMPLATE_OPTIONS as we have on later versions:

$ lxc-version 
lxc version: 0.9.0

$ lxc-create --help
usage: lxc-create -n NAME [-f CONFIG_FILE] [-t TEMPLATE] [FS_OPTIONS] --
         [-P lxcpath] [TEMPLATE_OPTIONS]

where FS_OPTIONS is one of:
  -B none
  -B dir [--dir rootfs_dir]
  -B lvm [--lvname LV_NAME] [--vgname VG_NAME] [--fstype FS_TYPE]
    [--fssize FS_SIZE]
  -B btrfs

Create a new container on the system.

Options:
  -n NAME            specify the name of the container
  -f CONFIG_FILE     use an existing configuration file
  -t TEMPLATE        use an accessible template script
  -B BACKING_STORE   alter the container backing store (default: none)
  --lxcpath path     specify an alternate container patch (default: /var/lib/lxc)
  --lvname LV_NAME   specify the LVM logical volume name
                      (default: container name)
  --dir ROOTFS_DIR   specify path for custom rootfs directory location
  --vgname VG_NAME   specify the LVM volume group name (default: lxc)
  --fstype FS_TYPE   specify the filesystem type (default: ext4)
  --fssize FS_SIZE   specify the filesystem size (default: 500M)

To see template-specific options, specify a template. For example:
  lxc-create -t ubuntu -h

Because we pass in the path to the rootfs tarball as a template parameter there is no way to make vagrant-lxc (on its current state and using the available boxes) to work under Deban Squeeze with 0.7.2. I also tried installing 0.8.0-rc1 from backports but ended up hitting this bug.

Now for the good news, I gave a shot at using the built in ubuntu template available on wheezy and things went just fine. So I went ahead and tweaked the vagrant-lxc config file to look like the builtin one, patched some vagrant-lxc code and changed the lxc-template to not rely on the aditional template parameters by hard coding in the path to the tarball. After bringing up the lxcbr0 bridge I was able to boot the container \o/

I've found a couple limitations and I'm not sure you'll hit them as well:

  • vagrant halt only works if forced with -f as a parameter
  • The container takes way too long to get an IP lease. By keeping another SSH connection open with the VBox VM with sudo tail -f /var/log/syslog running I noticed that it consistently takes 2 minutes for the container to be accessible. I have no idea why this is happening but I hope you won't experience that over there.

Here's a gist with the tweaks I've done to the plugin and to the templates / configs on a configured Squeeze VBox VM while I tried things out so you can reproduce over there. I hope you are able to get it to work on the machine you've been trying things as well.

Please LMK if the stuff on the gist works for you so that I can update the Wiki with the information and think about changes to vagrant-lxc as there is a lot of hacking involved :)

/cc @rcarmo

@kaystrobach

This comment has been minimized.

Show comment
Hide comment
@kaystrobach

kaystrobach Aug 9, 2013

hi @fgrehm ,

seems to me, that i missed to answer you before my vacation :(
I forked your gist to get it running in every home directory https://gist.github.com/kaystrobach/faa8c22e7ac648f99250

anyway there was a problem booting the lxc box, i still assume, that this is a problem with the virtualization HE uses, as i can't mount cgroup :(

kaystrobach commented Aug 9, 2013

hi @fgrehm ,

seems to me, that i missed to answer you before my vacation :(
I forked your gist to get it running in every home directory https://gist.github.com/kaystrobach/faa8c22e7ac648f99250

anyway there was a problem booting the lxc box, i still assume, that this is a problem with the virtualization HE uses, as i can't mount cgroup :(

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Aug 9, 2013

Owner

@kaystrobach have you tried bringing the container up by hand? you can do something like lxc-start -n $(cat .vagrant/machines/MACHINE_NAME/lxc/id) to start it on the foreground and have a look at the errors when it blows up

Owner

fgrehm commented Aug 9, 2013

@kaystrobach have you tried bringing the container up by hand? you can do something like lxc-start -n $(cat .vagrant/machines/MACHINE_NAME/lxc/id) to start it on the foreground and have a look at the errors when it blows up

@kaystrobach

This comment has been minimized.

Show comment
Hide comment
@kaystrobach

kaystrobach Aug 9, 2013

Interesting lines of VAGRANT_LOG=debug vagrant up --provider=lxc

 INFO machine: Initializing machine: default
 INFO machine:   - Provider: Vagrant::LXC::Provider
 INFO machine:   - Box: #<Vagrant::Box:0x00000013c15c88>
 INFO machine:   - Data dir: /root/vagrant/Vagrant.Themes/.vagrant/machines/default/lxc

Note homedir is: /root/

INFO subprocess: Starting process: ["/usr/bin/sudo", "lxc-create", "--template", "vagrant-tmp-VagrantThemes-1376062202", "--name", "VagrantThemes-1376062202", "-f", "/root/.vagrant.d/boxes/quantal64/lxc/lxc.conf", "--", "--tarball", "/root/.vagrant.d/boxes/quantal64/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/keys/vagrant.pub"]

Now see the error message:

DEBUG subprocess: stdout: Extracting /home/vagrant/.vagrant.d/boxes/quantal64/lxc/rootfs.tar.gz ...
DEBUG subprocess: stderr: tar (child): /home/vagrant/.vagrant.d/boxes/quantal64/lxc/rootfs.tar.gz: Kann open nicht ausführen: Datei oder Verzeichnis nicht gefunden
tar (child): Error is not recoverable: exiting now

So mainly a problem with the homedirectories like in your gist :( is it possible to change that to a "~", or use the one from the INFO machine section? I do not think, that everyone is working as vagrant user :D

Thanks

kaystrobach commented Aug 9, 2013

Interesting lines of VAGRANT_LOG=debug vagrant up --provider=lxc

 INFO machine: Initializing machine: default
 INFO machine:   - Provider: Vagrant::LXC::Provider
 INFO machine:   - Box: #<Vagrant::Box:0x00000013c15c88>
 INFO machine:   - Data dir: /root/vagrant/Vagrant.Themes/.vagrant/machines/default/lxc

Note homedir is: /root/

INFO subprocess: Starting process: ["/usr/bin/sudo", "lxc-create", "--template", "vagrant-tmp-VagrantThemes-1376062202", "--name", "VagrantThemes-1376062202", "-f", "/root/.vagrant.d/boxes/quantal64/lxc/lxc.conf", "--", "--tarball", "/root/.vagrant.d/boxes/quantal64/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.2.6/keys/vagrant.pub"]

Now see the error message:

DEBUG subprocess: stdout: Extracting /home/vagrant/.vagrant.d/boxes/quantal64/lxc/rootfs.tar.gz ...
DEBUG subprocess: stderr: tar (child): /home/vagrant/.vagrant.d/boxes/quantal64/lxc/rootfs.tar.gz: Kann open nicht ausführen: Datei oder Verzeichnis nicht gefunden
tar (child): Error is not recoverable: exiting now

So mainly a problem with the homedirectories like in your gist :( is it possible to change that to a "~", or use the one from the INFO machine section? I do not think, that everyone is working as vagrant user :D

Thanks

@kaystrobach

This comment has been minimized.

Show comment
Hide comment
@kaystrobach

kaystrobach Aug 9, 2013

PS: I'm working as "/root", /root/vagrant is just a directory in the home directory of /root :D

kaystrobach commented Aug 9, 2013

PS: I'm working as "/root", /root/vagrant is just a directory in the home directory of /root :D

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Aug 9, 2013

Owner

@kaystrobach I'll give a shot at trying it out from the root user to see how it goes, I'll also reopen the issue as there is a lot of stuff going on here that I need to keep track of :P

Owner

fgrehm commented Aug 9, 2013

@kaystrobach I'll give a shot at trying it out from the root user to see how it goes, I'll also reopen the issue as there is a lot of stuff going on here that I need to keep track of :P

@fgrehm fgrehm reopened this Aug 9, 2013

@kaystrobach

This comment has been minimized.

Show comment
Hide comment
@kaystrobach

kaystrobach Aug 9, 2013

thanks for all your efforts :D let me know how i can help you ;)
Even if i'm not the ruby expert :D

kaystrobach commented Aug 9, 2013

thanks for all your efforts :D let me know how i can help you ;)
Even if i'm not the ruby expert :D

@kaystrobach

This comment has been minimized.

Show comment
Hide comment
@kaystrobach

kaystrobach Aug 14, 2013

@fgrehm do you have an amazon wishlist or a donation account on paypal?
I'd like to support you (and i'd like to have vagrant-lxc running stable on debian / ubuntu for root / whoever as well) :D

kaystrobach commented Aug 14, 2013

@fgrehm do you have an amazon wishlist or a donation account on paypal?
I'd like to support you (and i'd like to have vagrant-lxc running stable on debian / ubuntu for root / whoever as well) :D

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Aug 15, 2013

Owner

@kaystrobach tks for that :) well, I haven't got a wishlist neither a donation account, but if you are feeling especially charitable there are gittips :P

Owner

fgrehm commented Aug 15, 2013

@kaystrobach tks for that :) well, I haven't got a wishlist neither a donation account, but if you are feeling especially charitable there are gittips :P

@kaystrobach

This comment has been minimized.

Show comment
Hide comment
@kaystrobach

kaystrobach Aug 16, 2013

mhmm i prefer one time donations over weekly ones :(

kaystrobach commented Aug 16, 2013

mhmm i prefer one time donations over weekly ones :(

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Sep 28, 2013

Owner

@kaystrobach following up, were u able to get a new machine with a recent Debian version or you still need things to work on squeeze?

Owner

fgrehm commented Sep 28, 2013

@kaystrobach following up, were u able to get a new machine with a recent Debian version or you still need things to work on squeeze?

@kaystrobach

This comment has been minimized.

Show comment
Hide comment
@kaystrobach

kaystrobach Oct 1, 2013

I'm still using the old maschine, all other hosters do not offer a firewall or are TOO expensive.
I tested in a virtualized maschine and it seems to work mostly. Thanks a lot.

PS: I do use jenkins and automated vhost management now ... anyway vagrant and virtual maschines are still my favorite :D

kaystrobach commented Oct 1, 2013

I'm still using the old maschine, all other hosters do not offer a firewall or are TOO expensive.
I tested in a virtualized maschine and it seems to work mostly. Thanks a lot.

PS: I do use jenkins and automated vhost management now ... anyway vagrant and virtual maschines are still my favorite :D

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Oct 1, 2013

Owner

Cool :)
This issue has grown too big and it will take some effort to make things work on Squeeze, for now I'll close this issue but if someone is up to contribute the required changes to make it happen just raise your hand :D

Owner

fgrehm commented Oct 1, 2013

Cool :)
This issue has grown too big and it will take some effort to make things work on Squeeze, for now I'll close this issue but if someone is up to contribute the required changes to make it happen just raise your hand :D

@fgrehm fgrehm closed this Oct 1, 2013

@kaystrobach

This comment has been minimized.

Show comment
Hide comment
@kaystrobach

kaystrobach Oct 2, 2013

thanks for all your efforts

kaystrobach commented Oct 2, 2013

thanks for all your efforts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment