Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
this is the one I used to create my chroot which is used to create the vagrant base box.
Fabio Rehm
@fgrehm
cool, I'll open up an issue to have a look into that
Jens Kleikamp
@jensk
great!
oh nice, now I see what you mentioned above https://github.com/lxc/lxc/blob/master/templates/lxc-gentoo.in
"Widely inspired from lxc-gentoo script" with some goodies. I will try that next time.
Fabio Rehm
@fgrehm
if you run 'sudo lxc-create -n bla -t download' on ubuntu trusty you'll be presented with a list of pre packaged containers to use
gentoo is there ;)
Jens Kleikamp
@jensk
uii nice command!
I checked the history. the gentoo template seems just a few months old
lxc develops so nicely
i use some words too often :D
my english is so horrible
Fabio Rehm
@fgrehm
you're fine, I'm not a native english speaker as well and I can understand you :smile:
Michael L.
@necrose99
/usr/lib64/ruby/site_ruby/1.9.1/rubygems/dependency.rb:298:in `to_specs': Could not find 'net-ssh' (< 2.8.0, >= 2.6.6) - did find: [net-ssh-2.9.0] (Gem::LoadError)
it might be a gentoo error , libs are feteched
jensk yeah lxc has a template made from lxc-gentoo
Fabio Rehm
@fgrehm
@necrose99 sorry but where's that error coming from?
Michael L.
@necrose99
vagrant plugin install vagrant-lxc
vagrant share
seems anything
hear goes the 6 line or so
/usr/lib64/ruby/site_ruby/1.9.1/rubygems/dependency.rb:298:in to_specs': Could not find 'net-ssh' (< 2.8.0, >= 2.6.6) - did find: [net-ssh-2.9.0] (Gem::LoadError) from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/specification.rb:1295:inblock in activate_dependencies'
from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/specification.rb:1284:in each' from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/specification.rb:1284:inactivate_dependencies'
from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/specification.rb:1266:in activate' from /usr/lib64/ruby/site_ruby/1.9.1/rubygems.rb:196:inrescue in try_activate'
from /usr/lib64/ruby/site_ruby/1.9.1/rubygems.rb:193:in try_activate' from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:132:inrescue in require'
from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:144:in require' from /usr/lib64/ruby/gems/1.9.1/gems/vagrant-1.4.3/bin/vagrant:27:in<top (required)>'
from /usr/bin/vagrant:8:in load' from /usr/bin/vagrant:8:in<main>'
Fabio Rehm
@fgrehm
@necrose99 weird, how did you install vagrant?
Michael L.
@necrose99
equo
sabayon entropy
mike-ltpc mike # equo search vagrant
╠ @@ Searching...
╠ @@ Package: app-emulation/vagrant-1.4.3-r1 branch: 5, [sabayonlinux.org]
╠ Available: version: 1.4.3-r1 ~ tag: NoTag ~ revision: 0
╠ Installed: version: 1.4.3-r1 ~ tag: NoTag ~ revision: 0
╠ Slot: 0
╠ Homepage: http://vagrantup.com/
╠ Description: A tool for building and distributing
╠ virtual machines using VirtualBox
╠ License: MIT
╠ Keywords: vagrant
╠ Found: 1 entry
bah no wonder sabayons bin for this is fing stale
sabayon Linux its a gentoo architype just
Fabio Rehm
@fgrehm
it might be that you are using an old vagrant version
latest is 1.6.something
Mikhail Zholobov
@legal90
@fgrehm Hi, Fabio! At first, thanks a lot for 'vagrant-lxc'! I'm maintainer of vagrant-parallels plugin and currently we have a weakly
unit test's in our provider. Please, may we use specs from 'vagrant-lxc' as an example/skeleton to write our tests in Parallels provider?
Fabio Rehm
@fgrehm
@legal90 sure! just keep in mind that most of the tests we have in place comes from the early days of the plugin which dates from over a year and a half ago :P
Mikhail Zholobov
@legal90
OK, thank you!
Jens Kleikamp
@jensk
anyone tried the plugin on the latest ubuntu release 14.10? :)
Jens Kleikamp
@jensk
seems lxc-attach requires /sbin/ip but this was never installed on my base boxes before
I mean lxc-attach from lxc-1.1
and of course apparmor prevent me from doing anything with vagrant-lxc
lxc.aa_profile = unconfined otherwise no box starts
Jens Kleikamp
@jensk
This message was deleted
This message was deleted
Fabio Rehm
@fgrehm
that sucks :(
I haven't looked at the new stuff from latest lxc yet
but requiring unconfined profile to be enabled sounds very weird to me
Jens Kleikamp
@jensk
yeah kinda :worried:
in the end I think both issues I had to tackle are not related to vagrant-lxc. ubuntu/apparmor crap and lxc is one version higher than recommended. so i ride the bleeding edge :fire: :smile:
maybe what vagrant-lxc could do if possible is to check for the provider version. if running on 1.1 it could stop with a notice that it isn´t supported yet
Jens Kleikamp
@jensk
ok. what I wrote doesn´t sound legit. i made my basebox work on 14.10 (lxc 1.1)
I did install iproute2 package and changed the lxc config aa_profile = unconfined. This is a gentoo 64bit basebox.
Geiger Peter
@ggrptr
I tried to install it on ubuntu 14.10 (its work on 14.04 for me), i installed lxc, lxc-templates, vagrant (1.4.3) with apt, and then typed vagrant plugin install vagrant-lxc.
I got the message: Installed the plugin 'vagrant-lxc (1.0.1)'!.
But after all, vagrant lxc ends with : The plugin "vagrant-lxc" could not be found.