Re: [Lxc-users] Horrors using Debian Wheezy
Thanks. That worked. I used [path-to-container]/run/shm because I got Permission Denied when using /dev/shm, which after booting is symlinked to /run/shm. -Randall On 09/17/2013 01:33 AM, Andreas Laut wrote: Hi. For lxc.mount.entry you have to write down the path from sight of your host. lxc.mount.entry = tmpfs /var/lib/lxc/[your-debian-container]/dev/shm tmpfs defaults 0 0 Regards, Andreas attachment: randall.vcf smime.p7s Description: S/MIME Cryptographic Signature -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151iu=/4140/ostg.clktrk___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Horrors using Debian Wheezy
Sorry I don't have the older emails in this thread, but the preferred syntax is to use a path relative to your container rootfs, i.e. 'run/shm', i.e. lxc.mount.entry = tmpfs run/shm tmpfs defaults 0 0 If that is not working then there's a bug. -serge Quoting Randall Smith (rand...@tnr.cc): Thanks. That worked. I used [path-to-container]/run/shm because I got Permission Denied when using /dev/shm, which after booting is symlinked to /run/shm. -Randall On 09/17/2013 01:33 AM, Andreas Laut wrote: Hi. For lxc.mount.entry you have to write down the path from sight of your host. lxc.mount.entry = tmpfs /var/lib/lxc/[your-debian-container]/dev/shm tmpfs defaults 0 0 Regards, Andreas begin:vcard fn:Randall Smith n:Smith;Randall org:Berrymantech, LLC email;internet:rand...@tnr.cc title:Owner tel;work:601-982-8766 tel;home:601-207-2363 tel;cell:504-957-3328 x-mozilla-html:TRUE url:http://www.berrymantech.com version:2.1 end:vcard -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151iu=/4140/ostg.clktrk ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151iu=/4140/ostg.clktrk ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Horrors using Debian Wheezy
I'm using your template on an Ubuntu 12.04 stock LXC install. I've run into a problem trying to use shared memory with Python's multiprocessing library. It relies on /dev/shm using tmpfs. I tried mounting it with an entry: lxc.mount.entry = tmpfs /dev/shm tmpfs defaults 0 0 and variations of the above without success. The included Ubuntu LXC template creates several tmpfs entries and I don't have this problem with it, so I think the issue is with the Debian guest. Do you have any idea how to fix this? My best guess is that it has something to do with the cgroup device restrictions. In the generated LXC configuration file you find several lxc.cgroup.devices.* entries. Remove these (make them comments) and restart your container. If this solves the problem you can probably copy the device entries from the Ubuntu configuration to the Debian configuration. Rob. http://freedomboxblog.nl -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151iu=/4140/ostg.clktrk ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Horrors using Debian Wheezy
Rob, I'm using your template on an Ubuntu 12.04 stock LXC install. I've run into a problem trying to use shared memory with Python's multiprocessing library. It relies on /dev/shm using tmpfs. I tried mounting it with an entry: lxc.mount.entry = tmpfs /dev/shm tmpfs defaults 0 0 and variations of the above without success. The included Ubuntu LXC template creates several tmpfs entries and I don't have this problem with it, so I think the issue is with the Debian guest. Do you have any idea how to fix this? Thanks. Randall -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151iu=/4140/ostg.clktrk ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Horrors using Debian Wheezy
On 05/11/2013 04:41 AM, Mason Loring Bliss wrote: Hi there! I'm trying to get LXC to work for me on Debian Wheezy/amd64 and I'm having a Hellish time. I'm following the advice on wiki.debian.org and other places, and I believe I'm creating my containers correctly, but when I launch a container, I get a bunch of messages about needing root to set a hostname, needing root to mount things, needing root to do various other things, and I see sshd fail to create keys, and at the very end I get nothing. No console. I can't use the console command to connect - I get nothing. The status tool says things are running. lxc-checkconfig says everything is hunky-dory and I'm not deviating from the instructions. Can someone suggest what might be going wrong here? Does it starts correctly if run it as root ? -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Horrors using Debian Wheezy
I'm trying to get LXC to work for me on Debian Wheezy/amd64 and I'm having a Hellish time. I'm following the advice on wiki.debian.org and other places, and I believe I'm creating my containers correctly, but when I launch a container, I get a bunch of messages about needing root to set a hostname, needing root to mount things, needing root to do various other things, and I see sshd fail to create keys, and at the very end I get nothing. No console. I can't use the console command to connect - I get nothing. The status tool says things are running. lxc-checkconfig says everything is hunky-dory and I'm not deviating from the instructions. Can someone suggest what might be going wrong here? Hi, The template to create Debian containers that ships with Wheezy is broken. I tried to get this fixed before the Wheezy release but failed. Here is my solution from the bug report at: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680469 snip First let me explain the problem. LXC uses shell scripts (they call them templates) to create the rootfs of a container, this is where things go wrong. The current Wheezy templates for creating a Debian rootfs use live-debconfig and this package will not be included in Wheezy. Although the scripts run, the generated rootfs is not configured correctly. Fortunately there is nothing wrong with LXC. Simply replacing the shell script with a version that does not depend on packages that are not in Wheezy will solve the problem. On my own computers i use a slightly modified version of the Debian template that came with Squeeze. My modifications are: 1) Installing a Squeeze rootfs instead of a Lenny rootfs 2) Replacing the deprecated DHCP package 3) Adding some mknod commands to create tty's in the generated rootfs 4) Support for the armel architecture. 5) For the network configuration the template expects that the host has a bridged network with the name br0 and a DHCP server running. I have updated this template to install a Wheezy rootfs and tested the result. It seems to work perfectly. So my solution is: remove the non-functioning Debian templates from the LXC package and replace them with my working template. You can download my Debian Wheezy template at: http://freedomboxblog.nl/wp-content/uploads/lxc-debian-wheezy.gz If you want to test the template: Extract the file to /usr/share/lxc/templates , change owner and group to root and make it executable. Create a container with: lxc-create -n wheezy01 -t debian-wheezy Start it: lxc-start -n wheezy01 The generated rootfs reports the container name to the DHCP server. If you happen to to run a combined DHCP/DNS server like dnsmasq this can be used to automatically create a domain-name for the container. (My own setup would create the DNS name wheezy01.freedom.box for the container. Handy for ssh connections...) Rob. http://freedomboxblog.nl /snip -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
