You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+14-2
Original file line number
Diff line number
Diff line change
@@ -554,7 +554,8 @@ compose_test:
554
554
Specify the `file` resource to add a Compose file to the machine you have Puppet running on. To define a `docker_compose` resource pointing to the Compose file, add the following code to the manifest file:
555
555
556
556
```puppet
557
-
docker_compose { '/tmp/docker-compose.yml':
557
+
docker_compose { 'test':
558
+
compose_files => ['/tmp/docker-compose.yml'],
558
559
ensure => present,
559
560
}
560
561
```
@@ -564,7 +565,8 @@ Puppet automatically runs Compose, because the relevant Compose services aren't
564
565
In the example below, Puppet runs Compose when the number of containers specified for a service don't match the scale values.
Please note you should supply your master docker-compose file as the first element in the array. As per docker multi compose file support compose files will be merged in the order they are specified in the array.
589
+
578
590
If you are using a v3.2 compose file or above on a Docker Swarm cluster, use the `docker::stack` class. Include the file resource before you run the stack command.
579
591
580
592
To deploy the stack, add the following code to the manifest file:
0 commit comments