• 1 Post
  • 2 Comments
Joined 1Y ago
cake
Cake day: Jul 01, 2023

help-circle
rss

To use Docker secrets so that the secrets are encrypted on the host. Using Docker Swarm was the path of least resistance to set up my system monitoring stack.

Docker Compose can use secrets without Swarm, but my understanding is that the those are in plaintext on the host.


Should I stick with Docker Swarm for self-hosting?
Hi! I'm starting out with self-hosting. I was setting up Grafana for system monitoring of my mini-PC. However, I ran into issue of keeping credentials secure in my Docker Compose file. I ended up using Docker Swarm since it was the path of least resistance. I've managed to set up Grafana/Prometheus/Node stack and it's working well. However, before continuing with Docker Swarm, I want to check if this is a good idea or will I potentially dig myself into a corner? Some of the options I've found while searching: - Continue with Docker Swarm and look into automation of stack/swarm in future - Ansible playbook has plugins for Docker Swarm. - Self-hosted vault: I want to avoid hosting my own secret/password manager at the moment. - Kubernetes (k8s / k3s) - *I don't wanna* 😭 - More seriously, I'm actually learning this for work but don't see the point of implementing it at home. The extra overhead doesn't seem worth it for a single node cluster. - ~~Live dangerously - Store crdentials in plaintext. Also use `admin` as password for everything~~ **Edit**: *Most of the services I'm planning on hosting will likely be a single replica service.*
fedilink

Wait, do you know if this still happens?

I have a ticket in our backlog to investigate similar issue with Teams Webhook reporting success but not posting anything.

None of us wanted to look at it so been in our backlog for a whilr