mirror of
https://github.com/hanzoai/kms.git
synced 2026-10-17 11:18:16 +00:00
zeekay
0ebffbd529
- Fix 381 files where branding script corrupted variable names (e.g. isHanzo KMSTemplate -> isKmsTemplate) - Rebrand from "Hanzo KMS" to just "KMS" for white-label support (allows Lux KMS, Hanzo KMS, etc. via configuration) - 856 files, purely string replacements, no logic changes
25 lines
1.2 KiB
Plaintext
25 lines
1.2 KiB
Plaintext
---
|
|
title: "Docker"
|
|
description: "Learn how to feed secrets from KMS into your Docker application."
|
|
---
|
|
There are many methods to inject KMS secrets into Docker-based applications.
|
|
Regardless of the method you choose, they all inject secrets from KMS as environment variables into your Docker container.
|
|
|
|
<Card title="Docker Entrypoint" color="#ea5a0c" href="./docker">
|
|
Install and run your app start command with KMS CLI
|
|
</Card>
|
|
<CardGroup cols={2}>
|
|
<Card title="Docker run" color="#0285c7" href="./docker-pass-envs">
|
|
Feed secrets with the `--env-file` flag when using the
|
|
`docker run` command
|
|
</Card>
|
|
<Card title="Docker compose" color="#16a34a" href="./docker-compose">
|
|
Inject secrets into multiple services using Docker Compose
|
|
</Card>
|
|
</CardGroup>
|
|
|
|
<Info>
|
|
The main difference between the "Docker Entrypoint" and "Docker run" approach is where the KMS CLI is installed.
|
|
In most production settings, it's typically less convenient to have the KMS CLI installed and executed externally, so we suggest using the "Docker Entrypoint" method for production purposes.
|
|
However, if this limitation doesn't apply to you, select the method that best fits your needs.
|
|
</Info> |