[lxc-users] lxc-users Digest, Vol 56, Issue 1

Thouraya TH thouraya87 at gmail.com
Mon Jan 5 18:56:02 UTC 2015


2015-01-05 13:00 GMT+01:00 <lxc-users-request at lists.linuxcontainers.org>:

> Send lxc-users mailing list submissions to
>         lxc-users at lists.linuxcontainers.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.linuxcontainers.org/listinfo/lxc-users
> or, via email, send a message with subject or body 'help' to
>         lxc-users-request at lists.linuxcontainers.org
>
> You can reach the person managing the list at
>         lxc-users-owner at lists.linuxcontainers.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of lxc-users digest..."
>
> Today's Topics:
>
>    1. Re: lxc-users Digest, Vol 55, Issue 6 (Thouraya TH)
>    2. Re: lxc-users Digest, Vol 55, Issue 6 (Tycho Andersen)
>    3. Snapshot size (Thouraya TH)
>    4. Failure with authorisation of update-manager in Ubuntu
>       Desktop-Container (Guido Jäkel)
>    5. cpu.shares doesn't work (zhen wang)
>    6. Re: Snapshot size (Ashish Bunkar)
>
>
> ---------- Message transféré ----------
> From: Thouraya TH <thouraya87 at gmail.com>
> To: LXC users mailing-list <lxc-users at lists.linuxcontainers.org>
> Cc:
> Date: Sun, 4 Jan 2015 16:26:12 +0100
> Subject: Re: [lxc-users] lxc-users Digest, Vol 55, Issue 6
>
> *Question 1:   lxc-attach didnt' work after restart !! Have you an idea
> please ?*
>
>
>
> *This is a known bug that I have unfortunately not had enough time to look
> into. It is definitely something that needs to be fixed, though :)*
> So, How to access to the container after the dumping process?
>
>
> * Question 3:* i ask what can i do to restart a container on the new
> machine ? i have just to send imgDir to the new machine and run the
> command to restore ? migration to another machine i mean
>
> Thanks a lot for answer.
> Best Regards.
>
>
>
>
> ---------- Message transféré ----------
> From: Tycho Andersen <tycho.andersen at canonical.com>
> To: LXC users mailing-list <lxc-users at lists.linuxcontainers.org>
> Cc:
> Date: Sun, 4 Jan 2015 08:37:23 -0700
> Subject: Re: [lxc-users] lxc-users Digest, Vol 55, Issue 6
> [Can you please reply to the threads instead of the daily digest? It
> would make tracking things in my mailer much easier :)]
>
> On Sun, Jan 04, 2015 at 04:26:12PM +0100, Thouraya TH wrote:
> > *Question 1:   lxc-attach didnt' work after restart !! Have you an idea
> > please ?*
> >
> >
> > *This is a known bug that I have unfortunately not had enough time to
> look
> > into. It is definitely something that needs to be fixed, though :)*
> > So, How to access to the container after the dumping process?
>
> You can ssh to it, or any other network connectivity.
>
> >
> > * Question 3:* i ask what can i do to restart a container on the new
> machine
> > ? i have just to send imgDir to the new machine and run the command to
> > restore ? migration to another machine i mean
>
> You can follow the instructions on my blog post:
> http://tycho.ws/blog/2014/09/container-migration.html
>
> Tycho
>
> > Thanks a lot for answer.
> > Best Regards.
>
> > _______________________________________________
> > lxc-users mailing list
> > lxc-users at lists.linuxcontainers.org
> > http://lists.linuxcontainers.org/listinfo/lxc-users
>
>
>
>
> ---------- Message transféré ----------
> From: Thouraya TH <thouraya87 at gmail.com>
> To: LXC users mailing-list <lxc-users at lists.linuxcontainers.org>
> Cc:
> Date: Sun, 4 Jan 2015 19:42:38 +0100
> Subject: [lxc-users] Snapshot size
> Hello,
>
> On what depends the size of a checkpoint of a container? the size of data that
> are in the container ?
> if i increase the size of data in a container, the snapshot's size
> increase ?
>
> Thanks a lot for answer.
> Best Regards.
>
>
> ---------- Message transféré ----------
> From: "Guido Jäkel" <G.Jaekel at dnb.de>
> To: LXC users mailing-list <lxc-users at lists.linuxcontainers.org>
> Cc:
> Date: Sun, 04 Jan 2015 20:01:15 +0100
> Subject: [lxc-users] Failure with authorisation of update-manager in
> Ubuntu Desktop-Container
> Dear others,
>
> using LXC at work in a server environment for years, this days I start to
> use it at home. My goal here is to set up a Ubuntu Desktop Container
> running on the existing vanilla PC acting as my home server. Up to now it
> was used as a server (router, firewall, NAS, DLNA-server, ...); it was
> managed "nearly headless" via ssh and on a simple VGA text mode console for
> emergencies. For the "Desktop Container" project, i have added a simple 3D
> graphic card and attached an WSXGA-display and a mouse, too.
>
> On the host (running on Gentoo), i have installed LXC 1.0.7 and as the
> container rootfs, I use a copy of one of my already established and
> well-working Ubuntu 14.04 Desktop installations.
>
> To do it step-by-step, i have first started with a "Ubuntu-Server"
> container. With this, i do the basics like a proper network setup. Then, i
> just add a few more lines to the configuration file an switch the rootfs to
> the Desktop clone.
>
>
>         # Template used to create this container:
> /usr/share/lxc/templates/lxc-download
>         # Parameters passed to the template: --no-validate --dist ubuntu
> --release trusty --arch amd64
>         # For additional config options, please look at
> lxc.container.conf(5)
>
>         # Distribution configuration
>         lxc.include = /usr/share/lxc/config/ubuntu.common.conf
>
>         [... usual basic and network setup ...]
>
>         # Desktop-Container: Allow direct access to video and input devices
>         lxc.mount.entry = /dev/dri      dev/dri         none
> bind,optional,create=dir
>         lxc.mount.entry = /dev/input    dev/input       none
> bind,optional,create=dir
>
>         lxc.cgroup.devices.allow = c   4:7 rwm  # /dev/tty7 X Desktop
>         lxc.cgroup.devices.allow = c   4:8 rwm  # /dev/tty8 X Desktop
>         lxc.cgroup.devices.allow = c   4:9 rwm  # /dev/tty9 X Desktop
>         lxc.cgroup.devices.allow = c  29:0 rwm  # /dev/fb0/* framebuffer
> device
>         lxc.cgroup.devices.allow = c 226:* rwm  # /dev/dri/* video card
> devices
>         lxc.cgroup.devices.allow = c  13:* rwm  # /dev/input/* input
> devices
>
>
>
> After a a few tweaks, this already runs very well: I just disabled some
> unnecessary services (avahi, bluetooth, cups, udev, ureadahead) in
> /etc/init/ because they produce a lot of "useless noise".
>
> To get the keyboard and mouse working, before i have to install the
> package  xserver-xorg-input-kbd  and have to add the file
> /etc/X11/xorg.conf.d/10-input.conf  containing
>
>         Section "ServerFlags"
>                 Option "AutoAddDevices" "False"
>         EndSection
>
>         Section "ServerLayout"
>                 Identifier     "Desktop"
>                 InputDevice    "Mouse0" "CorePointer"
>                 InputDevice    "Keyboard0" "CoreKeyboard"
>         EndSection
>
>         Section "InputDevice"
>                 Identifier "Keyboard0"
>                 Driver "kbd"
>                 Option "XkbLayout" "de"
>         EndSection
>
>         Section "InputDevice"
>                 Identifier "Mouse0"
>                 Driver "mouse"
>                 Option "Protocol" "auto"
>                 Option "Device" "/dev/input/mice"
>                 Option "ZAxisMapping" "4 5 6 7"
>         EndSection
>
> Then I was able to interact with the X server and even switch between the
> containers X Desktop and the hosts textmode terminals out of the box.
>
>
>
> But now I stuck at an issue concerning the GUI versions of software
> management: The apt commandline tools work, but the GUI program
> update-manager shows the error message "You are not allowed to perform this
> action" and fail to work. However, if i start it with 'gksudo
> update-manager', there is no such message.
>
> In the same way, the software-manager or other GUI methods to
> install/remove software is not working. May anybody please have a hint what
> might be missing in the container setup or have to be tweaked inside?
>
>
> greetings
>
> Guido
>
>
>
> ---------- Message transféré ----------
> From: zhen wang <wangzhenaaa7 at gmail.com>
> To: lxc-users at lists.linuxcontainers.org
> Cc:
> Date: Mon, 5 Jan 2015 13:35:48 +0800
> Subject: [lxc-users] cpu.shares doesn't work
> I have created two containers using docker.  When i changed  the value of
> cpu.shares in the associated path of the docker id ,and i have already
> substituted -1 in the cpu.cfs_quota_us with 50000,  I tested a program
> ,which doesn't use io, the result of test didn't show the setting of
>  cpu.shares  work. Example :
> i set the cpu.shares 128  in one container and the other 1024 and i run
> the program in the two container concurrently. The time of the program cost
> is almost the same.
> Kernel version 2.6.32-431.
> cpu cores - 2
>
>
> ---------- Message transféré ----------
> From: Ashish Bunkar <ashish.bunkar at oracle.com>
> To: lxc-users at lists.linuxcontainers.org
> Cc:
> Date: Mon, 05 Jan 2015 11:25:13 +0530
> Subject: Re: [lxc-users] Snapshot size
>  Hi
> What is your OS, because in my environment lxc-chekpoint is depreciated
> command now ?
>
> Thanks & Regards
> Ashish Bunkar
> Contact No.- +91-7259183696
>
> Hello, Ubuntu Trusty 14.04 LTS. Have you an idea please about my question ?
Best Regards.


> On 01/05/2015 12:12 AM, Thouraya TH wrote:
>
>  Hello,
>
> On what depends the size of a checkpoint of a container? the size of data that
> are in the container ?
>  if i increase the size of data in a container, the snapshot's size
> increase ?
>
>  Thanks a lot for answer.
>  Best Regards.
>
>
> _______________________________________________
> lxc-users mailing listlxc-users at lists.linuxcontainers.orghttp://lists.linuxcontainers.org/listinfo/lxc-users
>
>
>
> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20150105/a8358c5e/attachment.html>


More information about the lxc-users mailing list