Add ability to run VM like containers in Cloudron via Sysbox

[Lonkle]

@robi No no, I'm asking, what does this give us in a practical sense and how hard would it be to implement do you think?

[robi]

@lonk maybe read the thread again?

[Lonkle]

@robi So the pro is you can run your own OS completely inside a Docker container?

[robi]

@lonk yes, that was mentioned.

[Lonkle]

@robi So there’s more. But the developers seem against it. Can you tell why?

[robi]

@lonk against it? where does it say that?

[murgero]

@lonk said in Add ability to run VMs in containers in Cloudron via Sysbox:

No no, I'm asking, what does this give us in a practical sense and how hard would it be to implement do you think?

imho - What I can see down the road is the ability for companies to run some applications without the need to officially packaging the app. This can be useful for in-house apps that use parts of the filesystem that is normally read-only for example.

[robi]

@murgero Yes, that is what is meant by the Legacy Apps point above.

[Lonkle]

@robi Does it accomplish this by running another layer on top of the already existing Docker layer then?

[murgero]

@lonk I believe sysbox is a different container engine?

[Lonkle]

@murgero said in Add ability to run VMs in containers in Cloudron via Sysbox:

@lonk I believe sysbox is a different container engine?

Oh, now that I re-look at everything. You're right, I think it's too late for a restructure now.

[robi]

@murgero No.

It's simply a different container runtime.

Docker remains the same, we just tell it to use sysbox vs the default runcby adding --runtime sysbox-runc to the docker command line or default config.

That's it.

Simple.

[murgero]

@robi said in Add ability to run VMs in containers in Cloudron via Sysbox:

container runtime.

isn't that the same thing as engine? Or is docker the engine and containerd is the runtime?

[robi]

@murgero said in Add ability to run VMs in containers in Cloudron via Sysbox:

isn't that the same thing as engine? Or is docker the engine and containerd is the runtime?

No.
Docker Engine is a product name that uses containerd (the container daemon) which relies on runc (run container) which is a CLI tool for spawning and running containers according to the OCI specification.

All have a different abstraction level.

Therefore sysbox-runc is an alternate runc that is more secure and offers all of the above benefits.

Docker Engine and containerd don't change, and accept a parameter to specify which runtime (runc) to use.

[Lonkle]

@robi Thanks for going so much further into detail. Why do you personally want this feature?

[robi]

@lonk Let me count the ways.

1. It makes Cloudron better in so many ways already described above
2. It would let me have a build env in Cloudron
3. It would let me have a VDI in Cloudron via Guacamole
4. It would speed development
5. It would let me run more non-packaged apps more easily
6. It would open other opportunities we haven't even explored yet.

[Lonkle]

@robi said in Add ability to run VMs in containers in Cloudron via Sysbox:

@lonk Let me count the ways.

1. It makes Cloudron better in so many ways already described above
2. It would let me have a build env in Cloudron
3. It would let me have a VDI in Cloudron via Guacamole
4. It would speed development
5. It would let me run more non-packaged apps more easily
6. It would open other opportunities we haven't even explored yet.

Okay, perfect, now why do you think the developer's seem opposed (since those are the pros and if there were no cons, fs anyone would do it)? Time and effort switching infrastructures would be my personal guess.

[robi]

@lonk

1. fear?
2. lack of confidence?
3. not understanding how simple it may be?
4. time looking into it?
5. goto #1

[Lonkle]

@robi Can we help with any of those reasons or is this a vendetta we should give up?

[robi]

@lonk Hard to say, it's been a relatively odd echo chamber in this thread, so without more feedback and clarity of the thinking, it's feeling quite neglected.