r/docker • u/neilcresswell Official: Portainer • Dec 09 '25
Docker -> Kubernetes
Hey Docker community..
Many of you run Docker/Podman on your homelabs, in your DC’s and at the edge.. why? Because its lightweight and simple to use..
I know you have all heard of Kubernetes, but feel its overkill for what you need (non-orchestrated container runtime).. So, can I ask you to take a look at KubeSolo.io as an alternate to running Docker/Podman on your single server environments?
KubeSolo is a Kubernetes Distro that is designed exclusively to run on a single server. No clustering, no quorum, no scheduler.. the Kubernetes API (so Helm, CRD’s, CSI’s, CNI’s), but in a single binary and that runs within 200MB of RAM.
Underneath, it runs containerd, so you just need a linux server, install kubesolo and you are done.
KubeSolo was designed for the Industrial Edge, however its picking up adoption in CI pipelines, and as a Docker replacement on standalone Docker host environments. Oh, and its OSS.
Lemme know your thoughts.
5
u/nutlift Dec 09 '25
I havent used KubeSolo yet, I didnt realize it was a portainer product
4
u/neilcresswell Official: Portainer Dec 09 '25
Yup, its a Portainer project.. we want to provide our millions of Docker users a way into Kubernetes without the full on overhead of Kubernetes.
It will always remain OSS, no rug pull… its a project we want to see gain traction as Docker-CE really is lagging behind Kubernetes now, and this gives an easy way forward.
Personally, I have now “deleted” docker from my life (read: homelab) and couldnt be happier.
5
u/nutlift Dec 09 '25
It's a cool idea, although I'm not sure why I would opt into kubernetes single node instead of docker at a homelab level, I will still give it a look!
1
u/neilcresswell Official: Portainer Dec 09 '25
Helm charts… projects like InletsPro, MetalLB, etc.. kube is the way forward, its what the industry has rallied behind. i held out as long as I could, but made the switch myself.
3
u/nutlift Dec 09 '25
I understand the pros of kubernetes I work with it, but for for non-educational homelab purposes it seems overkill in my book.
I have a dev cluster used for learning/breaking but my homelab/selfhosted containers live in docker with good CI/CD. Not to mention Inlets also supports Docker based off of their website.
1
u/neilcresswell Official: Portainer Dec 09 '25
Totally agree.. non-educational, you want something that just works. Last thing you need is the family annoying you as Plex/HASS/PiHole is down. Docker is solid for that.
1
u/Dry_Term_7998 Dec 11 '25
Cri-o plus crictl? 😅 This is another bicycle in k8s world, nothing special
1
u/kwhali Dec 13 '25
What exactly is lagging behind with podman/docker on a single node use-case like you've targeted with KubeSolo?
Is the CLI and config files simpler / terser than podman/docker CLI for trying out containerized services? What if the project only offers an image at a registry? (no convenience like Helm chart from a third-party)
My understanding is I can write compose configs or quadlets rather easily to experiment if there's no suitable equivalent already (such as a github project including one officially to use / modify). Or I can just use the CLI for simple operations and image builds.
My k8s experience is limited, so perhaps I just don't know the ecosystem there that well but there was much more verbosity in configs, it was quite extensible yes but had been lagging behind docker and podman with some features (you still can't set ulimits per service IIRC? Some projects are wary to drop applying
CAP_NET_BINDfile-based capability to their binaries in images due to k8s lagging behind container ecosystem there, only this year did it become default if using containerd). Last I heard, rootless was still experimental with k8s?I also recall I couldn't easily manage the DNS routing between containers, so needed special handling for proxy protocol through ingress controller traffic vs alternative ports without proxy protocol for internal containers connecting to each other directly (in docker compose you can add a network alias that will route it's traffic through your reverse proxy layer for example).
To me k8s was useful for more advanced requirements, often related to managing the deployment with resource usage affecting scaling, better traceability, extensions to use GPU hardware on macOS via containers (podman and docker lack that capability AFAIK), and benefits like that.
Your solution with KubeSolo may reduce overhead, but I assume you're still meant to work with the more verbose config (presumably with some abstraction to simplify that). I don't doubt that there's some advantages for making the switch but I haven't yet found a convincing reason to switch personally to k8s land (that ecosystem is filled with options to choose, KubeSolo is just one of many with pros/cons alongside general learning overhead involved to properly take advantage of the switch in the first place.
I tried KinD recently and found that a bit annoying to get an image I built locally available, it required a manual import step unless I pushed to a registry it could pull from (regardless that's an extra copy on the system?).
3
u/NeoChronos90 Dec 09 '25 edited Dec 11 '25
I think the point in the documentation of KubeSolo, explaining it does NOT make a lot of sense to use it if you have more than 1 GB of RAM available should be mentioned here.
On another note: I don't see any mention of extensions, so I guess it's like k0s, you need to bring your own ingress, helm, etc.?
1
u/neilcresswell Official: Portainer Dec 09 '25
From a CPU/RAM perspective, if you have >1GB RAM, then its technically possible for you to use K3S, K0S etc.. however, KubeSolo still offers significantly lower operational overhead, with no clustering to care about.
And its a straight vanilla distro, so yes, you install any Ingress you prefer..
2
u/sirsavant Dec 10 '25
This looks neat. If this had been around a few years ago earlier into Dokku's history, I would have swapped over to it as a scheduling base (I'm the project maintainer).
1
1
u/SecretSinner Dec 09 '25
I thought the main advantage to running Kubernetes over Docker was the redundancy you get from clustering. What's the advantage of a single-server Kubernetes?
2
u/neilcresswell Official: Portainer Dec 09 '25
Whats the point of a single server docker host? Operational simplicity.. dont think of KubeSolo as “kubernetes”, in a like-for-like, think of it as a way to get Docker that speaks Kubernetes Api.. that was the design goal.
With kubesolo, we are pretty honest in the faq’s where to use it and where to not.. its a niche project, thats for sure.
1
u/Achmo Dec 09 '25
That sounds cool and I am going to give it a try on my home lab. One question if I may, what about more niche scenarios like docker swarm with mixed os? Can this setup be replicated without the complexity of kubeadm or rke2 clusters?
2
u/neilcresswell Official: Portainer Dec 09 '25
Nah, its pure standalone, and Linux.. that said, a single node swarm is easily replaced with kubesolo
1
u/cptsir Dec 09 '25
How’s it compare to minikube?
1
u/neilcresswell Official: Portainer Dec 09 '25
Minikube imitates Kubernetes for local testing, KubeSolo is Kubernetes for small, resource-constrained production environments
1
u/DenZalman Dec 09 '25
what about macos and apple silicon version? we are going to redesign local dev env for our developers using k8s, and looking for a solution for local k8s without much overhead. but our devs are 100% macos users.
2
u/neilcresswell Official: Portainer Dec 09 '25
Looking into it.. at the moment, it doesnt support Apple Containers… it needs containerd to function.
1
u/_Cinnabar_ Dec 09 '25
tbh, sounds really nice, thanks for showing that, I didn't know of it!
currently I'm running ~10 docker containers via compose, so a quite simple setup, but I thought of switching to k3s so I can also use argocd and sync it with a git repo, possibly even use gitlab ci/cd, but that's prob overkill for my usecase (tbh, any version of kubernetes also is)
but this sounds nice, so I could just set it up like normal k8s but only for my single node, have it behave like a docker network within a namespace, slap some shared PVCs in for data storage and design ingresses as I want? 🤔
1
u/neilcresswell Official: Portainer Dec 09 '25
Pretty much… its still Kube, so you may need MetalLB if you want to expose “low” ports… or use the host network.
1
-2
u/Grasume Dec 10 '25
Anything tied to portainer is a No for me
1
u/neilcresswell Official: Portainer Dec 10 '25
Why is that? We try pretty hard to be community centric…
0
u/Grasume Dec 10 '25
Portainer is a poor product that abstracts docker items into terms docker doesnt use. People become too dependent with Click ops that when docker containers break they don't know the basics on how to recover.
1
u/neilcresswell Official: Portainer Dec 10 '25
Cool, and have you used it lately? With all of the GitOps and policy management?
Its widely used in Global2000 enterprises, at massive scale.. ClickOps for non-prod, enforced GitOps for Prod..
1
u/Grasume Dec 10 '25
Nope , too much of a bad taste in my mouth from the beginning. Too many core differences and terminology that I can't see using it for home or where I work.
2
0
Dec 09 '25
[deleted]
3
u/neilcresswell Official: Portainer Dec 09 '25
2
u/neilcresswell Official: Portainer Dec 09 '25
Ok, and with Docker, how do you use HELM charts, install CRD’s? CSI drivers.. Kubernetes is everywhere now, and the industry is really only providing resources for Kube.. its getting harder and harder to avoid it.
If Docker works for you, keep using it.. if you need Kubernetes capabilities, but dont want the overhead, KubeSolo plugs that gap.
4
u/p58i Dec 09 '25
So effectively this only makes sense when you have workloads that are designed to run in k8s.
TBH I barely see this for homelab applications. So if you can run it on bare docker, you should run it on bare docker.
K8s just adds tons of complexity you really don’t want (unless you need the k8s advantages).
2
u/neilcresswell Official: Portainer Dec 09 '25
Correct.. if you have no need to run Kube, my advice remains, dont.
0
Dec 09 '25
[deleted]
1
16
Dec 09 '25
[removed] — view removed comment
5
u/neilcresswell Official: Portainer Dec 09 '25
They are still a full blown cluster, with all of its operation overhead. kubesolo is designed to remove all of that..
2
u/Dry_Term_7998 Dec 11 '25
A little bit but you need all this overhead to yourself also, for learning purpose. If you don’t need this overhead, use swarm or docker-compose…
2
u/Dry_Term_7998 Dec 11 '25
Same here, why we need some compact stuff with “batteries” if all this mini stuff already provided it, want super simple setup talos Linux or Kind also good.

6
u/ergonet Dec 09 '25
Hi Neil, it’s great to have you here and see you engaging with the community.
Ok, this will be a long comment…
I’ll start by stating that I find your post a little bit surprising given the KubeSolo documentation emphasizes that it is designed to fill a gap (total lack of offer) in the edge computing k8 use cases where resource constraints stop you from using K8 and the smaller distros (I.e. embedded devices, gateways, etc with 512MB RAM or less).
This is hardly what most people would call a typical server even in a homelab environment. Of course you can call almost anything a server but the website even says “If your devices have 1GB or more RAM, then standard lightweight Kubernetes distributions such as K3s, K0s, or MicroK8s are generally a better fit.”
That left me wondering: are you actually changing the focus and target use cases of KubeSolo? Or only considering expanding it?
This is a hard ask, but having the CEO talking about the product makes me wonder: can we get a glimpse on the product direction regarding monetization? You did say OSS and not FOSS after all.
What is the pricing model?
Are you going to eventually split KubeSolo on a Community Edition and Business Edition as Portainer? If that’s the case, What could we expect the value added features be?
If it’s not the case, is KubeSolo a loss leader for Portainer? (To centrally manage the isolated edge instances)
Random thoughts:
On the KubeSolo website, I feel you guys have made a good job by keeping it simple but I also feel that you are only targeting people that already understands orchestration and are able proficiently use k8.
You are essentially saying KubeSolo = K8 - (clustering logic, multi-node orchestration). But you don’t get to state what’s actually left functionality wise or what are the advantages (you assume the person already understands it and can subtract - like an expert)
If I may suggest, now that you appear to be targeting a wider audience, you could provide some resources that explain the provided services (for people that understands containers but haven’t used orchestration services).
Keep up the great work.