docker + vagrant usually requires you known very well what you are doing. since docker in one end is not meant to be run as a full OS, its meant to run a program.
vagrant in the other end, expect a full OS so can ssh into a do some changes. most of the docker container by default don't start ssh, so vagrant wont be able to login. Alvaro. On Sun, Dec 11, 2016 at 2:50 AM, Asif Iqbal <[email protected]> wrote: > > > On Sat, Dec 10, 2016 at 2:54 PM, Alvaro Miranda Aguilera < > [email protected]> wrote: > >> >> 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: >> > > I am failing to start it. What do I need in the config to start it? > > $ vagrant up --provider docker > Bringing machine 'default' up with 'docker' provider... > ==> default: Vagrant has noticed that the synced folder definitions have > changed. > ==> default: With Docker, these synced folder changes won't take effect > until you > ==> default: destroy the container and recreate it. > ==> default: Starting container... > ==> default: Waiting for machine to boot. This may take a few minutes... > Timed out while waiting for the machine to boot. This means that > Vagrant was unable to communicate with the guest machine within > the configured ("config.vm.boot_timeout" value) time period. > > If you look above, you should be able to see the error(s) that > Vagrant had when attempting to connect to the machine. These errors > are usually good hints as to what may be wrong. > > If you're using a custom box, make sure that networking is properly > working and you're able to connect to the machine. It is a common > problem that networking isn't setup properly in these boxes. > Verify that authentication configurations are also setup properly, > as well. > > If the box appears to be booting properly, you may want to increase > the timeout ("config.vm.boot_timeout") value. > > > I can run it using docker and I get a login. So I must be missing something > in my config? > > $ docker run -it --rm centos > [root@02afb48a009e /]# uname -a > Linux 02afb48a009e 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC > 2016 x86_64 x86_64 x86_64 GNU/Linux > [root@02afb48a009e /]# > > > > >> >> 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 a topic in the >> Google Groups "Vagrant" group. >> To unsubscribe from this topic, visit https://groups.google.com/d/to >> pic/vagrant-up/_EXNsr5NoVg/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To view this discussion on the web visit https://groups.google.com/d/ms >> gid/vagrant-up/CAHqq0ewCZzphe3FnWgM56qDm0D_F2wtzd- >> WUvCjkCqXdcQYmew%40mail.gmail.com >> <https://groups.google.com/d/msgid/vagrant-up/CAHqq0ewCZzphe3FnWgM56qDm0D_F2wtzd-WUvCjkCqXdcQYmew%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Asif Iqbal > PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > > -- > 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/CAOHBbgVc%3DaPrY1N%3DQLBrKMK2CRcC89yD3CnhTkp8Ctz8 > D3yonA%40mail.gmail.com > <https://groups.google.com/d/msgid/vagrant-up/CAOHBbgVc%3DaPrY1N%3DQLBrKMK2CRcC89yD3CnhTkp8Ctz8D3yonA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAHqq0exCRn_eDzP8MYLRvDs_0Gkis0mHD_t6Gad4Syy3hKV9Cg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
