Skip to content

-vaultHetzner

Vault is running on hetzner-services-stable-1 and 2 as docker. hashicorp/vault:1.15

git place:

[

github.com

https://github.com/Attracs/docker-hashicorp-vault

](https://github.com/Attracs/docker-hashicorp-vault)

we have docker-compose-1.yml for server (hetzner-services-stable-1) docker-compose-2.yml for server (hetzner-services-stable-2)

in the docker we have: docker hetzner-vault: at version 1.15 docker:haproxy:2.9 The haproxy service uses the haproxy:2.9 Docker image to provide a load balancer for the Vault service. The container is named hetzner-vault-haproxy and binds port 80 inside the container to port 4100 on the host IP 10.0.1.5. This allows external traffic to be routed through HAProxy.

A volume is mounted to provide HAProxy's configuration files from the host directory /opt/hashicorp_vaults/vault_stable/configuration to the container's /usr/local/etc/haproxy directory. Like the hetzner-vault service, this container is set to always restart and uses the gcplogs logging driver with the same project ID and label.

This configuration sets up a secure and scalable environment for running HashiCorp Vault with HAProxy as a load balancer. The use of external volumes ensures data persistence, while the logging configuration centralizes logs in Google Cloud Platform for monitoring and troubleshooting. The setup is tailored for a specific network (10.0.1.5) and integrates well with external configuration files and environment variables