-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
docker-compose V2? #65
Comments
@dmt0 Vagrant.configure("2") do |config|
config.vm.define "ubuntu" do |ubuntu|
ubuntu.vm.box = "bento/ubuntu-18.04"
config.vm.provider "virtualbox" do |vb|
vb.memory = "4096"
vb.cpus = "1"
end
config.vm.synced_folder "./vagrant_data", "/vagrant", SharedFoldersEnableSymlinksCreate: false
config.vm.provision "docker-compose-setup", type: "shell", preserve_order: true, path: "./vagrant_data/docker/install.sh"
config.vm.provision :docker
config.vm.provision "docker-compose-run", type: "shell",preserve_order: true, :run => 'always', path: "./vagrant_data/docker/run.sh"
ubuntu.trigger.before :destroy, :halt do |trigger|
trigger.info = "Stopping container..."
trigger.run_remote = {inline: "cd /vagrant/docker && docker-compose stop"}
end
end
end the config above should do the same as the plugin, at least it works for me. the install script installs the latest docker-compose version and the run scripts starts the containers on each to fix this problem in the plugin, it is probably enough to updated the value of |
@EricKrg Any chance you might share your "./vagrant_data/docker/run.sh" & "./vagrant_data/docker/run.sh" scripts. Would be helpful. Thanks! |
@evan108108 sure, https://github.com/EricKrg/vagrant-docker-compose-template/blob/main/vagrant_data/docker/run.sh i made a template project for this. There is actually not happening a lot in the run.sh, but you might want to update the install.sh with a current version of docker -compose. |
This doesn't work with V2 any more. The download URL has changed, so it simply can't pull it.
With v2 the URL is
https://github.com/docker/compose/releases/download/v2.11.0/docker-compose-Linux-x86_64
(there's av
in the version. There are probably other issues.If this project is dead, what's the standard way of provisioning docker compose these days?
The text was updated successfully, but these errors were encountered: