I have been in search for the perfect docker setup for home lab and production environments when Kubernetes doesn’t really …
[ad_2]
source
I have been in search for the perfect docker setup for home lab and production environments when Kubernetes doesn’t really …
[ad_2]
source
Lorem ipsum dolor sit amet, consectetur.
Hi, thanks for this video, one question, is this a possible way to get a kind of "HA" cross datacenters ? (yes, latency, speed might be a problem) but possible? do i need to open all the ports for ceph and swarm ? THX
Great video!!!!! Tks a lot!
So… after all the configuration of swarm and ceph, i install portainer normally on the first node? that's it?
Maybe a silly question, but what If you have your three docker nodes running on ProxMox with ceph. Can you use the ceph pool in ProxMox in any way for Docker Swarm?
Hey Brandon, what is the app you are using in this video with the SSH sessions?
What is the name of SSH terminal? It is great!
awesome tutorial. I am running a docker swarm as well. But I did an external VM to host and NFS share for the swarm. It works but I worry about hosting a game server as a swarm service, Don't want to loose my server progress.
Honestly i don't really get why you'd want to use swarm, it feels like its on life support and has been deprecated until mirantis bought docker. Almost everyone who wants high availability in their homelab gain so much more knowledge from running k8s that they can apply at their job or job interviews. And everyone else should just use the ha feature of their hypervisor to failover or live-migrate the docker vm in case of failure or maintenance
Hi, great video and nice idea with keepalived. I'm looking to improve my cloud hosting and came very close too using Docker Swarm a few months back, but got stuck on the distributed filesystem. So, microceph looks to fix that hurdle. It would have been good to show an actual deployment of an app but this is really useful, many thanks 🙂
Shared storage is a requirement? My Kubernetes clusters do not have any shared storage. So is this just a requirement for Docker Swarm? Can it be configured without using shared storage and if so, what limitations would it impose?
Curious that you didn't read the line re: "To add a manager node to this swam…" and instead chose to join nodes and then promote them. What do you think is the difference? Even if the results "appear" to be the same.
Is it possible to do the same thing with NFS?
Lost me at keepalive. The vast majority of people would want to run this in a test/production environment with a gateway and internal static IPs in a load balanced scenario instead of failover.
I have worked with swarm on the enterprise a lot and it has serious reliability issues. For smaller cluster sizes like 3 nodes at home it might be fine, but at larger deployments of a couple of dozen nodes the problems start to show, and when you approach 50 or 60 nodes it just bursts at the seams.
But for homelabbing I'm sure it's fine.
Great tutorial! What's the SSH terminal you're using? Looks cool!
First