awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-10-06 20:27:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: rewording

Browse Source
This commit is contained in:
Nicolas Hedger
2024-02-28 20:20:39 +01:00
parent 0497c3b49e
commit bb4810470f
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/integrations/platforms/docker-intro.mdx
+7 -7
View File
@@ -1,25 +1,25 @@
--- ---
title: "Docker" title: "Docker"
description: "Learn how to feed secrets from Infisical into your docker application" description: "Learn how to feed secrets from Infisical into your Docker application"
--- ---
There are many methods to inject Infisical secrets to docker-based applications. There are many methods to inject Infisical secrets into Docker-based applications.
Regardless of which method you choose, these methods will inject secrets from Infisical as environment variables into your Docker container. Regardless of the method you choose, they all inject secrets from Infisical as environment variables into your Docker container.
<Card title="Docker Entrypoint" color="#ea5a0c" href="./docker"> <Card title="Docker Entrypoint" color="#ea5a0c" href="./docker">
Install and run your app start command with Infisical CLI Install and run your app start command with Infisical CLI
</Card> </Card>
<CardGroup cols={2}> <CardGroup cols={2}>
<Card title="Docker run" color="#0285c7" href="./docker-pass-envs"> <Card title="Docker run" color="#0285c7" href="./docker-pass-envs">
Feed secrets via `--env-file` flag in docker run command Feed secrets via the `--env-file` flag in the
`docker run` command
</Card> </Card>
<Card title="Docker compose" color="#16a34a" href="./docker-compose"> <Card title="Docker compose" color="#16a34a" href="./docker-compose">
Inject secrets to multiple services using Docker Compose Inject secrets into multiple services using Docker Compose
</Card> </Card>
</CardGroup> </CardGroup>
<Info> <Info>
The main difference between the "Docker Entrypoint" and "Docker run" approach is where the Infisical CLI is installed. The main difference between the "Docker Entrypoint" and "Docker run" approach is where the Infisical CLI is installed.
In most production settings, it's typically inconvenient to have the Infisical CLI installed and executed externally. In most production settings, it's typically less convenient to have the Infisical CLI installed and executed externally, so we suggest using the "Docker Entrypoint" method for production purposes.
As a result, 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. However, if this limitation doesn't apply to you, select the method that best fits your needs.
</Info> </Info>