On Mon, 20.04.15 14:15, Spencer Baugh (sba...@catern.com) wrote:
> Lennart Poettering writes:
> > On Mon, 20.04.15 13:01, Spencer Baugh (sba...@catern.com) wrote:
> >> Lennart Poettering writes:
> >> > Hmm, so you say the initial connection does not work but triggers the
> >> > container, but th
Lennart Poettering writes:
> On Mon, 20.04.15 13:01, Spencer Baugh (sba...@catern.com) wrote:
>> Lennart Poettering writes:
>> > Hmm, so you say the initial connection does not work but triggers the
>> > container, but the subsequent one will?
>>
>> Not quite; the initial connection seems to act
On Fri, 17.04.15 23:27, sba...@catern.com (sba...@catern.com) wrote:
> Hi,
>
> I am having trouble with socket-activated containers, where the socket
> is first opened outside the container, on an interface/IP address that
> is then passed in to the container.
>
> In short, when I try to ssh to
--text follows this line--
Hi,
I am having trouble with socket-activated containers, where the socket
is first opened outside the container, on an interface/IP address that
is then passed in to the container.
In short, when I try to ssh to the IP address of the container, the
container is indeed
