adoralaura/personal-website
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

content: remove old blog remnants

Browse source
This commit is contained in:
Adora Laura Kalb 2024-10-10 14:51:10 +02:00
parent 5351f630c6
commit 8027fb87e1
Signed by: adoralaura
SSH key fingerprint: SHA256:3XrkbR8ikAZJVtYfaUliX1MhmJYVAe/ocIb/MiDHBJ8
2 changed files with 0 additions and 30 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
content/blog/2021/issues-with-docker-swarm-on-esxi.md
View file

@ -1,23 +0,0 @@
---
title: "Issues with Docker Swarm on ESXi"
description: "How to make Docker Swarm work with Nodes on ESXi"
publishdate: "2021-04-20"
author: "Adora 🌹"
draft: true
---
I once tried to set up a Docker Swarm Cluster. I had three nodes, two on Proxmox hosts, and one on a ESXi 7 host. The nodes had a GlusterFS storage attached to them which synced data to all three nodes so containers could be started on any node.
Everything worked wonderfully. Until I found out that some Containers couldn't talk to others.
Off to troubleshooting then. It seemed very sporadic, with communication working most of the time somehow. I tried some things, until I found out that it only happens if a container on the ESXi node tried to talk to others on the Proxmox nodes.
After _A LOT_ of googling and searching many a reddit thread I finally found out why:
It seems like ESXi, even when in standalone mode, silently drops packets on `udp/4789`, which apparently is VMWares `VTEP VXLAN Port for NSX-T`.
The fix for the Swarm cluster is to (re-)create the Swarm Cluster with `--data-path-port=xxxx`:
```
docker swarm init --data-path-port=(port that's not 4789)
```
Afterwards all communication works again 🎉

7
content/blog/_index.md
View file

@ -1,7 +0,0 @@
---
title: My Blog 🌸
description: "Lauras Blog about random stuff :3"
---
I'll be posting about random stuff here :3 IT, Politics, Love...
Posts will be in _English_ and in _German_!