mirror of
https://github.com/fosrl/docs-v2.git
synced 2026-02-08 05:56:45 +00:00
docs: clarify blueprint behavior with docker
This commit is contained in:
@@ -177,6 +177,10 @@ client-resources:
|
||||
|
||||
For containerized applications, you can define blueprints using Docker labels.
|
||||
|
||||
<Note>
|
||||
Blueprints will **continuously apply** from changes in the docker stack, newt restarting, or when viewing the resource in the dashboard.
|
||||
</Note>
|
||||
|
||||
### Enabling Docker Socket Access
|
||||
|
||||
To use Docker labels, enable the Docker socket when running Newt:
|
||||
@@ -193,6 +197,10 @@ DOCKER_SOCKET=/var/run/docker.sock
|
||||
|
||||
### Docker Compose Example
|
||||
|
||||
<Note>
|
||||
The compose file will be the source of truth, any edits through the resources dashboard will be **overwritten** by the blueprint labels defined in the compose stack.
|
||||
</Note>
|
||||
|
||||
```yaml
|
||||
services:
|
||||
newt:
|
||||
|
||||
Reference in New Issue
Block a user