Refactor Ignite into a client-server model about ignite HOT 9 OPEN

Yes, I know, this design indeed has its limitations. However, at this stage still it's simpler/faster to implement a pure client-based model. In the future we will maybe do client-server.

from ignite.

Is this asking for something like the Docker socket? If so +1 to that

from ignite.

Is this asking for something like the Docker socket? If so +1 to that

maybe. we have been thinking about breaking one part of ignite into a daemonized containerd plugin, which would be very nice, too

from ignite.

My use case is that im wanting to create a simplistic CaaS system using LXC or firecracker vms as isolation between users. LXC and Docker have a socket i can mount into my CaaS service container hence itd be great to have the same for this :)

from ignite.

We might also consider something like gRPC for the client <-> server interaction.

from ignite.

That should also be supportable using unix sockets, as GRPC is over HTTP anyways

from ignite.

Is this issue still being worked on? I was hoping to work on a Golang Ignite client and use it as a library in my project.

from ignite.

@supra08 contribution is welcome!

from ignite.

Oh great! I would love to. It could be of help if I could know how much has been already worked on. Apart from this, what are the expections regarding this issue from weaveworks.

from ignite.