Difference between revisions of "Docker-compose config"
Jump to navigation
Jump to search
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | {{lc}} | ||
| + | <code>[[docker-compose]] config</code> | ||
| + | |||
| + | |||
Added <code>--hash</code> option to the docker-compose config command, allowing users to print a hash string for each service's configuration to facilitate [[rolling updates]]. | Added <code>--hash</code> option to the docker-compose config command, allowing users to print a hash string for each service's configuration to facilitate [[rolling updates]]. | ||
| Line 10: | Line 14: | ||
== See also == | == See also == | ||
* {{docker-compose}} | * {{docker-compose}} | ||
| − | |||
| − | |||
[[Category:Docker]] | [[Category:Docker]] | ||
Latest revision as of 11:54, 10 January 2023
docker-compose config
Added --hash option to the docker-compose config command, allowing users to print a hash string for each service's configuration to facilitate rolling updates.
Related terms[edit]
- CKAD: Understand Deployments and how to perform rolling updates:
kubectl rolling-update
See also[edit]
docker-compose,docker-compose.yml: [services|volumes|networks|up|down|restart|logs|create|changelog|version|secrets|config|-v|-h|exec], docker-compose pull,Environment:, Docker-compose.yml examples,.env, release notes, expose:, docker-compose --env-file,services.deploy.resources
Advertising:
