#dockerswarm — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #dockerswarm, aggregated by home.social.
-
In this small blog post I want to show my small bash script that can initialize a docker swarm cluster (up to nine nodes) with a user interface (portainer) a reverse proxy (traefik or nginx proxy manager) and a high available storage (syncthing4Swarm).
The docker swarm cluster can also be installed in a "rootless"-mode (user namespace).
https://hostlab.tech/blog/swarmpilot-docker-swarm-cluster-in-one-script
#docker #dockerswarm #traefik #keepalived #nginxproxymanager #syncthing #cluster #tutorial #forgejo
-
pi@pi0:~ $ ansible all -i hosts -m shell -a "docker system prune -a -f --volumes" --become
Just freed up over 1.6 Gigabytes of disk space
That's two years' worth of junk from messing about. 🤣
-
pi@pi0:~ $ ansible all -i hosts -m shell -a "docker system prune -a -f --volumes" --become
Just freed up over 1.6 Gigabytes of disk space
That's two years' worth of junk from messing about. 🤣
-
https://www.portainer.io/blog/cve-2025-68121-and-docker#what-the-vulnerability-is
If you are running Docker Swarm in production today, this vulnerability creates some pressure to address your orchestration strategy.
-
Как развернуть кластер среды общих данных Pilot: от теории к практике с Docker Swarm
Привет, друзья! Сегодня поговорим о кластерном режиме в Pilot – линейке продуктов, на базе которых организуют совместную работу над строительными проектами, сборку и проверку BIM-моделей. Кластерный режим Pilot обеспечивает отказоустойчивость и горизонтальное масштабирование её центрального компонента — Pilot-Server. Для хранения данных в кластере используется PostgreSQL, а для взаимодействия между узлами — Redis. Примечание: На данный момент кластеризация доступна только для Pilot-Server. Pilot-BIM-Server и Pilot-Web-Server работают как отдельные сервисы без возможности горизонтального масштабирования. Какие преимущества мы получаем по сравнению с подходом, где используется один компонент Pilot-Server? 1. Аппаратный сбой на сервере Pilot-Server. При падении машины, на которой расположен единственный экземпляр Pilot-Server, работа пользователей парализуется, никакие действия с системой в режиме онлайн невозможно совершить. При нескольких компонентах на разных серверах, в случае падения одного из них, мгновенно назначается новый активный узел из оставшихся рабочих. Для пользователей это будет кратковременный разрыв соединения, после которого они переподключатся к новому узлу. 2. Обновление ПО. При обновлении Pilot-Server с единственным экземпляром, пользователи не могут подключаться в этот момент. В кластерном режиме обновление можно произвести в режиме “Последовательного обновления”. 3. Рост нагрузки на Pilot-Server. Большое количество запросов к одному компоненту Pilot-Server может превысить пропускную способность одного сервера. В кластерном режиме за счёт нескольких узлов с Pilot-Server нагрузка будет распределяться между ними через балансировщик.
https://habr.com/ru/companies/ascon/articles/1011322/
#pilotbim #pilotice #pilotweb #кластеризация #postgresql #docker #dockerswarm #dockercompose
-
Es gibt scheinbar keine einfache storage Lösung für docker swarm, die, ähnlich wie longhorn, replizierten storage zur Verfügung stellt...
-
Es gibt scheinbar keine einfache storage Lösung für docker swarm, die, ähnlich wie longhorn, replizierten storage zur Verfügung stellt...
-
Hi everyone,
I want to show my small script (SwarmPilot) that I made for initializing a docker swarm cluster (up to 9 nodes) with the following features:
- keepalived: One IP address for the entire cluster
- syncthing: For volume replication between the nodes
- portainer: Web UI Management
- nginx proxy manager: Reverse Proxyhttps://github.com/SuitDeer/SwarmPilot
#keepalived #docker #dockerswarm #syncthing #portainer #nginxproxymanager #opensource #ubuntu
-
I am using a Docker Swarm cluster for my services at home and I am currently testing different storage solutions (volume replication). For that I wanted to test and measure the synchronization time (delay) between my docker swarm nodes.
For that testing I have build SyncWatch
-
I am using a Docker Swarm cluster for my services at home and I am currently testing different storage solutions (volume replication). For that I wanted to test and measure the synchronization time (delay) between my docker swarm nodes.
For that testing I have build SyncWatch
-
In this guide, I will try to explain how to set up a Docker Swarm system that is completely highly available
https://hostlab.tech/blog/docker-swarm-ha-gluster
#docker #dockerswarm #keepalived #nginx #linux #ubuntu #portainer #gluster #glusterfs #tutorial #opensource #highavailability
-
Prosty poradnik pokazujący wykorzystanie #DockerSwarm, który jest znany jako znacznie prostsze narzędzie do orkiestracji kontenerów na serwerze niż #Kubernetes. A to dopiero pierwszy tekst serii artykułów na tym blogu.
https://www.c-sharpcorner.com/article/deploying-your-first-service-on-docker-swarm/
-
I am taking a look at https://docs.docker.com/engine/swarm/ and I don't see any timeouts. Obviously, there are going to be timeouts at the OS layer and such, but it seems like there should be timeouts in #dockerswarm. Do they not exist?
-
I am taking a look at https://docs.docker.com/engine/swarm/ and I don't see any timeouts. Obviously, there are going to be timeouts at the OS layer and such, but it seems like there should be timeouts in #dockerswarm. Do they not exist?
-
Here is my new #minirack !
DeskPi RackMate T1, 2x GeeekPi 10 Inch 2U Rack Mount for Raspberry, MikroTik CSS610-8G-2S+in Network Switch, and DeskPi 7.84-inch Touch Screen.
4xpi5-8gb and 4xpi5 -6gb, 8 total nodes. There is also an additional pi4 running the display.
Running docker swarm with Portainer.
So far my stacks are: CoreDNS, traefik, tailscale, docker-registry, and nextjs dashboard for the display.
-
Here is my new #minirack !
DeskPi RackMate T1, 2x GeeekPi 10 Inch 2U Rack Mount for Raspberry, MikroTik CSS610-8G-2S+in Network Switch, and DeskPi 7.84-inch Touch Screen.
4xpi5-8gb and 4xpi5 -6gb, 8 total nodes. There is also an additional pi4 running the display.
Running docker swarm with Portainer.
So far my stacks are: CoreDNS, traefik, tailscale, docker-registry, and nextjs dashboard for the display.
-
Thanks @jadehopepunk perfect timing!
@ryan @goblin @organvoid
I just did a quick search, this video was pretty good as a quick explainer.. -
Thanks @jadehopepunk perfect timing!
@ryan @goblin @organvoid
I just did a quick search, this video was pretty good as a quick explainer.. -
Hadoop на микросервисах или история одного пет-проекта
Столкнувшись с концепцией Big Data некоторое время назад, у меня возник очевидный вопрос: как это можно «потрогать» своими собственными руками, где и как можно посмотреть программное обеспечение, составляющее данный концепт, разобраться с его конфигурацией, а в силу того, что я являюсь специалистом информационной безопасности, «потыкать в него палочками», провести проверку на предмет защищенности, возможности несанкционированных доступов. Ввиду специфики систем данного рода, их достаточно тяжело развернуть в качестве учебного проекта на собственном персональном компьютере. Используемые в организации программы такого рода, мягко говоря, также не очень предназначены для того, чтобы их «ковыряли», «подламывали» и всячески пытались вывести из штатного режима работы. Представляемый в данной статье проект предназначен для того, чтобы развернуть внутри Docker-контейнеров, распределенных на несколько компьютеров, максимально защищенную среду Hadoop (включающую в себя ПО Ranger и Knox), предоставить доступ к ее интерфейсам для тестирования и настройки. Если кратко, то это все. «Git clone», «docker compose up -d» с некоторыми предварительными настройками и «будет вам счастье». Написанный код (преимущественно shell-скрипты и конфигурация docker) максимально документирован ссылками на ресурсы сети Интернет, откуда это взято и где это все подробно описано. Технологии все общеизвестные, новые паттерны я здесь не изобретал. Если же что-то становится не понятным или docker-контейнеры «не взлетают» с первого раза – придется читать дальше, тут я как раз постараюсь описать все подробнее. Итак, поехали…
-
Anyone know about the #DockerSwarm routing mesh? I can't seem to access containers running on other worker nodes (e.g. when accessing a service proxied through caddy), and the ingress routing doesn't work either. The proxied services work OK on a single node, but apart from ingress published ports never worked.
This stuff is really hard to debug; any pointers appreciated.
-
Anyone know about the #DockerSwarm routing mesh? I can't seem to access containers running on other worker nodes (e.g. when accessing a service proxied through caddy), and the ingress routing doesn't work either. The proxied services work OK on a single node, but apart from ingress published ports never worked.
This stuff is really hard to debug; any pointers appreciated.
-
Finally getting to put some time towards my #homelab again. Scrap the previous work I did at automating #dockerswarm containers and try out #proxmox instead?
I know both have pros and cons and are different tools for different jobs, but I'd love discourse from either side to validate or prevent the choice.
-
@futurebird do you have an old computer or 2 #DockerSwarm
-
@futurebird do you have an old computer or 2 #DockerSwarm
-
I've also been trying to troubleshoot my #Pixelfed instance, specifically the web container. For some reason it's magically decided to crap itself. :jellyfish_angry:
And finally I've been updating my #Docker containers that handle backing up the various databases I am using for my services. :docker:
#selfhost #selfhosting #DockerSwarm #SysAdmin #Linux :linux: :ubuntu:
-
I've also been trying to troubleshoot my #Pixelfed instance, specifically the web container. For some reason it's magically decided to crap itself. :jellyfish_angry:
And finally I've been updating my #Docker containers that handle backing up the various databases I am using for my services. :docker:
#selfhost #selfhosting #DockerSwarm #SysAdmin #Linux :linux: :ubuntu:
-
It's been a busy morning already. I've cleaned up the base of a #resin #3DPrint which I will be using for this #dragon I am also printing out. #3DPrinting #3DPrinter 🐉
I've been working on upgrading my #GitHubEnterprise instance. New settings for #OpenTelemetry (#OTEL) keep getting me. Fingers crossed I have it working now, but we'll see in about 15 minutes. I made sure to get this documented! :github1:
#selfhost #selfhosting #DockerSwarm #SysAdmin #Linux :linux: :ubuntu:
-
It's been a busy morning already. I've cleaned up the base of a #resin #3DPrint which I will be using for this #dragon I am also printing out. #3DPrinting #3DPrinter 🐉
I've been working on upgrading my #GitHubEnterprise instance. New settings for #OpenTelemetry (#OTEL) keep getting me. Fingers crossed I have it working now, but we'll see in about 15 minutes. I made sure to get this documented! :github1:
#selfhost #selfhosting #DockerSwarm #SysAdmin #Linux :linux: :ubuntu:
-
Upgraded my #Hoppscotch, #Excalidraw, #Komga, #Traefik :traefik:, and #UniFi Network Application instances. :docker: :ubuntu:
#selfhost #selfhosted #selfhosting #Linux #Docker #DockerSwarm
-
Upgraded my #Hoppscotch, #Excalidraw, #Komga, #Traefik :traefik:, and #UniFi Network Application instances. :docker: :ubuntu:
#selfhost #selfhosted #selfhosting #Linux #Docker #DockerSwarm
-
So it looks like you can't use --device with #Docker Swarm? 😩 :docker:
#Linux #DockerSwarm :linux:
-
So it looks like you can't use --device with #Docker Swarm? 😩 :docker:
#Linux #DockerSwarm :linux:
-
Just had an interesting chat with #ChatGPT about my #Homelab and the possibility of switching from #Proxmox to #DockerSwarm. 🖥️
After some back and forth, ChatGPT actually recommended migrating to Docker Swarm – it could offer better performance and a more flexible high availability setup. 🔄✨
I’m genuinely impressed by what “trained intelligence” can suggest these days. I’m seriously considering the switch! 🤔
That said, I’d really miss my beloved #ProxmoxBackupServer. 😅
How about you? Do you run #DockerSwarm or stick with Proxmox? Would love to hear from fellow #Homelab enthusiasts! -
Just had an interesting chat with #ChatGPT about my #Homelab and the possibility of switching from #Proxmox to #DockerSwarm. 🖥️
After some back and forth, ChatGPT actually recommended migrating to Docker Swarm – it could offer better performance and a more flexible high availability setup. 🔄✨
I’m genuinely impressed by what “trained intelligence” can suggest these days. I’m seriously considering the switch! 🤔
That said, I’d really miss my beloved #ProxmoxBackupServer. 😅
How about you? Do you run #DockerSwarm or stick with Proxmox? Would love to hear from fellow #Homelab enthusiasts! -
In this guide, I will try to explain how to set up a Docker Swarm system that is completely highly available
https://hostlab.tech/blog/docker-swarm-ha
#docker #dockerswarm #haproxy #nginxproxymanager #portainer #ceph #tutorial #opensource
-
In this guide, I will try to explain how to set up a Docker Swarm system that is completely highly available
https://hostlab.tech/blog/docker-swarm-ha
#docker #dockerswarm #haproxy #nginxproxymanager #portainer #glusterfs #tutorial #opensource
-
Uusi lomarojekti aloitettu: tällä kertaa palvelinten kanssa testailua (ihanaa) ja skaalautuva WordPress-ympäristö Dockerilla, Traefik-välityspalvelimella, MariaDB:llä ja Dockerin Swarm-klusterointiominaisuudella. Konttina on toki ihan vaan "wordpress" eli Apache, eli jotain optimointeja voi vielä tuohon taikoa 😄
Kontit jakautuu automaattisesti usean palvelimen välille (tässä tapauksessa kaksi Hetznerin pilvipalvelinta, toinen toimii managerina ja toinen worker nodena). MariaDB skaalautuu myös ja replicat synkronoi tietonsa keskenään vaikka olisivat eri palvelimilla. Docker Swarm hoitaa tämän automaattisesti.
https://scalewptesti.mikroni.fi pyörii, toki ei varmaan nopein sillä pyynnöt kulkee kolmen palvelimen ja kahden TLS-terminaation läpi sillä palvelimella pyöri jo Caddy. Eli nyt menee pyynnöt Caddy->Traefik->Apache, optimitilanteessa suoraan Traefikille. Ja Caddy-Traefik liikenne on myös HTTPS.
Ihan siisti vehe. Päivityksetkin kontteihin saa rolling updates-periaatteella eli päivitetty kontti päälle ja sitten vanha pois, ei downtimeä.
Ping @rolle kun en suoriltaan osaa sanoa ketä muuta voisi kiinnostaa sysadmin sekoilut.
#WordPress #Docker #Traefik #DockerSwarm #Hetzner #sysadmin ja mitälie risuaitoja löytyy aiheeseen liittyen.
-
Uusi lomarojekti aloitettu: tällä kertaa palvelinten kanssa testailua (ihanaa) ja skaalautuva WordPress-ympäristö Dockerilla, Traefik-välityspalvelimella, MariaDB:llä ja Dockerin Swarm-klusterointiominaisuudella. Konttina on toki ihan vaan "wordpress" eli Apache, eli jotain optimointeja voi vielä tuohon taikoa 😄
Kontit jakautuu automaattisesti usean palvelimen välille (tässä tapauksessa kaksi Hetznerin pilvipalvelinta, toinen toimii managerina ja toinen worker nodena). MariaDB skaalautuu myös ja replicat synkronoi tietonsa keskenään vaikka olisivat eri palvelimilla. Docker Swarm hoitaa tämän automaattisesti.
https://scalewptesti.mikroni.fi pyörii, toki ei varmaan nopein sillä pyynnöt kulkee kolmen palvelimen ja kahden TLS-terminaation läpi sillä palvelimella pyöri jo Caddy. Eli nyt menee pyynnöt Caddy->Traefik->Apache, optimitilanteessa suoraan Traefikille. Ja Caddy-Traefik liikenne on myös HTTPS.
Ihan siisti vehe. Päivityksetkin kontteihin saa rolling updates-periaatteella eli päivitetty kontti päälle ja sitten vanha pois, ei downtimeä.
Ping @rolle kun en suoriltaan osaa sanoa ketä muuta voisi kiinnostaa sysadmin sekoilut.
#WordPress #Docker #Traefik #DockerSwarm #Hetzner #sysadmin ja mitälie risuaitoja löytyy aiheeseen liittyen.
-
First time added A records to a real-world DNS server.
First time added a docker swarm stack with its own services.
First time managed to map the two with a Nginx web server config.
Cool!
-
First time added A records to a real-world DNS server.
First time added a docker swarm stack with its own services.
First time managed to map the two with a Nginx web server config.
Cool!
-
Still knackered. 😭
#Raspberrypi #Clusterhat #DockerSwarm -
I can't convincingly make the argument to my coworkers that kubernetes is worth the added complexity.
But while I like the simplicity of just starting a few containers with docker compose, I would like failing health checks to actually restart the failing container and a better way to update my services.
So now I'm wondering if single node Docker Swarm without the routing mesh is just the right fit.
-
I can't convincingly make the argument to my coworkers that kubernetes is worth the added complexity.
But while I like the simplicity of just starting a few containers with docker compose, I would like failing health checks to actually restart the failing container and a better way to update my services.
So now I'm wondering if single node Docker Swarm without the routing mesh is just the right fit.
-
🛠️ I'm almost done adding Swarm support to https://coolify.io!
It won't be a fully automated installation and configuration process, but I'm currently preparing documentation on how to do it (literally 5 minutes). 🤯 #docker #dockerswarm #buildinpublic
-
🛠️ I'm almost done adding Swarm support to https://coolify.io!
It won't be a fully automated installation and configuration process, but I'm currently preparing documentation on how to do it (literally 5 minutes). 🤯 #docker #dockerswarm #buildinpublic
-
💥 Sale ending, get yours quick! Take advantage of the $9.99 (USD) sale on all my Udemy courses about #Docker, #Kubernetes, Docker for #Nodejs, and #DockerSwarm.
https://www.bretfisher.com/courses/ -
I have a #devops (or what we used to call #sysadmin) question...
I like Docker Swarm for its simplicity and apparent "lightweight" nature. From a user standpoint, you can simply define a set of services and it's not that much of a leap to go from a docker-compose file to a full blown distributed system for a small number f nodes.
The problems are that Docker Swarm only appears to be offered by Docker (tm) and requires the real Docker (tm) stack, as opposed to the solution most distros use today, which is to use podman as a Docker replacement (for many good reasons).
And the fact that Docker is owned by Mirantis, Mirantis's future seems uncertain is good reason not to stay.
Is anyone still using Docker Swarm? If not, do you have a lightweight alternative (not Kubernetes)? I've heard not-great things about Nomad.
I feel like this is a huge missing area in the orchestration landscape.