On Fri, Dec 9, 2016 at 5:23 AM, Asif Iqbal <[email protected]> wrote:
> The container started either never left the "stopped" state or
> very quickly reverted to the "stopped" state. This is usually
> because the container didn't execute a command that kept it running,
> and usually indicates a misconfiguration.
>
> If you meant for this container to not remain running, please
> set the Docker provider configuration "remains_running" to "false":
>
> config.vm.provider "docker" do |d|
> d.remains_running = false
> end
>
why you say is failing?
the message says the machine have no command to run so it stopped, so is an
expected result:
The container started either never left the "stopped" state or
very quickly reverted to the "stopped" state. This is usually
because the container didn't execute a command that kept it running,
and usually indicates a misconfiguration.
If you meant for this container to not remain running, please
set the Docker provider configuration "remains_running" to "false":
config.vm.provider "docker" do |d|
d.remains_running = false
end
Alvaro.
--
Alvaro
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ewCZzphe3FnWgM56qDm0D_F2wtzd-WUvCjkCqXdcQYmew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
