New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how to fix error "default: stdin: is not a tty" when using vagrant up #517
Comments
Hi @ricker07 - I'd try a |
Pretty sure this is symptomatic of mitchellh/vagrant#1673, which unfortunately is unresolved. |
thank you guys for your help. sorry for late reply. i'm just beginner in On 8 January 2015 at 12:51, Jeremy Felt notifications@github.com wrote:
|
There is a simple fix for the issue (assuming you don't really need a TTY); essentially you need to remove the |
thanks sir @twisty7867 for the help. :) On 28 April 2015 at 04:48, twisty7867 notifications@github.com wrote:
|
This will be fixed/merged in #633 pending license approval. Thanks all! |
- preconfigures apt to bypass any configured proxy server - runs apt-get update to ensure that the package install triggered by bootstrap_chef.sh comes from the local mirror - an attempt to fix the Vagrant error 'stdin: is not a tty' (see Varying-Vagrant-Vagrants/VVV#517) - fix for a grep pattern so that the proxy server is still inserted into apt's configuration even with the DIRECT pattern for a local mirror
I still have the same error. I am using Mac OS though |
+1 on OSX |
+2 on OSX |
+1 in OSX |
Insert this line in Vagrantfile, was resolved for me. config.ssh.shell = "bash -c 'BASH_ENV=/etc/profile exec bash'" |
@mateuslopesbh that can have some other deleterious effects, according to hashicorp/vagrant#1673 (not necessarily in a VVV context). The code I proposed absolutely fixes this issue, regardless of host OS, for a standard Ubuntu 14.04 install. If anyone continuing to experience this issue could share with me their Vagrantfile and a screen grab of the output during vagrant up, I'll be happy to help troubleshoot. |
Hey @twisty7867, I already have this in my Vagrantfile, and it seems I'm unable to put in your fix in combination with this existing declaration:
I don't know much at all about vagrant or Ruby, and am unsure how to include both your fix and my existing stuff here (which was put there by someone else no longer around)? I tried two blocks (put yours first), and then I get an error that says "fix-no-tty provisioner could not be found"... I tried putting your stuff into this same block, and I get "only of |
The "could not be found" error is because your version of Vagrant is too old. You need at least 1.7 to support a named provisioner. You could edit the first line of my code to look more like the one you pasted, e.g. just copy and past the first line of above and replace the first line of mine with it, changing |
On OSX, and when I |
config.ssh.shell = "bash -c 'BASH_ENV=/etc/profile exec bash'" did it. Thanks |
@nkasvosve 's solution worked for me, just added that line in the Vagrantfile, inside the loop "Vagrant.configure(2) do |config|. Thank you! |
@nkasvosve Thanks.. worked for me... |
@twisty7867 Thank you! It worked for me too. |
In a nutshell, inserting the following line into a
See hashicorp/vagrant#1673 (comment) There is also the possibility to set
See hashicorp/vagrant#1673 (comment) and http://docs.vagrantup.com/v2/vagrantfile/ssh_settings.html On the contrary, the next provisioning script provided by @twisty7867 seems to fix the issue without visible regression as far as I can tell from a very restricted usage.
See http://foo-o-rama.com/vagrant--stdin-is-not-a-tty--fix.html |
@nkasvosve, worked for me. Thanks! |
@thierrymarianne "fix-no-tty" worked for me. Thanks! |
Still the same problem for me too, this fixes the issue:
|
I ve started exploring Hyperledger and i have encountered a problem while installing vagrant. Following is the error i encountered after i used the command - 'vagrant up': ==> default: Running provisioner: shell... What should i do? |
@thierrymarianne thanks for your "fix-no-tty"-snipped. Works very well. Even on OSX. |
@rahulswimmer did you ever find a solution to that problem? I am having the same issue |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This is what i get when i run "vagrant up". i already do everything, line "sudo service mysql restart || true", vagrant hault, vagrant provision, sudo apt-get update, etc. but it doesn't work. please help me, i just want to update my mysql from 5.5 to 5.6 because i'm using laravel framework and the system i'm working on today is required to use mysql version 5.6.
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'laravel/homestead'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'laravel/homestead' is up to date...
==> default: A newer version of the box 'laravel/homestead' is available! You currently
==> default: have version '0.2.0'. The latest is version '0.2.1'. Run
==> default:
vagrant box update
to update.==> default: Setting the name of the VM: Homestead_default_1418261939885_87172
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 80 => 8000 (adapter 1)
default: 3306 => 33060 (adapter 1)
default: 5432 => 54320 (adapter 1)
default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection timeout. Retrying...
default: Warning: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
default: /vagrant => /home/sedp/Homestead
default: /home/vagrant/Projects => /home/sedp/Projects
==> default: Running provisioner: shell...
default: Running: inline script
==> default: stdin: is not a tty
==> default: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCiivZdJRmsEDj0PtfecSxl3g/HOAsmQXh7K4x0LQB5NKONbpO0leFRFJ2lV+iGMasqA45tfF9jGSIxmGsMfmg6VOVkUZ2EWk6tURFfM5FW3DgeL9CLcG4OhTHLyA9AcTHH0BvVml2OWYeXyfM5J8rURbaURZF1qKtjuR2r/JfF1HK0fhgjgnPMfBgkEt77XXMYSfDYxOSY9IhXEr8uNzXRjBWVmB1PNERoOCmodfANjClL8ptbguT+jYgUIFxDbpvm87plT4LzCCo+otoLSgCF+k51mwf0/Y3/IvhuskKdfSEYomRdBVCy19sY5c75oh5f471OFMfAehtFoOYdiRw7 bantonricker07@gmail.com
==> default: Running provisioner: shell...
default: Running: inline script
==> default: Running provisioner: shell...
default: Running: inline script
==> default: stdin: is not a tty
==> default: Running provisioner: shell...
default: Running: inline script
==> default: stdin: is not a tty
==> default: * Restarting nginx nginx
==> default: ...done.
==> default: php5-fpm stop/waiting
==> default: php5-fpm start/running, process 1966
==> default: Running provisioner: shell...
default: Running: inline script
==> default: stdin: is not a tty
==> default: * Restarting nginx nginx
==> default: ...done.
==> default: php5-fpm stop/waiting
==> default: php5-fpm start/running, process 2021
==> default: Running provisioner: shell...
default: Running: inline script
==> default: stdin: is not a tty
==> default: * Restarting nginx nginx
==> default: ...done.
==> default: php5-fpm stop/waiting
==> default: php5-fpm start/running, process 2076
==> default: Running provisioner: shell...
default: Running: inline script
==> default: stdin: is not a tty
==> default: php5-fpm stop/waiting
==> default: php5-fpm start/running, process 2109
The text was updated successfully, but these errors were encountered: