If I have umask 007 (or any other value that masks the world-execute bit)
when I run lxc-start for the first time after logging in, my host system
enters a state with the following problems:
* lxc-stop hangs forever instead of stopping any container, even one that
wasn't started with umask 007.
*
Is there a way to use the new nvidia runtime passthrough feature with plain
lxc containers? That is, without lxd at all? If so, can someone point me
toward a doc on how to do this?
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://li
I have a script that launches a bunch of children in their own namespaces,
and uses lxc-user-nic to attach a veth in each one to lxcbr0.
lxc-user-nic sometimes fails with the following output:
cmd/lxc_user_nic.c: 937: lxc_secure_rename_in_ns: Error -1 renaming netdev
vethP73QDAp to eth%d in conta
Yesterday, I created an unprivileged debian jessie container using the
lxc-provided template, like so:
lxc-create -t download -n debbox -- -d debian -r jessie -a amd64
I replaced systemd with sysvinit-core, since systemd was causing endless
hangs whenever I installed or upgraded packages. The
>We cannot stop or restart
>containers, lxc simply hangs when we try that. Inside containers we get the
>/proc must be mounted error.
Is your umask set to something other than 022? I reported a bug with those
symptoms a few years ago. I don't think it has been fixed.
https://github.com/lxc/lxc/
When I use the ps command's "lxc" format specifier, for example:
ps -eo pid,lxc,command
The second output column is supposed to show "the name of the lxc container
within which a task is running. If a process is not running inside a
container, a dash ('-') will be shown." This worked fine unti
Forest wrote:
>When I use the ps command's "lxc" format specifier, for example:
>
>ps -eo pid,lxc,command
>
>The second output column is supposed to show "the name of the lxc container
>within which a task is running. If a process is not running inside a
&
I am not passing any command line options to lxc-monitor, and its manual
says, "The default is no log." Nevertheless, whenever I run it,
lxc-monitord writes to lxc-monitord.log.
I have tools that regularly use lxc-monitor, and this log file has been
slowly growing in size for who knows how long.
On Sun, 12 Apr 2020 10:51:16 -0500, Serge E. Hallyn wrote:
>On Sat, Apr 11, 2020 at 08:09:56PM -0700, Forest wrote:
>> I am not passing any command line options to lxc-monitor, and its manual
>> says, "The default is no log." Nevertheless, whenever I run it,
>
On Sun, 12 Apr 2020 19:39:05 -0500, Serge E. Hallyn wrote:
>On Sun, Apr 12, 2020 at 10:48:08AM -0700, Forest wrote:
>> On Sun, 12 Apr 2020 10:51:16 -0500, Serge E. Hallyn wrote:
>>
>> >On Sat, Apr 11, 2020 at 08:09:56PM -0700, Forest wrote:
>> >> I am not pas
On Sun, 12 Apr 2020 10:51:16 -0500, Serge E. Hallyn wrote:
>On Sat, Apr 11, 2020 at 08:09:56PM -0700, Forest wrote:
>> I am not passing any command line options to lxc-monitor, and its manual
>> says, "The default is no log." Nevertheless, whenever I run it,
>
I'm trying to get game controllers to work inside an unprivileged container,
without exposing any more host details than necessary. This mostly works:
lxc.mount.entry = /dev/input dev/input none bind,optional,create=dir
lxc.mount.entry = /dev/uinput dev/uinput none bind,optional,create=file
lxc.m
12 matches
Mail list logo
