Can't start VM on Fedora 19 #113
Comments
|
More info: When I tried |
|
@sickill do you mind getting hold of a Vagrant / VBox VM so that we have a common ground for reproducing and discussing the issues? ;) |
|
@fgrehm sure. Do you have similar script for setting up vagrant/vagrant-lxc on Fedora VM like you had for Ubuntu one? |
|
@sickill unfortunately not, I actually never used Fedora before =/ can you gist me the steps to install vagrant and the LXC packages there? I might be able to get to this tonight before releasing 0.4.0 ;) |
|
@sickill I was able to reproduce an error but I'm not sure if it is the same as you are experiencing over there. Here's a fedora 19 vagrant VBox VM ready for vagrant-lxc usage and this is my debugging session. |
|
I can verify the problem is reproducible on a Precise Host using the following versions Tested on current base boxes found at the wiki page, Precise/Quantal/Raring all experience the above error. My current vagrant file: Output from vagrant up --provider=lxc My ifconfig output for lxcbr0 Ill try to dig more into this problem tonight but putting this up here for reference |
|
@battlemidget tks for the info, I'll try it out later on but it's really weird since I haven't had an issue with precise hosts in a while and I always run the sanity check tests from a precise VBox VM before releasing new boxes one thing you can try out to debug is manually run |
Running this command as a normal user results in a permission denied but when run under sudo the container starts up without a problem. So that makes me wonder if @fgrehm your setup uses sudo anywhere during the container creation? Using the defaults for a vagrant box under virtualbox doesn't require the use of sudo so maybe im missing a configuration option in my vagrantfile? I just double checked your sanity tests and noticed everything is run with sudo, so this is probably the issue we are seeing as well. @fgrehm second question: do you run your containers with apparmor enabled? The default profile puts both lxc-start and lxc-container-default into enforce mode on 12.04 which I believe is where the problem is |
Sorry, I missed out the
There is no
I'm not sure about that but a gist with the output of |
Here is the output with the latest raring v3 box and 0.4.0 http://paste.ubuntu.com/5889411/ I manually ran the lxc-info to see but when I run lxc-start against that id it works just fine |
|
@battlemidget tks! so if you look at the line 212 you'll see the command that vagrant-lxc is running to start the container. if you were able to start it with |
Sooo that was the offending part and can you spot the issue? :) (hint: it was a particular letter that needed to go at the end of 1024) So everything works now thanks for the fresh set of eyes |
|
@battlemidget 🎆 glad to help :D |
|
hey @sickill, yesterday I came across this comment on the GH lxc repo and it seems that lxc is broken on F18 and F19 hosts =/ |
|
@fgrehm oh, this looks bad :/ |
|
I'm trying it in Fedora 19, with vagrant 1.3.1 + lxc 0.9 + vagrant-lxc 0.6.0 + kernel 3.10.11. One of the problems is about lxcbr0, it is an ubuntu thing, is not created by default in other distros. One possible solution is to check for it, and auto create it if not found. |
|
@jalberto hum... are you able to manually create and boot containers without vagrant-lxc? Last time I tried it didn't work out =/ |
|
[root@olive ~]# lxc-info --name healandgo_default-1379435452 I can access with lxc-console but I cannot connect to it using ssh, I think because lxcbr0 need to have an specific address This howto have some clues: http://blog.bodhizazen.net/linux/lxc-linux-containers/ |
|
@jalberto awesome! I'm not familiar with Fedora so would you be able to create a gist with the steps required to get to the point where you are? Even better would be if you could set things up on a Vagrant VirtualBox VM so that I can reproduce the steps from here and we can better collaborate to make this work ;) |
|
@fgrehm with this Vagrantfile you will get a environment similar to mine :) |
|
@jalberto awesome! Just to double check, have you seen this wiki page on setting things up for Debian? I think that if you are able to replicate a NAT setup similar to Ubuntu's one you should be good to go too :) Just LMK how it goes so we can create a new Wiki page for Fedora ;) We might automatically do these configs at some point, but I'm not looking into it before I'm able to deal with hashicorp/vagrant#2005 |
|
@fgrehm This is a init file modified to work with fedora, just small changes, but interfaces are created. But I yet cannot connect by ssh |
|
Using static IP config I can login with ssh: config.vm.provider :lxc do |lxc| but the container don't have internet connection |
|
great news: http://blog.docker.io/2013/09/red-hat-and-docker-collaborate/ I think is a good strategy to use libvirt for network things |
|
@jalberto someone else suggested using libvirt for networking before but I have no idea how that would look like. would you mind sharing your thoughts on #120 and #119? |
So I switched to Fedora (19) and I tried to use raring64 lxc box. This is what I got when ran
vagrant up:Where should I look to give you more information?
The text was updated successfully, but these errors were encountered: