Dynamic Container Configuration and State¶
Dynamic configuration and state patterns let a VHT 1.x container read configuration provided by the VeeaHub environment and preserve runtime state across container restarts.
Use this pattern when a container needs site-specific settings, generated credentials, mesh-specific values, service URLs, or persistent application state.
Local Workflow¶
- Define the configuration values the container needs.
- Store those values in the VHT 1.x configuration model or a mounted configuration volume.
- Read the configuration from inside the container at runtime.
- Write mutable state to a persistent volume rather than baking it into the image.
- Test restart, stop/start, and backup/restore behavior on a development VeeaHub.
Related Local Pages¶
- An Example to Demonstrate Container Configuration 1.2
- An Example to Demonstrate Volumes 1.2
- An Example to Demonstrate Container Backup and Restore 1.2
- Mesh-enabled Template Example Configuration 1.2
Note
Keep secrets and site-specific values out of the Docker image. Pass them through runtime configuration or generated state.