[lxc-users] passthrough of usb 433mHz transceiver

I have a rfxcom 433 mHz transceiver (http://www.rfxcom.com/epages/78165469.sf/nl_NL/?ObjectPath=/Shops/78165469/Products/14103). It is connected via usb and controls some domotica switches on the 433mHz frequency. In the domotica software is shows up as serial device on /dev/ttyUSB0 I can't

Re: [lxc-users] Status: Debian Jessie support for unprivileged containers?

On Tue, Oct 13, 2015 at 4:44 PM, Christian Benke wrote: > On 13 October 2015 at 11:15, Fajar A. Nugraha wrote: >> So bottom line, don't bother unless you're willing to run a >> "frakenstein", unsupported distro. Either retry with stretch and hope >> it works

Re: [lxc-users] Status: Debian Jessie support for unprivileged containers?

On 13 October 2015 at 11:15, Fajar A. Nugraha wrote: > So bottom line, don't bother unless you're willing to run a > "frakenstein", unsupported distro. Either retry with stretch and hope > it works better, or switch to ubuntu. Thanks a lot for the detailed explanation Fajar!

Re: [lxc-users] Status: Debian Jessie support for unprivileged containers?

Le 13/10/2015 11:49, Fajar A. Nugraha a écrit : On Tue, Oct 13, 2015 at 4:44 PM, Christian Benke wrote: On 13 October 2015 at 11:15, Fajar A. Nugraha wrote: So bottom line, don't bother unless you're willing to run a "frakenstein", unsupported distro.

Re: [lxc-users] LXD with LVM backend

On Mon, Oct 12, 2015 at 4:34 PM, Mike McCracken wrote: > Hi, the storage.lvm_vg_name is not a per-container config setting, > it's for the whole daemon. > > You set it using 'lxc config set storage.lvm_vg_name myvolgroup', and > then lxd will use the volume group as

Re: [lxc-users] passthrough of usb 433mHz transceiver

Don't know anything about it, but I'd try stracing the software to see whether there are any EACESS or EPERMs or whether there are any other paths under /dev or /sys which get ENOENT and should be bind-mounted in. Quoting JPS (mail...@jsierink.nl): > I have a rfxcom 433 mHz transceiver >

Re: [lxc-users] Container starts on incorrect runlevel

Thanks Fajar, yes, Debian installed from a template correctly starts on runlevel 2, the default for Debian. Since mine starts on "S" instead, a simple workaround could be to symlink /etc/rcS.d to /etc/rc2.d or, better, just issue "init 2" from an hypothetical rcS.d script. However, I prefer

Re: [lxc-users] LXC 1.1.3 update blocks container startup.

Greetings, Andrey Repin! > I'm trying to upgrade to 1.1.4 right now. It works now. >.< *shrugs* # uname -a; lxc-info --version; lxc-ls -f Linux user.td-art.lan 3.13.0-65-generic #106~precise1-Ubuntu SMP Fri Oct 2 22:07:14 UTC 2015 i686 i686 i386 GNU/Linux 1.1.4 NAME STATEIPV4

Re: [lxc-users] Container starts on incorrect runlevel

On Tue, Oct 13, 2015 at 9:18 PM, Davide Baldini wrote: > Thanks Fajar, > > yes, Debian installed from a template correctly starts on runlevel 2, the > default for Debian. > > Since mine starts on "S" instead, a simple workaround could be to symlink > /etc/rcS.d to

Re: [lxc-users] LXC 1.1.3 update blocks container startup.

Greetings, Serge Hallyn! >> >> >> >> >> What lxc version did you say you were using? >> >> >> >> > >> >> >> >> > Were using - 1.1.2. >> >> >> >> > Then I got an upgrade and my DC didn't came up after a host >> >> >> >> > reboot. >> >> >> >> > Had to roll back to 1.1.2 to recover operation. >> >>

Re: [lxc-users] LXC 1.1.3 update blocks container startup.

Greetings, Serge Hallyn! >> Can we coordinate a session sometime after 18:00Z and look into it in a more >> interactive manner? I'm largely omnipresent in LXC IRC. > We can try to meet up at some point after 18:00 utc tomorrow. Sure, I'm available. I hope it wouldn't be too late of a

[lxc-users] lxc-usernsexec completely unexpected behaviour, reproducible on trunk?

Hello List, I've accidentally destroyed some files due to following unexpected behaviour. Is this also reproducible on trunk? # echo "content" > file # cat file content # lxc-usernsexec -m u:0:851968:65536 -m g:0:851968:65536 -- /bin/echo xxx < file # cat file xxx ent It seems, that the bad