The documentation mentioned that instead of using docker, vagrant can also support docker-compose as a provider.
compose (boolean) - If true, Vagrant will use docker-compose to manage the lifecycle and configuration of containers. This defaults to false.
compose_configuration (Hash) - Configuration values used for populating the docker-compose.yml file. The value of this Hash is directly merged and written to the docker-compose.yml file allowing customization of non-services items like networks and volumes.
But maybe my understanding is incorrect, maybe it only means internally a docker-compose is used, but if one has multiple containers, they all have to be config-ed separately?
I'm confused and I can't find an example anywhere. You seemed to have looked into this, do you happen to know whether a docker-compose file can be used a provider?
If yes, can one do the following too?
use shell provisioner with the containers defined inside the docker-compose file. How to refer those containers by vagrant names?
enable ssh in the docker image;
use ansible provisoner with the containers defined inside the docker-compse file.
use the compose-configuration hash to merge with docker-compose file.
The documentation mentioned that instead of using docker, vagrant can also support docker-compose as a provider.
But maybe my understanding is incorrect, maybe it only means internally a docker-compose is used, but if one has multiple containers, they all have to be config-ed separately?
I'm confused and I can't find an example anywhere. You seemed to have looked into this, do you happen to know whether a docker-compose file can be used a provider?
If yes, can one do the following too?
use shell provisioner with the containers defined inside the docker-compose file. How to refer those containers by vagrant names?
enable ssh in the docker image;
use ansible provisoner with the containers defined inside the docker-compse file.
use the compose-configuration hash to merge with docker-compose file.