[lxc-users] Can I fork a process with stateful stop?

[Yohei Kamitsukasa]

Hello everyone,

I have been trying to use 'lxc stop --stateful' and 'lxc move'.
Can we fork a process and checkpoint the process with a container by 
'lxd stop --stateful'?
Although I used 'lxc exec' and forked a process, I was not able to 
checkpoint the process with a container.

If we can do this, I would appreciate it if you advise me.

Thanks,
Yohei Kamitsukasa
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] proc-sys-fs-binfmt_misc.automount failed

[Fajar A. Nugraha]

On Sat, Sep 3, 2016 at 9:13 PM,   wrote:
> From your
> answer I assume, LXC itself does not need it.

Correct. Your container mounts it, and failed, but most program can
still run fine without it.

> If I install
> "autofs", the error dont go away.

Because autofs (most mount command, actually) doesn't work in lxc.

> I then just disabled and
> masked the service inside the VM - this helped.

Correct. That's a workaround.
On ubuntu lxd containter, there's  proc-sys-fs-binfmt_misc.mount
service, which works fine.

> if I need automount later at some point. BTW, my VMs are
> on ZFS anyways.

If you use lxd (not lxc) with zfs backend, you'd get some level of
storage management (including container disk quota) managed by lxd.
Container creation from a downloaded template will also be instaneous
(since lxd basically just need to run "zfs clone").

lxd can run fine without zfs (it can use btrfs or plain directory
storage backend), but the additional functionality is nice.

> I do not have the competition to decide about security, but
> experts told me, not to use Ubuntu, so I keep plain debian.

I'd say saying "x is more secure than y" without telling the whole
story (e.g. what you're using it for) can be misleading.

For example, from the host perspective (i.e. "can this application
that I run mess up the host"), running containers under ubuntu + lxd
(which uses unprivileged containers by default) is much more secure
than debian + lxc (which uses an old version of lxc, and privileged
containers by default).

> I try to avoid backports, because they caused me at least two
> nightmares in the last weeks ...

There are ways to run lxd (with unpriv) in debian. But since you have
nightmares even with backports, my best advice is to "if you know and
can accept the consequences, stick with what you're most familiar
with"

-- 
Fajar
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] proc-sys-fs-binfmt_misc.automount failed

[webman]

Hi !

Thanks ! I am on the way to migrate my whole it environment away
from windows - so I am new to too many things at the same time.

That I asked about binfmt, was that searching the internet show
up nothing about, binfmt would be used inside LXC at some point
or not and the core message was "failed to load automount".

I try to create a VM for a DMZ inside a firewall machine and
even I am using mono (which MAY use binfmt to make exe programs
easier to use), does not force ME to use binfmt. From your
answer I assume, LXC itself does not need it. If I install
"autofs", the error dont go away. I then just disabled and
masked the service inside the VM - this helped. Will see,
if I need automount later at some point. BTW, my VMs are
on ZFS anyways.

I do not have the competition to decide about security, but
experts told me, not to use Ubuntu, so I keep plain debian.

I try to avoid backports, because they caused me at least two
nightmares in the last weeks ...

Regards,
Manfred


> -Original Message-
> From: lxc-users [mailto:lxc-users-boun...@lists.linuxcontainers.org] On
> Behalf Of Fajar A. Nugraha
> Sent: Saturday, September 03, 2016 12:03 PM
> To: LXC users mailing-list
> Subject: Re: [lxc-users] proc-sys-fs-binfmt_misc.automount failed
> 
> On Sat, Sep 3, 2016 at 1:21 PM,   wrote:
> > Hello !
> >
> > I have a problem with LXC (1.0.6-6+deb8u2, on debian jessie, 8.5, uname
> 3.16.xx).
> 
> If you REALLY have (or want) to use debian jessie, I recommend at
> least use jessie-backports:
> https://packages.debian.org/search?keywords=lxc
> It has lxc-2.0.x which has lots of improvements over 1.0.x.
> 
> > [FAILED] Failed to set up automount Arbitrary Executable File Formats
> File System Automount Point.
> > See 'systemctl status proc-sys-fs-binfmt_misc.automount' for details.
> > Unit proc-sys-fs-binfmt_misc.automount entered failed state.
> 
> Some things, like autofs or loading kernel module, simply doesn't work
> inside a container. Most linux programs can run just fine without it
> though.
> 
> > I do not understand too much of Linux to know, what this means. I just
> created
> > another machine, whith same results. All work done as root.
> 
> A simple google search for "linux binfmt" (or reading the link in
> systemd unit) would've told you a lot. Short version, if you're not
> using wine or qemu user emulation, it should be safe to ignore it.
> 
> If you're "just a user who wants to use linux container", I highly
> recommend you use ubuntu + lxd + zfs instead. Ubuntu has gone a long
> way to integrate lxd/lxc into their distro, including tweaking their
> packages to be more container-friendly.
> 
> --
> Fajar
> ___
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users


___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

[lxc-users] ustuehler's lxc-desktop package

[brian mullan]

Dan

I'd seen that same github on the lxc-desktop by Uwe Stuehler and tried to
figure out how to contact him but had no luck (his email isn't on his
github page).

So I added some info to one of my "issues" I'd created on Uwe's GitHub:
https://github.com/ustuehler/lxc-desktop/issues/12

Assuming what I posted there solves the sticking points he had around
a *pre-start
hook for LXD* to set audio/video devices from the Host into the containers
then that would only leave the effort of creating an lxd template for it
which I don't have any experience with so not sure of how much work that
would be.

Brian
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] proc-sys-fs-binfmt_misc.automount failed

[Fajar A. Nugraha]

On Sat, Sep 3, 2016 at 1:21 PM,   wrote:
> Hello !
>
> I have a problem with LXC (1.0.6-6+deb8u2, on debian jessie, 8.5, uname 
> 3.16.xx).

If you REALLY have (or want) to use debian jessie, I recommend at
least use jessie-backports:
https://packages.debian.org/search?keywords=lxc
It has lxc-2.0.x which has lots of improvements over 1.0.x.

> [FAILED] Failed to set up automount Arbitrary Executable File Formats File 
> System Automount Point.
> See 'systemctl status proc-sys-fs-binfmt_misc.automount' for details.
> Unit proc-sys-fs-binfmt_misc.automount entered failed state.

Some things, like autofs or loading kernel module, simply doesn't work
inside a container. Most linux programs can run just fine without it
though.

> I do not understand too much of Linux to know, what this means. I just created
> another machine, whith same results. All work done as root.

A simple google search for "linux binfmt" (or reading the link in
systemd unit) would've told you a lot. Short version, if you're not
using wine or qemu user emulation, it should be safe to ignore it.

If you're "just a user who wants to use linux container", I highly
recommend you use ubuntu + lxd + zfs instead. Ubuntu has gone a long
way to integrate lxd/lxc into their distro, including tweaking their
packages to be more container-friendly.

-- 
Fajar
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

[lxc-users] proc-sys-fs-binfmt_misc.automount failed

[webman]

Hello !

I have a problem with LXC (1.0.6-6+deb8u2, on debian jessie, 8.5, uname 
3.16.xx).
I am making just the basisc to start: lxc-create.
Creation of the VM works, I gave it a network (which work) and start it.

Then I got this message:

Set hostname to .
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Paths.
[  OK  ] Reached target Encrypted Volumes.
Failed to open /dev/autofs: No such file or directory
Failed to initialize automounter: No such file or directory
[FAILED] Failed to set up automount Arbitrary Executable File Formats File 
System Automount Point.
See 'systemctl status proc-sys-fs-binfmt_misc.automount' for details.
Unit proc-sys-fs-binfmt_misc.automount entered failed state.

Anyway, the machine is running and I log in and follow the message (above):

$ systemctl --failed
  UNIT  LOAD   ACTIVE SUBDESCRIPTION
● proc-sys-fs-binfmt_misc.automount loaded failed failed Arbitrary Executable 
File Formats File System Automount Point

and

$ systemctl status -l proc-sys-fs-binfmt_misc.automount
● proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File 
System Automount Point
   Loaded: loaded (/lib/systemd/system/proc-sys-fs-binfmt_misc.automount; 
static)
   Active: failed (Result: resources)
Where: /proc/sys/fs/binfmt_misc
 Docs: https://www.kernel.org/doc/Documentation/binfmt_misc.txt
   http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems

There are no files below:

/proc/sys/fs/binfmt_misc/

I do not understand too much of Linux to know, what this means. I just created
another machine, whith same results. All work done as root.

I put here all relevant lines of the config file (the network is ok):

lxc.rootfs = /var/lib/lxc/vmtest/rootfs
lxc.include = /usr/share/lxc/config/debian.common.conf
lxc.mount = /var/lib/lxc/vmtest/fstab
lxc.utsname = vmtest
lxc.arch = amd64
lxc.autodev = 1
lxc.kmsg = 0
lxc.tty = 8

Additional to note: There is nothing in the '/var/lib/lxc/vmtest/fstab' file.

Looking at systemd's unit-file, I see a precondition, which is NOT true:
ConditionPathIsReadWrite=/proc/sys/

So, if someone could help, this would be great. It's a bad idea to me,
to continue with this fault (and to not know about the consequences).
Beneth what systemd tells, "Failed to open /dev/autofs: No such file or 
directory"
seems to be the core of the problem.

BTW, did exact the same on another jessie (same versions), same result
and there seems to be no apparmor or selinux on my computers.

Thanks anyway and best regards,
Manfred




___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users