Live data from Hacker News

LXC and LXD: a different container story

lwn.net

101–102 of 102 posts

Re: LXC and LXD: a different container story

#101
post #98
post #96

Earlier quoted context omitted.

What mac address restriction is there? One sets them up on their robot interface so things will actually route. You get the assigned mac and use that in your virt ip or bridge settings. Are we talking about something else?

The Robot interface thing is actually relatively new (some years). Before they introduced that, all your IP addresses (and maybe subnets, too?) were delivered to your physical MAC address, period. Wanted to use a VM? Maybe use proxy_arp or some 1:1 NAT. Bridging? Not possible.

I checked my emails. My initial server with them was provisioned at the end of 2009 and it's accompanied by my Robot details. I did have IP aliasing on this bare metal server which also needed the assigned mac from Robot.

Re: LXC and LXD: a different container story

#102

Earlier quoted context omitted.

I can't speak to supporting these, but there are a few vendors that offer k8s in a box for this exact use case. Replicated is the first that comes to my mind. I've used this one as a customer. It worked fine but felt it necessary to do a bit of poking under the hood to help it understand things like our AZs in a private cloud: https://www.replicated.com/kubernetes/

ya I'm sure there are some good options especially nowadays. But now think about getting signoff to use that software at VISA, US Bank, or the US military, for extremely sensitive info. Sometimes its just the policies that limit what tools you can use.

I hear you. I was at one of those banks and everything was miserable. For reference, Mulesoft uses (or use to) use Replicated for one of their products that is popular with banks.
Post reply on HN