Kasm - Virtual Desktop / Browser Isolation
-
@robi No, I can see how it can load desktops and such - it's the way the server backend is installed - using multiple different containers that one app can't use on it's own without Cloudron adding a new "addon"
@murgero this sounds like a perfect use case for Sysbox.
That way a full machine image can be installed with Kasm to have access and control over all the containers.
Docker in docker, the outer one managed by Cloudron, the inner one by Kasm.
-
@murgero this sounds like a perfect use case for Sysbox.
That way a full machine image can be installed with Kasm to have access and control over all the containers.
Docker in docker, the outer one managed by Cloudron, the inner one by Kasm.
-
@robi Kasm already supports full desktops in docker - or it at least gives the illusion of it.
-
@murgero I am aware
hence my comment.if you want to split the bounty on this one, I'll help with Sysbox.
-
I would start with the outer part, which means helping the Cloudron team integrate Sysbox.
It would require a new base container image that runs with a new container runtime (sysbox) instead of the default. This is just an extra parameter in the docker run command.
$ docker run --runtime=sysbox-runc -it some-imageAll else stays the same.
In this container, you can now run Systemd, Docker, Kubernetes, etc., just like you would on a physical host or virtual machine. You can launch inner containers (and even inner privileged containers), knowing that the outer container is strongly isolated from the underlying host (via the Linux user-namespace). No more complex docker images or docker run commands, and no need for unsecure privileged containers.
-
I would start with the outer part, which means helping the Cloudron team integrate Sysbox.
It would require a new base container image that runs with a new container runtime (sysbox) instead of the default. This is just an extra parameter in the docker run command.
$ docker run --runtime=sysbox-runc -it some-imageAll else stays the same.
In this container, you can now run Systemd, Docker, Kubernetes, etc., just like you would on a physical host or virtual machine. You can launch inner containers (and even inner privileged containers), knowing that the outer container is strongly isolated from the underlying host (via the Linux user-namespace). No more complex docker images or docker run commands, and no need for unsecure privileged containers.
@robi It would be more ideal to get the Kasm devs to also give a build not reliant on docker - so we can dockerize it ourselfs, or at least I would think that way anyway.
Sysbox is pretty cool but I'm sure that would require a complete overhaul of current code?
-
I am going to disagree here. The docker solution is elegant and doesn't pollute the filesystem with lots of X libraries and other junk.
In fact the sysbox-runc is more secure than the current one, hence if Cloudron decided to use it, all it would take is a one parameter addition.
--runtime=sysbox-runcno overhaul required.
-
I am going to disagree here. The docker solution is elegant and doesn't pollute the filesystem with lots of X libraries and other junk.
In fact the sysbox-runc is more secure than the current one, hence if Cloudron decided to use it, all it would take is a one parameter addition.
--runtime=sysbox-runcno overhaul required.
-
@robi Oh wow - if that's the case then it definitely is at least worth more research and discussion.
-
P plusone-nick referenced this topic on
-
any news on this, I just watched a tutorial video on KASM and it really looks very interesting
-
any news on this, I just watched a tutorial video on KASM and it really looks very interesting
@RazielKanos yep, it's nice.
I have KASM on a separate VPS and it's useful.
In my case, I don't use KASM enough to justify it using a whole VPS.
So it would sure be good to have it in Cloudron as an occasional resource, and get rid of the other VPS. -
I would start with the outer part, which means helping the Cloudron team integrate Sysbox.
It would require a new base container image that runs with a new container runtime (sysbox) instead of the default. This is just an extra parameter in the docker run command.
$ docker run --runtime=sysbox-runc -it some-imageAll else stays the same.
In this container, you can now run Systemd, Docker, Kubernetes, etc., just like you would on a physical host or virtual machine. You can launch inner containers (and even inner privileged containers), knowing that the outer container is strongly isolated from the underlying host (via the Linux user-namespace). No more complex docker images or docker run commands, and no need for unsecure privileged containers.
@robi said in Kasm - Virtual Desktop / Browser Isolation:
I would start with the outer part, which means helping the Cloudron team integrate Sysbox.
It would require a new base container image that runs with a new container runtime (sysbox) instead of the default. This is just an extra parameter in the docker run command.
$ docker run --runtime=sysbox-runc -it some-imageAll else stays the same.
In this container, you can now run Systemd, Docker, Kubernetes, etc., just like you would on a physical host or virtual machine. You can launch inner containers (and even inner privileged containers), knowing that the outer container is strongly isolated from the underlying host (via the Linux user-namespace). No more complex docker images or docker run commands, and no need for unsecure privileged containers.
Thanks. Would this container need any modifications to enable it to run init daemons, like OpenRC, Dinit, s6, runit, SysVinit, and Upstart?
-
Kasm could be a great asset to add to Cloudron for sure.
And, if it would be easier to integrate with Sysbox first on Cloudron, be it known as well that Docker has acquired Sysbox in May 2022. -
I have a VPS running Kasm.
Works very well. But I only use it occasionally so would be great to have it on Cloudron, and I can get rid of a VPS.
Slightly tricky install depending on what version of Ubuntu it runs on and whether it supports some library. But other than that, very nice. -
Yes its a good application but very resource intensive workspace so i hosted it separately but their was a proxy issue and was not working so for the timebeing i used nginx proxy manager but @girish released a patch in the last update 7.60. Now all is good and i am using it withing cloudron and also used cloudron ODIC integration it was long weekend night but well spent.
-
Yes its a good application but very resource intensive workspace so i hosted it separately but their was a proxy issue and was not working so for the timebeing i used nginx proxy manager but @girish released a patch in the last update 7.60. Now all is good and i am using it withing cloudron and also used cloudron ODIC integration it was long weekend night but well spent.
@DualOSWinWiz have any specific docs that would save us some time that you could share?
-
@DualOSWinWiz have any specific docs that would save us some time that you could share?
@plusone-nick What type of infrastructure you have? On site or in cloud?
