vagrant/plugins/providers/docker
Paul Hinze 8d46b09a11
Fix Docker machines being lost in go side
By pruning machines that are in "unknown" status after each operation,
the Go code path exposed the fact that the Docker provider was not
updating the machine index during an "up" - leaving the state as
"unknown".

This is basically a bug within the Docker provider, so I think it's okay
to update the plugin code to correct this rather than working around the
issue in Go.

All we need to do is call `machine.state` instead of reaching through to
`machine.provider.state` while waiting for the container to be started.
That causes the extra logic for updating the machine index in
`machine.state` to fire.
2022-07-13 14:04:32 -05:00
..
action Fix Docker machines being lost in go side 2022-07-13 14:04:32 -05:00
cap Add provider capaiblity :has_communicator 2020-06-09 09:33:11 -05:00
command (#9622) Use SafeExec for docker-exec 2018-05-02 14:23:50 -07:00
driver Ensure build_args are passed into docker compose config file 2019-10-07 12:48:59 -07:00
executor Add option for docker executor to handle stderr from results 2019-11-22 12:04:09 -08:00
hostmachine providers/docker: use new b2d box 2015-07-07 16:06:04 -06:00
action.rb Add provider capaiblity :has_communicator 2020-06-09 09:33:11 -05:00
communicator.rb Fixes #9067: Ensure new containers don't grab existing bound ports 2020-05-11 10:17:22 -07:00
config.rb Fixup docker config update 2018-09-19 10:52:59 -07:00
driver.rb Update compose tests to pass fully through Util::Subprocess 2021-07-12 09:54:56 -07:00
errors.rb Enhance docker build matching for determining built container ID 2019-11-19 10:59:28 -08:00
plugin.rb Add provider capaiblity :has_communicator 2020-06-09 09:33:11 -05:00
provider.rb providers/docker: Fix usability check 2019-09-10 15:10:43 -07:00
synced_folder.rb Support Docker volume consistency for synced folders 2018-07-27 15:16:39 -07:00