search

IceWhaleTech / CasaOS

CasaOS - A simple, easy-to-use, elegant open-source Personal Cloud system.
https://casaos.io
Apache License 2.0
25.87k stars 1.41k forks source link

Run CasaOS inside a container #31

Closed FrozenSource closed 2 years ago

FrozenSource commented 2 years ago

Is your feature request related to a problem? Please describe. I Would like to try CasaOS; but wouldn't it be possible to run in from inside a ubuntu based docker container?

Describe the solution you'd like Is it an option to just create a docker file with ubuntu and docker installed; install it through the sh file and then pass the docker socket from the host. Has anybody yet tried this?

Describe alternatives you've considered

Additional context

JohnGuan commented 2 years ago

Theoretically, it should be possible. but we have no plans to make it a Docker container yet.

However, CasaOS is still in its early stages, you can notice that we have "OS" in our name but it is still only installed as a system service in base OS. Because we have a lot of features in the development plan.

But I would love to know why you would like CasaOS to be installed in a container and what features you would like to see in this form.

ddproxy commented 2 years ago

Could, theoretically, run the majority of the stack within a docker stack. Having it this way would enable running it alongside an existing docker cluster or installation without meddling with the host system - and designing the system to be container-based from the get-go may improve portability of the system (to different OS's or to a multi-host like kubernetes installation).

Just, as a concept. I haven't dug into how CasaOS works fundamentally, yet.

tigerinus commented 2 years ago

It'd be nice to consider Docker-in-Docker (DIND) or K8s in Docker (KIND) mode such that all CasaOS' containers are wrapped inside a CasaOS container context.

OR,

consider containerd level containerization for CasaOS as a grouping. Basically you run nerdctl ps to see all containerd based containers, and run docker ps to see all docker based containers.

Either approach above quarantines all CasaOS stuff together so user have a cleaner docker environment for their own use.

I personally prefer first approach (DIND/KIND) so that I can easily spawn a CasaOS instance anywhere without worrying too much about the level of intrusion from CasaOS to my host OS. I can also easy disable CasaOS by simply docker stop or kuberctl scale --replica=0 in one step, and vice versa for enabling. Not to mention it's also much easier for CasaOS dev team to test with DIND/KIND due to the decoupling.

Another benefit of DIND is it make it easier to run CasaOS on Windows with Docker or Mac with Docker. People might run Windows on ZB. A large number of HTPC market is also Windows based. CasaOS should bring the app-ized home server apps to all platforms.

LouvAndTech commented 2 years ago

I would be extremely pleasant to use it alongside an already existing homelab setup. First of all as a container manager (Almost like a portainer) and also as a well thought interface (I love it btw) for a whole home setup. The ability to deploy stack would be useful too.