On Fri, Jan 24, 2014 at 2:02 AM, Lennart Poettering
wrote:
> On Thu, 23.01.14 11:27, David Timothy Strauss (da...@davidstrauss.net) wrote:
>
>>
>> Has anyone looked at using socketat() for this? It's unclear whether
>> that syscall actually exists in any supported form; it's certainly not
>> docum
On Sat, Jan 18, 2014 at 7:45 AM, Peeters Simon wrote:
> 2014/1/18 Alex Polvi :
>> Hello,
>>
>> Is there a way to have a .socket bind in a particular network
>> namespace? The use case is to have a container with isolated
>> networking be able to start a servi
Hello,
Is there a way to have a .socket bind in a particular network
namespace? The use case is to have a container with isolated
networking be able to start a service, or tunnel to a remote service,
that exists outside the containers namespace.
Thank you for any leads. I could not find anything
We would love to join!
On Aug 12, 2013 8:38 PM, "David Strauss" wrote:
> Are there any plans?
>
> --
> David Strauss
>| da...@davidstrauss.net
>| +1 512 577 5827 [mobile]
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
>
Hello,
TL;DR criu works if you disable the journal and stop the .socket
before restore, criu appears to be incompatible with systemd-nspawn.
I've been "having fun" with systemd, -nspawn, and the latest criu
tools. These are just my research notes. I wanted to share progress,
would love any feedba
Done and done, complete example (with amd64 container) here:
https://github.com/polvi/go-socket-activated-example
-Alex
On Mon, Jun 24, 2013 at 8:46 AM, David Strauss wrote:
> Exciting! You should post this to the systemd group on Google+.
___
syst
Hi, I was tinkering with socket activation in go today, thought I'd
share the working example incase anyone else was interested.
https://gist.github.com/polvi/b4c3aaa59c9b13e0b334
This was based on:
https://gist.github.com/alberts/4640792
(thanks alberts)
Works like a charm! It also worked
