Thanks for your input!
On Tue, Jun 13, 2017 at 2:35 AM, Fajar A. Nugraha wrote:
> On Mon, Jun 12, 2017 at 10:22 PM, Christoph Mathys
> wrote:
>>
>> In a test setup, I run an VM with lxd in a NATed network. When I try
>> to copy an image to another server (on the other side of the NAT), it
>> can
On Mon, Jun 12, 2017 at 10:22 PM, Christoph Mathys
wrote:
> In a test setup, I run an VM with lxd in a NATed network. When I try
> to copy an image to another server (on the other side of the NAT), it
> cannot do that because the other server tries to connect to the IP of
> the VM behind the NAT.
In a test setup, I run an VM with lxd in a NATed network. When I try
to copy an image to another server (on the other side of the NAT), it
cannot do that because the other server tries to connect to the IP of
the VM behind the NAT. I tried with portforwarding, but I think I
would also need to tell
I must have missed that part, thank you.
On Mon, Jun 12, 2017 at 2:57 PM, brian mullan
wrote:
> I talked to Lin Sun as she works for IBM here locally and her Kubernetes
> demo actually ran LXD worker nodes instead of Docker.
>
> Matter of fact, she stated in the video that Docker presented vario
I talked to Lin Sun as she works for IBM here locally and her Kubernetes
demo actually ran LXD worker nodes instead of Docker.
Matter of fact, she stated in the video that Docker presented various
problems to IBM that use of LXD/LXC containers resolved.
Brian
If you watch the full video you se
Jeff, there is also the virtlet project [1] that allows you to replace
kubelet with anything libvirt can talk to (haven't tested it).
Brian, the IBM presentation at KubeCon talks about deploying Kubernetes on
top of LXD. I think Jeff was asking for the opposite (lxd as a runtime).
Deploying Kubern
