Compare commits

..

No commits in common. "098cbca3c3519d19fbdad10f0a344eff3bed9ebc" and "5351f630c619ed1d3a7dd56dbebadaef2b1ab672" have entirely different histories.

3 changed files with 33 additions and 3 deletions

View file

@ -0,0 +1,23 @@
---
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 Normal file
View file

@ -0,0 +1,7 @@
---
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_!

View file

@ -1,4 +1,4 @@
Contact: mailto:security@lila.network Contact: mailto:security@lauka.net
Expires: 2034-10-10T21:59:00.000Z Expires: 2033-08-08T21:59:00.000Z
Preferred-Languages: en, de Preferred-Languages: en, de
Canonical: https://adora.codes/.well-known/security.txt Canonical: https://www.lauka.net/.well-known/security.txt