by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
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.
Jens Kleikamp
@jensk
@ggrptr hm. sounds like an 1.4.x issue. yesterday I installed on 14.10 with vagrant 1.6.5 and no problems
Geiger Peter
@ggrptr
Yep, I dropped the apt-get version, and and installed 1.6.5 from the vagrant site, and it works fine. Thx.
Jens Kleikamp
@jensk
@fgrehm do you use virtualbox and lxc sometimes on the same host machine?
I am hunting a bug :) seeing host os freezes when virtualbox and lxc both are running
Fabio Rehm
@fgrehm
@jensk sorry I missed your message. I havent used the virtualbox provider in a while now
but I've never seen the host os freeze because of that
Ian Gudger
@iangudger
I am having a problem where the waiting for machine to boot step is timing out.

==> default: Starting container...
==> default: Waiting for machine to boot. This may take a few minutes...

Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

I am using the fgrehm/trusty64-lxc box.
Bryan Larsen
@bryanlarsen
host OS? Ubuntu 11.10?
Ian Gudger
@iangudger
Ubuntu 14.10
x64
Bryan Larsen
@bryanlarsen
let me grab my laptop, I recently debugged a similar problem.
Ian Gudger
@iangudger
Thanks
Bryan Larsen
@bryanlarsen
it's an LXC problem, not a vagrant-lxc one. you probably did a recent apt-get upgrade
Ian Gudger
@iangudger
Are you suggesting that I downgrade lxc?
Bryan Larsen
@bryanlarsen
I fixed it by upgrading
Ian Gudger
@iangudger
To what version?
Bryan Larsen
@bryanlarsen
to 1.1.0~alpha2-0ubuntu7
It's not released for 14.10 yet, but the 15.04 version installs fine
Ian Gudger
@iangudger
Ok, thanks
Ian Gudger
@iangudger
Great, thanks. I got it working.
still much work but might be able to varant them as well.
Fabio Rehm
@fgrehm
@necrose99 awesome!
Michael L.
@necrose99
I just hope my templates get a more sane make over in time , kinda hotwireing as gentoo-lxc exits & chrooting into... adding overlays and updates. just from a sysmin pov it should do the job.
Fabio Rehm
@fgrehm
cool!
Andrii Podanenko
@podarok
@fgrehm ping, are you around?
Fabio Rehm
@fgrehm
@podarok do u still need help?
snolahc
@snolahc
hi all, i have some apps to launch via vagrant and i'd love to use LXC. Is your provider project compatible with LXC1.0+ ? Thanks for all :)
Michael L.
@necrose99
simple bridge , lxc is backend insted of say virtual box
LeyluIAA
@LeyluIAA
Hi all, i have difficulties to install the vagrant-lxc plugin:

vagrant plugin install vagrant-lxc give me an error :

Bundler, the underlying system used to manage Vagrant plugins,
is reporting that a plugin or its dependency can't be found.
This is usually caused by manual tampering with the 'plugins.json'
file in the Vagrant home directory. To fix this error, please
remove that file and reinstall all your plugins using vagrant plugin install.
/opt/vagrant/embedded/gems/gems/bundler-1.7.9/lib/bundler/resolver.rb:368:in resolve': Could not find gem 'vagrant-lxc (>= 0) ruby' in the gems available on this machine. (Bundler::GemNotFound) from /opt/vagrant/embedded/gems/gems/bundler-1.7.9/lib/bundler/resolver.rb:166:instart'
from /opt/vagrant/embedded/gems/gems/bundler-1.7.9/lib/bundler/resolver.rb:129:in resolve' from /opt/vagrant/embedded/gems/gems/bundler-1.7.9/lib/bundler/definition.rb:193:inresolve'
from /opt/vagrant/embedded/gems/gems/bundler-1.7.9/lib/bundler/definition.rb:132:in specs' from /opt/vagrant/embedded/gems/gems/bundler-1.7.9/lib/bundler/definition.rb:177:inspecs_for'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant.rb:76:in <top (required)>' from /opt/vagrant/embedded/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:inrequire'
from /opt/vagrant/embedded/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:in rescue in require' from /opt/vagrant/embedded/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:144:inrequire'
from /opt/vagrant/bin/../embedded/gems/gems/vagrant-1.7.1/bin/vagrant:105:in `<main>'

I tried to rm plugins.json and reinstall the plugins but it does not change anything. Does someone has an idea ?
Keith Swett
@swettk
Any time for a simple pull request? fgrehm/vagrant-lxc#408
Ryan Schachte
@Schachte
Would anyone here know why lxd-top displays 0 container results?
I have 2 running lxd containers on my machine
Igor Savlook
@isavl
Hi! Someone know it is exist plugin like vagrant-lxc but for systemd-nspawn?
dhallam
@dhallam
Hi. Is anyone aware of an up-to-date example of running a docker container inside an lxc container? Most of the examples on the internet talk about using the exec-driver=lxc option which is no longer there. We use vagrant-lxc to spin up a cutdown replica of our production system for dev/ci/cd. One of the new projects wants to run a docker container inside one of the instances, but I've had no success getting this to work. Tried all sorts of options from all over the internet, e.g. setting lxc.aa_profile=unconfined and even stopping apparmor on the host - but no joy. I'm running Ubuntu 16.04 with a HWE 4.4.0-112-generic kernel on the host, and Ubuntu 14.04 with the same kernel on each of the lxc containers. LXC version 2.0.8. Docker version 17.12.0-ce. Have been getting different errors trying different things, e.g. docker: Error response from daemon: cgroups: cannot found cgroup mount destination: unknown. Many thanks.
Michael L.
@necrose99
@dhallam lxc or lxd is just a virtual machine class. https://app.vagrantup.com/markducommun/boxes/docker-compose-box wich vagrant can pull box , box uses lxc insted of vmware or virtualbox
rrmckinley
@rrmckinley
Hi, for a value like /proc/sys/fs/mqueue/msg_max in a privileged it is lower in the guest than on the host. Why is that and where is that set? I can manipulate it if I disable apparmor, but I'd rather just have the guest match the host and no higher