Re: [Lxc-users] trying to bridge wireless
Ok, i added the change to lxcbr0-up file and saved. I went back and used
brctl to add in the info you gave before but when i run ifup lxcbr0 i get:
dnsmasq:bad command line options: try --help
Seems as if there is some wrong network info i may have entered somewhere on
my end. Just wanted to ask if this looked like a familiar error to ya?
On Sat, Jun 4, 2011 at 9:11 PM, Serge Hallyn wrote:
> Quoting matthew byers (faintstlsa...@gmail.com):
> > here is what i got when i ran last command:
> >
> > stlsaint@stlsaint-devcore:~$ sudo /opt/bin/lxcbr0-up
> > iptables v1.4.4: host/network `' not found
>
> Oh, fudge. The problem is I told you (in the blog post) to do
>
> cat > file << EOF
> hack hack $var hack hack
> EOF
>
> but when you do that $var gets substituted! So your script has
>
>'/24'
>
> instead of
>
>'${braddr}/24'
>
> Please open /opt/bin/lxcbr0-up in an editor, clear it out, and paste in:
>
> #!/bin/sh
> # This is the address we assigned to our bridge in /etc/network/interfaces
> braddr=192.168.30.1
> # ip address range for containers
> brrange=192.168.30.2,192.168.30.254
> iptables -A FORWARD -i lxcbr0 -s ${braddr}/24 -m conntrack --ctstate NEW -j
> ACCEPT
> iptables -A FORWARD -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
> iptables -A POSTROUTING -t nat -j MASQUERADE
> dnsmasq --bind-interfaces --conf-file= --listen-address $braddr
> --except-interface lo --dhcp-range $brrange --dhcp-lease-max=253
> --dhcp-no-override
>
> Hopefully that's the last of my blog posting booboos for now, and it'll
> now work for you.
>
> -serge
>
--
God Bless
--
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today.
http://p.sf.net/sfu/quest-dev2dev2 ___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] trying to bridge wireless
here is what i got when i ran last command: stlsaint@stlsaint-devcore:~$ sudo /opt/bin/lxcbr0-up iptables v1.4.4: host/network `' not found Try `iptables -h' or 'iptables --help' for more information. dnsmasq: bad command line options: try --help stlsaint@stlsaint-devcore:~$ On Fri, Jun 3, 2011 at 9:24 PM, matthew byers wrote: > I will try that out when i get back home. I had to go to work. > > > On Fri, Jun 3, 2011 at 7:59 PM, Serge Hallyn > wrote: > >> Weird. >> >> You have bridge-utils installed? Does >> >>brctl addbr lxcbr0 >>ifconfig lxcbr0 192.168.42.8 netmask 255.255.255.0 >>/opt/bin/lxcbr0-up >> >> work? >> >> Quoting matthew byers (faintstlsa...@gmail.com): >> > stlsaint@stlsaint-devcore:~$ sudo ifup lxcbr0 >> > SIOCSIFADDR: No such device >> > lxcbr0: ERROR while getting interface flags: No such device >> > SIOCSIFNETMASK: No such device >> > lxcbr0: ERROR while getting interface flags: No such device >> > Failed to bring up lxcbr0. >> > >> > >> > On Fri, Jun 3, 2011 at 6:14 PM, Serge Hallyn < >> serge.hal...@canonical.com>wrote: >> > >> > > Quoting matthew byers (faintstlsa...@gmail.com): >> > > > Hey i am trying to run lxc on my laptop but am having problem >> setting up >> > > > bridge. My internet connection consist of a WAN that i have >> absolutely no >> > > > control over. I connect my tablet to the network and then tether it >> to my >> > > > laptop. I followed directions from this site: >> > > > >> > > >> http://s3hh.wordpress.com/2011/05/17/lxc-containers-on-a-host-with-wireless/up >> > > > until the point of running: ifup br0 #in which i get the Ignoring >> Uknown >> > > > Interface.as shown below >> > > > >> > > > stlsaint@stlsaint-devcore:~$ cat /etc/network/interfaces >> > > > auto lo >> > > > iface lo inet loopback >> > > > >> > > > auto lxcbr0 >> > > > iface lxcbr0 inet static >> > > > address 192.168.42.8 >> > > > netmask 255.255.255.0 >> > > > post-up /opt/bin/lxcbr0-up >> > > > >> > > > >> > > > stlsaint@stlsaint-devcore:~$ cat /opt/bin/lxcbr0-up >> > > > #!/bin/sh >> > > > # This is the address we assigned to our bridge in >> > > /etc/network/interfaces >> > > > braddr=192.168.42.8 >> > > > # ip address range for containers >> > > > brrange=192.168.42.9,192.168.42.230 >> > > > iptables -A FORWARD -i lxcbr0 -s /24 -m conntrack --ctstate NEW -j >> ACCEPT >> > > > iptables -A FORWARD -m conntrack --ctstate ESTABLISHED,RELATED -j >> ACCEPT >> > > > iptables -A POSTROUTING -t nat -j MASQUERADE >> > > > dnsmasq --bind-interfaces --conf-file= --listen-address >> > > --except-interface >> > > > lo --dhcp-range --dhcp-lease-max=253 --dhcp-no-override >> > > > >> > > > >> > > > stlsaint@stlsaint-devcore:~$ sudo ifup br0 >> > > > Ignoring unknown interface br0=br0. >> > > >> > > D'oh! >> > > >> > > Halfway through writing the post I changed br0 to lxcbr0. Apparently >> not >> > > completely. >> > > What happens if you do: >> > > >> > > sudo ifup lxcbr0 >> > > >> > > ? >> > > >> > >> > >> > >> > -- >> > God Bless >> > > > > -- > God Bless > -- God Bless -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] trying to bridge wireless
I will try that out when i get back home. I had to go to work. On Fri, Jun 3, 2011 at 7:59 PM, Serge Hallyn wrote: > Weird. > > You have bridge-utils installed? Does > >brctl addbr lxcbr0 >ifconfig lxcbr0 192.168.42.8 netmask 255.255.255.0 >/opt/bin/lxcbr0-up > > work? > > Quoting matthew byers (faintstlsa...@gmail.com): > > stlsaint@stlsaint-devcore:~$ sudo ifup lxcbr0 > > SIOCSIFADDR: No such device > > lxcbr0: ERROR while getting interface flags: No such device > > SIOCSIFNETMASK: No such device > > lxcbr0: ERROR while getting interface flags: No such device > > Failed to bring up lxcbr0. > > > > > > On Fri, Jun 3, 2011 at 6:14 PM, Serge Hallyn >wrote: > > > > > Quoting matthew byers (faintstlsa...@gmail.com): > > > > Hey i am trying to run lxc on my laptop but am having problem setting > up > > > > bridge. My internet connection consist of a WAN that i have > absolutely no > > > > control over. I connect my tablet to the network and then tether it > to my > > > > laptop. I followed directions from this site: > > > > > > > > http://s3hh.wordpress.com/2011/05/17/lxc-containers-on-a-host-with-wireless/up > > > > until the point of running: ifup br0 #in which i get the Ignoring > Uknown > > > > Interface.as shown below > > > > > > > > stlsaint@stlsaint-devcore:~$ cat /etc/network/interfaces > > > > auto lo > > > > iface lo inet loopback > > > > > > > > auto lxcbr0 > > > > iface lxcbr0 inet static > > > > address 192.168.42.8 > > > > netmask 255.255.255.0 > > > > post-up /opt/bin/lxcbr0-up > > > > > > > > > > > > stlsaint@stlsaint-devcore:~$ cat /opt/bin/lxcbr0-up > > > > #!/bin/sh > > > > # This is the address we assigned to our bridge in > > > /etc/network/interfaces > > > > braddr=192.168.42.8 > > > > # ip address range for containers > > > > brrange=192.168.42.9,192.168.42.230 > > > > iptables -A FORWARD -i lxcbr0 -s /24 -m conntrack --ctstate NEW -j > ACCEPT > > > > iptables -A FORWARD -m conntrack --ctstate ESTABLISHED,RELATED -j > ACCEPT > > > > iptables -A POSTROUTING -t nat -j MASQUERADE > > > > dnsmasq --bind-interfaces --conf-file= --listen-address > > > --except-interface > > > > lo --dhcp-range --dhcp-lease-max=253 --dhcp-no-override > > > > > > > > > > > > stlsaint@stlsaint-devcore:~$ sudo ifup br0 > > > > Ignoring unknown interface br0=br0. > > > > > > D'oh! > > > > > > Halfway through writing the post I changed br0 to lxcbr0. Apparently > not > > > completely. > > > What happens if you do: > > > > > > sudo ifup lxcbr0 > > > > > > ? > > > > > > > > > > > -- > > God Bless > -- God Bless -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] trying to bridge wireless
stlsaint@stlsaint-devcore:~$ sudo ifup lxcbr0 SIOCSIFADDR: No such device lxcbr0: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device lxcbr0: ERROR while getting interface flags: No such device Failed to bring up lxcbr0. On Fri, Jun 3, 2011 at 6:14 PM, Serge Hallyn wrote: > Quoting matthew byers (faintstlsa...@gmail.com): > > Hey i am trying to run lxc on my laptop but am having problem setting up > > bridge. My internet connection consist of a WAN that i have absolutely no > > control over. I connect my tablet to the network and then tether it to my > > laptop. I followed directions from this site: > > > http://s3hh.wordpress.com/2011/05/17/lxc-containers-on-a-host-with-wireless/up > > until the point of running: ifup br0 #in which i get the Ignoring Uknown > > Interface.as shown below > > > > stlsaint@stlsaint-devcore:~$ cat /etc/network/interfaces > > auto lo > > iface lo inet loopback > > > > auto lxcbr0 > > iface lxcbr0 inet static > > address 192.168.42.8 > > netmask 255.255.255.0 > > post-up /opt/bin/lxcbr0-up > > > > > > stlsaint@stlsaint-devcore:~$ cat /opt/bin/lxcbr0-up > > #!/bin/sh > > # This is the address we assigned to our bridge in > /etc/network/interfaces > > braddr=192.168.42.8 > > # ip address range for containers > > brrange=192.168.42.9,192.168.42.230 > > iptables -A FORWARD -i lxcbr0 -s /24 -m conntrack --ctstate NEW -j ACCEPT > > iptables -A FORWARD -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT > > iptables -A POSTROUTING -t nat -j MASQUERADE > > dnsmasq --bind-interfaces --conf-file= --listen-address > --except-interface > > lo --dhcp-range --dhcp-lease-max=253 --dhcp-no-override > > > > > > stlsaint@stlsaint-devcore:~$ sudo ifup br0 > > Ignoring unknown interface br0=br0. > > D'oh! > > Halfway through writing the post I changed br0 to lxcbr0. Apparently not > completely. > What happens if you do: > > sudo ifup lxcbr0 > > ? > -- God Bless -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
[Lxc-users] trying to bridge wireless
Hey i am trying to run lxc on my laptop but am having problem setting up bridge. My internet connection consist of a WAN that i have absolutely no control over. I connect my tablet to the network and then tether it to my laptop. I followed directions from this site: http://s3hh.wordpress.com/2011/05/17/lxc-containers-on-a-host-with-wireless/ up until the point of running: ifup br0 #in which i get the Ignoring Uknown Interface.as shown below stlsaint@stlsaint-devcore:~$ cat /etc/network/interfaces auto lo iface lo inet loopback auto lxcbr0 iface lxcbr0 inet static address 192.168.42.8 netmask 255.255.255.0 post-up /opt/bin/lxcbr0-up stlsaint@stlsaint-devcore:~$ cat /opt/bin/lxcbr0-up #!/bin/sh # This is the address we assigned to our bridge in /etc/network/interfaces braddr=192.168.42.8 # ip address range for containers brrange=192.168.42.9,192.168.42.230 iptables -A FORWARD -i lxcbr0 -s /24 -m conntrack --ctstate NEW -j ACCEPT iptables -A FORWARD -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT iptables -A POSTROUTING -t nat -j MASQUERADE dnsmasq --bind-interfaces --conf-file= --listen-address --except-interface lo --dhcp-range --dhcp-lease-max=253 --dhcp-no-override stlsaint@stlsaint-devcore:~$ sudo ifup br0 Ignoring unknown interface br0=br0. stlsaint@stlsaint-devcore:~$ -- God Bless -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] lxc-clone
I saw this on the blog. Very useful and time saver. Exactly what alot of
pople were looking for.
On Wed, Mar 30, 2011 at 7:29 PM, Serge E. Hallyn wrote:
> I've replaced most of my previous use of kvm and cloud instances for bug
> investigations with lxc instances. To emulate my older workflows, I've
> created lxc-clone. My diff against the current natty lxc package is
> attached. I've written up how I use this at s3hh.wordpress.com. Briefly,
> I have a single pristine container, with LVM rootfs, for each of lucid,
> maverick, and natty. When I want a container, I
>
>lxc-clone -o natty -n n1 -s
>lxc-start -n n1
>
> which takes about 5 seconds altogether. Ruin n1 however I like, and
>
>lxc-destroy -l -n n1
>
> when done.
>
> It needs fleshing out, but it's at the point where it does exactly what
> I need. The next thing I'm likely to add will be btrfs snapshotting,
> not sure when.
>
> Daniel, is this something you'd consider adding? I assume that if so,
> then there are changes you'd like to make to the interface :)
>
> thanks,
> -serge
>
> === modified file 'configure'
> --- configure 2011-03-10 07:25:34 +
> +++ configure 2011-03-30 15:36:58 +
> @@ -5057,7 +5057,7 @@
> CFLAGS="$CFLAGS -Wall"
> fi
>
> -ac_config_files="$ac_config_files Makefile lxc.pc lxc.spec config/Makefile
> doc/Makefile doc/lxc-create.sgml doc/lxc-destroy.sgml doc/lxc-execute.sgml
> doc/lxc-start.sgml doc/lxc-checkpoint.sgml doc/lxc-restart.sgml
> doc/lxc-stop.sgml doc/lxc-console.sgml doc/lxc-freeze.sgml
> doc/lxc-unfreeze.sgml doc/lxc-monitor.sgml doc/lxc-wait.sgml doc/lxc-ls.sgml
> doc/lxc-ps.sgml doc/lxc-cgroup.sgml doc/lxc-kill.sgml doc/lxc.conf.sgml
> doc/lxc.sgml doc/common_options.sgml doc/see_also.sgml doc/rootfs/Makefile
> doc/examples/Makefile doc/examples/lxc-macvlan.conf
> doc/examples/lxc-vlan.conf doc/examples/lxc-no-netns.conf
> doc/examples/lxc-empty-netns.conf doc/examples/lxc-phys.conf
> doc/examples/lxc-veth.conf doc/examples/lxc-complex.conf templates/Makefile
> templates/lxc-lenny templates/lxc-debian templates/lxc-lucid
> templates/lxc-maverick templates/lxc-natty templates/lxc-busybox
> templates/lxc-fedora templates/lxc-sshd src/Makefile src/lxc/Makefile
> src/lxc/lxc-ps src/lxc/lxc-ls src/lxc/lxc-netstat src/lxc/lxc-checkconfig
> src/lxc/lxc-setcap src/lxc/lxc-setuid src/lxc/lxc-version src/lxc/lxc-create
> src/lxc/lxc-destroy"
> +ac_config_files="$ac_config_files Makefile lxc.pc lxc.spec config/Makefile
> doc/Makefile doc/lxc-create.sgml doc/lxc-destroy.sgml doc/lxc-execute.sgml
> doc/lxc-start.sgml doc/lxc-checkpoint.sgml doc/lxc-restart.sgml
> doc/lxc-stop.sgml doc/lxc-console.sgml doc/lxc-freeze.sgml
> doc/lxc-unfreeze.sgml doc/lxc-monitor.sgml doc/lxc-wait.sgml doc/lxc-ls.sgml
> doc/lxc-ps.sgml doc/lxc-cgroup.sgml doc/lxc-kill.sgml doc/lxc.conf.sgml
> doc/lxc.sgml doc/common_options.sgml doc/see_also.sgml doc/rootfs/Makefile
> doc/examples/Makefile doc/examples/lxc-macvlan.conf
> doc/examples/lxc-vlan.conf doc/examples/lxc-no-netns.conf
> doc/examples/lxc-empty-netns.conf doc/examples/lxc-phys.conf
> doc/examples/lxc-veth.conf doc/examples/lxc-complex.conf templates/Makefile
> templates/lxc-lenny templates/lxc-debian templates/lxc-lucid
> templates/lxc-maverick templates/lxc-natty templates/lxc-busybox
> templates/lxc-fedora templates/lxc-sshd src/Makefile src/lxc/Makefile
> src/lxc/lxc-ps src/lxc/lxc-ls src/lxc/lxc-netstat src/lxc/lxc-checkconfig
> src/lxc/lxc-setcap src/lxc/lxc-setuid src/lxc/lxc-version src/lxc/lxc-create
> src/lxc/lxc-clone src/lxc/lxc-destroy"
>
> ac_config_commands="$ac_config_commands default"
>
> @@ -5842,6 +5842,7 @@
> "src/lxc/lxc-setuid") CONFIG_FILES="$CONFIG_FILES src/lxc/lxc-setuid"
> ;;
> "src/lxc/lxc-version") CONFIG_FILES="$CONFIG_FILES src/lxc/lxc-version"
> ;;
> "src/lxc/lxc-create") CONFIG_FILES="$CONFIG_FILES src/lxc/lxc-create"
> ;;
> +"src/lxc/lxc-clone") CONFIG_FILES="$CONFIG_FILES src/lxc/lxc-clone" ;;
> "src/lxc/lxc-destroy") CONFIG_FILES="$CONFIG_FILES src/lxc/lxc-destroy"
> ;;
> "default") CONFIG_COMMANDS="$CONFIG_COMMANDS default" ;;
>
>
> === modified file 'configure.ac'
> --- configure.ac2011-03-10 07:25:34 +
> +++ configure.ac2011-03-30 15:36:58 +
> @@ -156,6 +156,7 @@
>src/lxc/lxc-setuid
>src/lxc/lxc-version
>src/lxc/lxc-create
> + src/lxc/lxc-clone
>src/lxc/lxc-destroy
>
> ])
>
> === modified file 'lxc.spec'
> --- lxc.spec2011-03-10 07:25:34 +
> +++ lxc.spec2011-03-30 15:36:58 +
> @@ -78,6 +78,7 @@
> %{_bindir}/*
> %attr(4111,root,root) %{_bindir}/lxc-attach
> %attr(4111,root,root) %{_bindir}/lxc-create
> +%attr(4111,root,root) %{_bindir}/lxc-clone
> %attr(4111,root,root) %{_bindir}/lxc-start
> %attr(4111,root,root) %{_bindir}/lxc-netstat
> %attr(4111,root,root) %{_bindir}/lxc-unshare
>
> === modified file 'src/lxc/Makefile.am'
> --- src/lxc/Makefile.am 2011-03-10 07:25:34 +
> +++ src/lxc/Makefil
Re: [Lxc-users] Control panel
yes that would be by far the best server solution i have ever come across if somehow the openvz kernel could be used in conjuction with lxc. On Wed, Mar 16, 2011 at 10:14 AM, Stuart Johnson wrote: > On 16/03/11 16:01, matthew byers wrote: > > Oh i wasnt suggesting switching to proxmox, i was speaking mostly on > > the control panel it uses and some of the stuff that can be > > incorporated into this lxc panel. i used proxmox before too and i > > highly enjoy it but i am unable to use my extra drives in my server > > unless i setup lvm which i dont want. > > No I know, you weren't. Just agreeing that proxmox is a superb product, > and if it supported LXC, then I would be using it. > > > > > -- > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > ___ > Lxc-users mailing list > Lxc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/lxc-users > -- God Bless -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Control panel
Oh i wasnt suggesting switching to proxmox, i was speaking mostly on the control panel it uses and some of the stuff that can be incorporated into this lxc panel. i used proxmox before too and i highly enjoy it but i am unable to use my extra drives in my server unless i setup lvm which i dont want. On Wed, Mar 16, 2011 at 9:50 AM, Stuart Johnson wrote: > On 16/03/11 15:18, matthew byers wrote: > > This is a great start as i have heard many folks inquire about this > > for lxc. I dont know if you all are familiar with something called > > Proxmox (debian with openvz kernel for openvz and kvm containers) but > > it has a great web browser based control panel that is accessed via > > the server ip address. The panel has some functions such as: > > 1. Start/stop/restart containers (as discussed already) > > 2. VNC into a container > > 3. Creation/destruction of containers > > 4.manage container resources (RAM, hdd size, container ip, dns, etc) > > > > Im not sure with the resource management as we use cgroups but i just > > wanted to throw out some ideas on it. > > I have recently been evaluating Proxmox, and it's near perfect for what > I need. But it has a major drawback, in that it does not have LXC > support yet, and requires a customised kernel for OpenVZ. In fact it's > a customised distro, which is fine if your installing it on your own > hardware, but a bit of a problem installing it at a datacentre on > someone else's machine. > > When I thought about it, all I needed was a recent distro (debian or > whatever), and a simple GUI. SSH into the box, install LXC, and the > network bridge. Start an ncurses app, and start creating & managing > containers. Job done. > > Stuart. > > > -- > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > ___ > Lxc-users mailing list > Lxc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/lxc-users > -- God Bless -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Control panel
This is a great start as i have heard many folks inquire about this for lxc. I dont know if you all are familiar with something called Proxmox (debian with openvz kernel for openvz and kvm containers) but it has a great web browser based control panel that is accessed via the server ip address. The panel has some functions such as: 1. Start/stop/restart containers (as discussed already) 2. VNC into a container 3. Creation/destruction of containers 4.manage container resources (RAM, hdd size, container ip, dns, etc) Im not sure with the resource management as we use cgroups but i just wanted to throw out some ideas on it. On Wed, Mar 16, 2011 at 6:05 PM, Serge E. Hallyn wrote: > Quoting Geordy Korte (gko...@gmail.com): > > On Wed, Mar 16, 2011 at 3:00 PM, Daniel Lezcano >wrote: > > > > > On 03/16/2011 02:16 PM, Serge E. Hallyn wrote: > > > > > >> Had some time to spare and decided that I would pitch in. Attached a > > >>> simple > > >>> dialog system that will allow you to start/stop an lxc container and > open > > >>> the console. It's really really really early (lol took me 5 minutes) > but > > >>> let me know if this is what you are looking for and if so what you > would > > >>> like to have added to it. > > >>> > > >> > > >> Exactly - this is exactly what I was thinking and how I've done some > > >> things like this in the past. It's not that the things it does need > > >> to be fancy - it's just that it should reduce typing quite a bit. > > >> > > >> I like it. > > >> > > > > > > I share Serge's opinion. > > > > > > Thanks ! > > > > > > OK... > > > > So what could we put in it? We can edit the cfg files for a container but > > that seems a little over the top since VI or any good text editor will do > > the same. > > > > I can't think of anything I would like in there but then again I only > have 8 > > containers. > > Some simple things: > > 1. editing configs actually is useful just bc you don't have to type > in the whole config pathname > > 2. tag containers in the list view and perform group actions > > 3. open consoles - heck, perhaps tag containers in the list view, > create a new screen session, and open a console for each container > in a new window in the screen session. Limited by # of screens in > a session though. > > -serge > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.10 (GNU/Linux) > > iQEcBAEBAgAGBQJNgNG6AAoJEHmllQITXQdFHfsH/25stTltRlEzqiyJX6Fx8y+u > Mwt/kA3PJHnhcl/m6SHxzdUBJJ9rGUL8ZOngucUfG9Mt78fApXFEGTWpBX9UkQQY > U39NllZwFW7myQUIqmAvkr7Ta8D1n2zPAHC35b05a34XJdR9JftoPwD/wXA/RWAD > lJwWz9vqYODng94r0zgea0v7EdMUt9WGaBOALoXSbYLJT+IsR6Gn49gFjRA076u4 > rcwDb0aL/usEE2Ce/FF8psZDPN+kPP3rGRFzgHrZA5wCeLqE/DEJBdHgYtO7Antv > XSKeroUqyYnhMSUaEBFDvP2iTgqkG2xrd0TPHqXNo5pm3J0+2LO7t5JnPGNlwhg= > =gR8x > -END PGP SIGNATURE- > > > -- > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > ___ > Lxc-users mailing list > Lxc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/lxc-users > > -- God Bless -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] making bridge in container
Oh ok, well is there another guide on how to setup openvpn in a container? All the guides show to use a bridge. On Mon, Jan 17, 2011 at 12:32 AM, Daniel Lezcano wrote: > On 01/16/2011 11:27 PM, matthew byers wrote: > >> The container kernel is 2.6.32-27-server >> > > Hmm, I think this is not supported by this kernel version. You should use a > 2.6.35 where the sysfs per namespace is supported. > If I am not wrong, you should have a kernel oops in your /var/log/messages. > > -- Daniel > -- God Bless -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] making bridge in container
The container kernel is 2.6.32-27-server On Sat, Jan 15, 2011 at 6:51 AM, Daniel Lezcano wrote: > On 01/15/2011 08:56 AM, matthew byers wrote: > >> Im trying to setup openvpn on container. Guides say to setup bridge in >> container for vpn. When i first configured bridge i got the "segment >> fault..." error. Now i just get a the "Trying to reconfigure >> interfaces..." >> and it just stays there. It doesnt say the usual "ok" confirmation. Here >> is >> my current container interfaces conf: (based off the guide) >> basically i need a guide on setting up a bridge in a lxc container. >> > > What is the kernel version ? > >> >> container conf >> >> auto br0 >> iface br0 inet static >> address 192.168.1.109 >> network 192.168.1.0 >> netmask 255.255.255.0 >> broadcast 192.168.1.255 >> gateway 192.168.1.1 >> bridge_ports eth0 >> bridge_fd 9 >> bridge_hello 2 >> bridge_maxage 12 >> ### >> Here is my host conf: >> ### >> auto br0 >> iface br0 inet static >> address 192.168.1.106 >> netmask 255.255.255.0 >> network 192.168.1.0 >> gateway 192.168.1.1 >> broadcast 192.168.1.255 >> bridge_ports eth0 >> bridge_stp off >> bridge_maxwait 5 >> post-up /usr/sbin/brctl setfd br0 0 >> >> >> >> >> >> >> >> >> >> >> >> -- >> Protect Your Site and Customers from Malware Attacks >> Learn about various malware tactics and how to avoid them. Understand >> malware threats, the impact they can have on your business, and how you >> can protect your company and customers by using code signing. >> http://p.sf.net/sfu/oracle-sfdevnl >> >> >> ___ >> Lxc-users mailing list >> Lxc-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/lxc-users >> > > -- God Bless -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
[Lxc-users] making bridge in container
Im trying to setup openvpn on container. Guides say to setup bridge in container for vpn. When i first configured bridge i got the "segment fault..." error. Now i just get a the "Trying to reconfigure interfaces..." and it just stays there. It doesnt say the usual "ok" confirmation. Here is my current container interfaces conf: (based off the guide) basically i need a guide on setting up a bridge in a lxc container. container conf auto br0 iface br0 inet static address 192.168.1.109 network 192.168.1.0 netmask 255.255.255.0 broadcast 192.168.1.255 gateway 192.168.1.1 bridge_ports eth0 bridge_fd 9 bridge_hello 2 bridge_maxage 12 ### Here is my host conf: ### auto br0 iface br0 inet static address 192.168.1.106 netmask 255.255.255.0 network 192.168.1.0 gateway 192.168.1.1 broadcast 192.168.1.255 bridge_ports eth0 bridge_stp off bridge_maxwait 5 post-up /usr/sbin/brctl setfd br0 0 -- God Bless -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] rootfs backup
What is the name of the tool? I have extra drives so making one that doesn't house system files is easy enough. I run btrfs on my main install on my laptop for months now with no issues whatsoever, btw. On Mon, Jan 10, 2011 at 7:30 PM, Trent W. Buck wrote: > matthew byers > writes: > > > Yea i know btrfs has snapshot abilities but my entire server is ext4. > > There is a tool to convert an ext filesystem to btrfs IN-PLACE. > > I do not recommend it, because I do not recommend btrfs at all -- it is > not production-ready. (I do use it at home; YMMV.) > > > > -- > Gaining the trust of online customers is vital for the success of any > company > that requires sensitive data to be transmitted over the Web. Learn how to > best implement a security strategy that keeps consumers' information secure > and instills the confidence they need to proceed with transactions. > http://p.sf.net/sfu/oracle-sfdevnl > ___ > Lxc-users mailing list > Lxc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/lxc-users > -- God Bless -- Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] rootfs backup
Yea i know btrfs has snapshot abilities but my entire server is ext4. I could format a extra drive with btrfs. Would that allow me to use btrfs for containers? Are there any other ideas or processes i can try out? On Thu, Jan 6, 2011 at 12:50 PM, C Anthony Risinger wrote: > On Thu, Jan 6, 2011 at 12:02 PM, Noah Campbell > wrote: > > > > With my limited knowledge of lxc, I would recommend looking at a > filesystem that supports snapshots. > > yes, in the past i've used btrfs for this (.32 kernel). some will say > that it's not suitable for use (and in some situations it may not be), > but imo, it's stable enough for my uses; i've had a server running > since .32 was released (2 yrs?) hosting several btrfs-based containers > without any issue... and btrfs was only considered "ready for early > adopters" at that point. > > using a couple of template subvolumes, i was able to snapshot them > into usable domains in < 1 second, and create backups just as fast, > while at the same time reusing blocks and saving enormous amounts of > disk space. > > works like a treat :-) i plan on using it extensively very soon for an > updated KVM+LXC server using libvirt. > > C Anthony > > psdepending on how... bold... you are, there are LZO compression > patches queued for .38: > > http://www.spinics.net/lists/linux-btrfs/msg07748.html > > and some dedup work is basic but workable: > > http://www.spinics.net/lists/linux-btrfs/msg07819.html > http://www.spinics.net/lists/linux-btrfs/msg07820.html > > both will be very useful for containerized environments. > -- God Bless -- Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
[Lxc-users] rootfs backup
Hey i was wondering if there is a way to backup a rootfs aside from copying it over. Im asking because i made a container with intent of messing it up. I succeeded which in turn messed up the rootfs. So i was wondering if there was a way to backup a rootfs aside from using: cp rootfs.ubuntu rootfs.ubuntu.bak Is there a snapshot ability or something? As you can tell i am newly starting to get into lxc. Any help/ideas is greatly appreciated. -- God Bless -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] lxc doesn't work on Fedora 13
Yea this seems to be a issue with the basic fedora template. On Fri, Sep 17, 2010 at 4:27 AM, Scott Bronson wrote: > I have lxc working pretty well on my Ubuntu Lucid box. Now I'm trying > to get it to work on my Fedora 13 laptop but I can't seem to get it to > connect to any guest consoles. > > Here's an example: > > [r...@lyra-f13 ubu-guest]# lxc-start -f config -n ubu-guest -o > $(tty) -l DEBUG > lxc-start 1284711204.849 DEBUGlxc_conf - allocated pty > '/dev/pts/8' (4/5) > ... > lxc-start 1284711204.884 NOTICE lxc_start - exec'ing '/sbin/init' > lxc-start 1284711204.886 NOTICE lxc_start - '/sbin/init' > started with pid '14166' > lxc-start 1284711204.886 DEBUGlxc_utmp - Added > 'rootfs/var/run' to inotifywatch > > Things look OK but when I try to connect from another terminal: > >[r...@lyra-f13 bronson]# lxc-console -n ubu-guest >Type to exit the console > > Nothing happens. It just hangs until I exit the console (well, > characters are echoed back). > > This appears on the debug console when I try to connect. > > lxc-start 1284711279.657 DEBUGlxc_commands - peer has disconnected > > > I rsynced this guest to my Ubuntu Lucid box and everything works > great. lxc-start fires right up, and lxc-console connects and > immediately prompts for a login. > > Any idea why lxc isn't working in F13? This happens for all guests > that I try -- Ubuntu, Debian, and Busybox, all of which work on Lucid. > I'm using stock distro kernels. Thanks! > >- Scott > > > Failing, Fedora 13 log: > > [r...@lyra-f13 ubu-guest]# lxc-start -n ubu-guest -f config -o $(tty) -l > DEBUG > lxc-start 1284711865.511 DEBUGlxc_conf - allocated pty > '/dev/pts/5' (4/5) > lxc-start 1284711865.512 DEBUGlxc_conf - allocated pty > '/dev/pts/6' (6/7) > lxc-start 1284711865.512 DEBUGlxc_conf - allocated pty > '/dev/pts/7' (8/9) > lxc-start 1284711865.512 DEBUGlxc_conf - allocated pty > '/dev/pts/8' (10/11) > lxc-start 1284711865.512 INFO lxc_conf - tty's configured > lxc-start 1284711865.512 DEBUGlxc_console - using '/dev/tty' > as console > lxc-start 1284711865.512 DEBUGlxc_start - sigchild handler set > lxc-start 1284711865.512 INFO lxc_start - 'ubu-guest' is > initialized > lxc-start 1284711865.518 DEBUGlxc_conf - instanciated veth > 'veth8b9zhC/vethdzJ3Mu', index is '60' > lxc-start 1284711865.523 DEBUGlxc_cgroup - using cgroup > mounted at '/cgroup' > lxc-start 1284711865.523 DEBUGlxc_cgroup - '/cgroup/14448' > renamed to '/cgroup/ubu-guest' > lxc-start 1284711865.527 DEBUGlxc_conf - move 'virbr0' to '14448' > lxc-start 1284711865.527 INFO lxc_conf - 'ubu-guest' > hostname has been setup > lxc-start 1284711865.531 DEBUGlxc_conf - 'eth0' has been setup > lxc-start 1284711865.531 INFO lxc_conf - network has been setup > lxc-start 1284711865.531 DEBUGlxc_cgroup - using cgroup > mounted at '/cgroup' > lxc-start 1284711865.531 DEBUGlxc_conf - cgroup > 'devices.deny' set to 'a' > lxc-start 1284711865.531 DEBUGlxc_conf - cgroup > 'devices.allow' set to 'c 1:3 rwm' > lxc-start 1284711865.531 DEBUGlxc_conf - cgroup > 'devices.allow' set to 'c 1:5 rwm' > lxc-start 1284711865.531 DEBUGlxc_conf - cgroup > 'devices.allow' set to 'c 5:1 rwm' > lxc-start 1284711865.531 DEBUGlxc_conf - cgroup > 'devices.allow' set to 'c 5:0 rwm' > lxc-start 1284711865.531 DEBUGlxc_conf - cgroup > 'devices.allow' set to 'c 4:0 rwm' > lxc-start 1284711865.531 DEBUGlxc_conf - cgroup > 'devices.allow' set to 'c 4:1 rwm' > lxc-start 1284711865.531 DEBUGlxc_conf - cgroup > 'devices.allow' set to 'c 1:9 rwm' > lxc-start 1284711865.531 DEBUGlxc_conf - cgroup > 'devices.allow' set to 'c 1:8 rwm' > lxc-start 1284711865.531 DEBUGlxc_conf - cgroup > 'devices.allow' set to 'c 136:* rwm' > lxc-start 1284711865.531 DEBUGlxc_conf - cgroup > 'devices.allow' set to 'c 5:2 rwm' > lxc-start 1284711865.531 DEBUGlxc_conf - cgroup > 'devices.allow' set to 'c 254:0 rwm' > lxc-start 1284711865.531 INFO lxc_conf - cgroup has been setup > lxc-start 1284711865.531 DEBUGlxc_conf - mounted proc on > rootfs/proc, type proc > lxc-start 1284711865.531 DEBUGlxc_conf - mounted devpts on > rootfs/dev/pts, type devpts > lxc-start 1284711865.532 DEBUGlxc_conf - mounted sysfs on > rootfs/sys, type sysfs > lxc-start 1284711865.532 INFO lxc_conf - mount points have been > setup > lxc-start 1284711865.532 INFO lxc_conf - mount points have been > setup > lxc-start 1284711865.532 INFO lxc_conf - console has been setup > lxc-start 1284711865.532 INFO lxc_conf - 4 tty(s) has been setup > lxc-start 1284711865.532 DEBUGlxc_conf - mounted 'rootfs' on > '/usr/lib64/lxc/rootfs' > lxc-start 1284711865.532 DEBUGlxc_conf - mount
Re: [Lxc-users] fedora template not working
Awesome man please let it be known when the template is functional! On Sun, Sep 5, 2010 at 3:26 PM, Daniel Lezcano wrote: > On 09/04/2010 10:55 PM, matthew byers wrote: > >> Using the templates i am able to create a fully working ubuntu and debian >> container. But when i use the exact same procedure for fedora i get the >> Type >> .etc error and am unable to connect to the container. Is >> this >> something that everyone is going through? I am using lxc version 0.7.2. >> >> > > Yep, I think the lxc-fedora template is not yet finished. > I tried to update it in order to have the script similar to the ubuntu > template. > Unfortunately I am running on an ubuntu host and febootstrap fails to > create the fedora rootfs. > > I have now a fedora container running, so I will try to fix the lxc-fedora > script by using the fedora container and the febootstrap tool running > inside. > > Thanks > -- Daniel > -- God Bless -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
[Lxc-users] fedora template not working
Using the templates i am able to create a fully working ubuntu and debian container. But when i use the exact same procedure for fedora i get the Type .etc error and am unable to connect to the container. Is this something that everyone is going through? I am using lxc version 0.7.2. -- God Bless -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
