= Small Docker grombolan Bare Metal Server Setup = ![ ](httpswww.redditstatic.com/desktop2x/img/renderTimingPixel.png) Aku ngrancang nggawe kluster Docker Swarm sing siap produksi cilik ing telung server logam kosong. Aku ngarep-arep akun pribadi / umpan balik babagan rasa lara lan sukses ing nyetel penyebaran kasebut. Rekomendasi kaya apa sing digunakake O / S, pola sing bisa migunani, link migunani, lsp matur nuwun sadurunge! RedHat duwe akeh dokumentasi lan dhukungan kanggo Podman, yaiku keluhan OCI lan bisa digunakake karo wadhah tanpa root. Sampeyan uga bisa kanggo njaluk certified ing. Dheweke uga duwe mbangun atom RedHat sing dirancang khusus kanggo dadi wadah Host OS. Nanging, Ubuntu duwe akeh dhukungan pangembang. Gumantung ing arah sing sampeyan aran luwih apik kanggo skenario sampeyan. RedHat uga duwe lisensi dhukungan mandiri gratis nganti 16 server. Sampeyan uga bisa mlebu ing CentOS Stream 8 lan mung luwih dhisik tinimbang RedHat perusahaan linux babagan nganyari, yen sampeyan mung ngindhari lisensi. Dadi ahead saka nganyari duwe kaluwihan lan cacat. Sing paling disenengi babagan RedHat yaiku OS tetep stagnant banget babagan arsitektur. Ubuntu kerep diganti. ** Pandhuan kanggo Kontainer RedHat 8 (Podman httpsaccess.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/building_running_and_managing_containers/index#con_characteristics-of-podman-buildah-and-skopeo_assembly_starting-with-containers ** Pandhuan ing RedHat UBI8, wadhah sing dikembangake dening RedHat kanggo dadi dhasar bangunan sampeyan httpscatalog.redhat.com/software/containers/ubi8-init/5c6aea74dd19c77a158f0892 Aku lagi nggarap swarm 3-debian-node karo ansible dhewe saiki bagean grombolan relatif ora pati penting lan cepet kanggo tangi lan mlaku swarm njupuk alih iptables lan aturan biasa sampeyan ora ditrapake maneh, sampeyan kudu nambah sawetara sing khusus Yen sampeyan ngeculake simpul kanthi alasan apa wae (urip maneh etc), yen wis bali, wadhah sing ditiru sing dipindhah nganggo saluran ora bakal bali dhewe, sampeyan bisa nganyari layanan docker --forceone by one, but that wouldand redo/redistribute the containers, so some requests could be dropped the "hard" part is to set up your cluster-able services (reverse proxies, databases depends on what and how, and that's where you see that a lot of the same problems have been solved for Kubernetes (helper tools, plugins, documentation etc), with swarm you are on your own volumes aren't replicated, you might need glusterfs, nfs etc I’m planning on setting up 3 node clusters for Elasticsearch, RabbitMQ and MariaDB on these servers. We don’t want to use Kubernetes as we are far from experts in setting that up. I was reading that docker swarm will make the deployment easier, but you have brought up some addition issues I need to consider. Maybe going back a step, is it worth the complexity to add docker swarm to the tech stack or just manually setup everything using docker alone? == About Community == Members Online