[lxc-users] lxd in Debian

[P. Lowe]

Why isn't socket activation transparent to the operation of LXD?

Why should LXD care if it was activated by a socket connection or via  
/etc/init.d/lxd? Shouldn't the operation in both cases be the same  
from LXD's (daemon's) point of view?

In one case it's launched like a program, in the other it's launched,  
except a socket connection is then given to it once it starts up, no?

-P. Lowe


Quoting Pierre Couderc <pierre at couderc.eu>:

> Mmm, n'est-ce pas le marteau pour écraser la mouche..?
>
>
>
> On 08/23/2016 10:45 PM, Tycho Andersen wrote:
>> On Tue, Aug 23, 2016 at 08:40:33PM +0000, P. Lowe wrote:
>>> For socket activation of the LXD daemon or socket activation of a  
>>> container?
>> For socket activation of the LXD daemon,
>>
>> https://github.com/lxc/lxd/blob/master/lxd/daemon.go#L866
>>
>> Tycho
>>
>>> -P. Lowe
>>>
>>> Quoting Tycho Andersen <tycho.andersen at canonical.com>:
>>>
>>>> On Tue, Aug 23, 2016 at 04:56:43PM +0000, P. Lowe wrote:
>>>>> Why on earth does lxd depend on "golang-github-coreos-go-systemd-dev"?
>>>>>
>>>>> I'm also wondering, why should lxd even depend on systemd?
>>>> LXD has the capability to be socket activated, this library implements
>>>> a go API for handling the case when it is socket activated.
>>>>
>>>> Tycho
>>>>
>>>>> -P. Lowe
>>>>>
>>>>> Quoting "Fajar A. Nugraha" <list at fajar.net>:
>>>>>
>>>>>> On Tue, Aug 23, 2016 at 3:28 PM, Micky Del Favero  
>>>>>> <micky at mesina.net> wrote:
>>>>>>> Paul Dino Jones <spacefreak18 at brak.space> writes:
>>>>>>>
>>>>>>>> So, i see lxc 2.0 has made it's way into Stretch and Jessie backports,
>>>>>>>> but I don't see any activity on lxd. Is this going to happen in time
>>>>>>>> for the Stretch freeze?
>>>>>>> I've packaged LXD for Jessie (Devuan's, but the same applied  
>>>>>>> to Debian),
>>>>>>> here I've explain what I've do:
>>>>>>> http://micky.it/log/compiling-lxd-on-devuan.html
>>>>>>> https://lists.linuxcontainers.org/pipermail/lxc-users/2016-July/012045.html
>>>>>>> if nobody will package LXD you can do it yourself follow my way.
>>>>>>
>>>>>> I'm confused.
>>>>>>
>>>>>> How did you managed to get it build, when the source from
>>>>>> http://packages.ubuntu.com/xenial-updates/lxd has
>>>>>>
>>>>>> Build-Depends: debhelper (>= 9),
>>>>>>               dh-apparmor,
>>>>>>               dh-golang,
>>>>>>               dh-systemd,
>>>>>>               golang-go,
>>>>>>               golang-go.crypto-dev,
>>>>>>               golang-context-dev,
>>>>>>               golang-github-coreos-go-systemd-dev,
>>>>>>               golang-github-gorilla-mux-dev,
>>>>>>               golang-github-gosexy-gettext-dev,
>>>>>>               golang-github-mattn-go-colorable-dev,
>>>>>>               golang-github-mattn-go-sqlite3-dev,
>>>>>>               golang-github-olekukonko-tablewriter-dev,
>>>>>>               golang-github-pborman-uuid-dev,
>>>>>>               golang-gocapability-dev,
>>>>>>               golang-gopkg-flosch-pongo2.v3-dev,
>>>>>>               golang-gopkg-inconshreveable-log15.v2-dev,
>>>>>>               golang-gopkg-lxc-go-lxc.v2-dev,
>>>>>>               golang-gopkg-tomb.v2-dev,
>>>>>>               golang-goprotobuf-dev,
>>>>>>               golang-petname-dev,
>>>>>>               golang-yaml.v2-dev,
>>>>>>               golang-websocket-dev,
>>>>>>               help2man,
>>>>>>               lxc-dev (>= 1.1.0~),
>>>>>>               pkg-config,
>>>>>>               protobuf-compiler
>>>>>>
>>>>>> and https://packages.debian.org/petname returns zero result?
>>>>>> altlinux's lxd rpm (which I use as starting point for my c6 build) has
>>>>>> similar requirement, and when I tried removing golang-petname-dev
>>>>>> requirement when building for centos, the build failed, so I had to
>>>>>> create a new rpm package for that.
>>>>>>
>>>>>> --
>>>>>> Fajar
>>>>>> _______________________________________________
>>>>>> lxc-users mailing list
>>>>>> lxc-users at lists.linuxcontainers.org
>>>>>> http://lists.linuxcontainers.org/listinfo/lxc-users
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> lxc-users mailing list
>>>>> lxc-users at lists.linuxcontainers.org
>>>>> http://lists.linuxcontainers.org/listinfo/lxc-users
>>>> _______________________________________________
>>>> lxc-users mailing list
>>>> lxc-users at lists.linuxcontainers.org
>>>> http://lists.linuxcontainers.org/listinfo/lxc-users
>>>
>>>
>>>
>>> _______________________________________________
>>> lxc-users mailing list
>>> lxc-users at lists.linuxcontainers.org
>>> http://lists.linuxcontainers.org/listinfo/lxc-users
>> _______________________________________________
>> lxc-users mailing list
>> lxc-users at lists.linuxcontainers.org
>> http://lists.linuxcontainers.org/listinfo/lxc-users
>
> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users