Re: why lxc and not docker, mailing list?

[Linas Vepstas]

Hi Mark,

The mailing list is ope...@googlegroups.com  and I thought that is where you wrote to start this conversation, before it dropped off and became private. I'm cc'ing it now.

To interested readers:  Mark is trying to take the old Hanson Robotics Eva docker containers, and make them run again. Most of the thread is at https://github.com/opencog/docker/issues/167

If there's anyone out there who is good with blender, ROS, nvidia graphics drivers, docker containers, etc and wants to help get Eva running again ... Mark is your guy.

--linas

On Tue, Feb 8, 2022 at 11:36 PM Mark Wigzell <markw...@gmail.com> wrote:

Hi again, not sure how to CC the mailing list, I guess I didn't pick up on that.

Regarding LXC as a delivery vehicle, point taken, though in all that Docker stuff someone could also easily stuff something.

For the immediate future, I'm going to work in the container because it makes sense to learn everything without docker in the middle of everything.

Later, well, maybe try and stuff things back into Docker. But here is the issue: a Docker container rusts, as you and I both know all too well. 

But an LXC is exactly as you left it. It won't rot and as long as LXC is honoured with at least an upgrade path, you can always get it back. Every last installed package, just as it is intended to be, with a snapshot of the OpenCog stuff building properly. Thats the vision.

Maybe a middle ground will open up when I get there.

Cheers

--Mark

--

Patrick: Are they laughing at us?

Sponge Bob: No, Patrick, they are laughing next to us.