-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
vbox: Ubuntu 16.04 (Inappropriate ioctl for device) #665
Comments
Hello, We're going to need a bit more detail to assist here. That bug, iirc, was related to issues with a specific Vagrant version. Perhaps you could post a bit more complete log and provider the version of the box you are using ( |
Hello, i will do my best to give you more informations. The message comes up everytime like this:
But it is unrealted to the provision shell-script because it happend everytime on every script!
I installed it today. Can you tell me which other logs you need and where to find them? |
What version of virtualbox and vagrant please? (just to verify the CLI output as vbox doesn't always uninstall properly) |
Latest virtualbox-extension is also installed. |
Try with the latest boxes (2.3.0) which is built with Vbox 5.1 |
It still happens with the new version (==> default: mesg: ttyname failed: Inappropriate ioctl for device) I also get sometimes "==> default: dpkg-preconfigure: unable to re-open stdin: No such file or directory" e.g. while insalling kibana:
|
Sometimes in this "format":
|
Have you tried upgrading to vagrant 1.8.6? I'm not sure what the other error has to do with this if anything. The error related to stdin is likely coming from the shell provisioner commands as you aren't passing |
Thx for your reply. Upgrading to vagrant 1.8.6 did not change this. I will have a look at the second part soon. |
Have this issue too on MacOS X Sierra
This is log of vagrant up:
Some first vagrant up && restart was successful, but now I can't up my box during this error. |
Hmm, I had this sometimes when destroying-vm and provision it again. It seems that "exports" under "/etc/exports" were not cleared correctly. After removing anything from there and rebooting my mac it works again. I don't think your "mesg: ttyname failed: Inappropriate ioctl for device" is related to the nfs error. |
@SebTM thank you! I just cleaned /etc/exports on my mac and restart it. After I tried to start vagrant and it stucked yet with the same logs... |
So can I consider this closed as it's external to bento? |
I think, my issue consider to vagrant 1.8.6 because after I reverted it to 1.8.5 and reinit my box I can't replay it. Tnx all! |
@cheeseplus I can't test at the moment if the problem is solved by downgrading vagrant |
Closing this one as it doesn't seem specific to the bento boxes, more vagrant configuration and NFS. Feel free to open another issue if it's something specific to a bento build. |
Funny, Vagrant says just the opposite. hashicorp/vagrant#7155 It seems to me like they are saying "bento is doing it right," but I am seeing that other people have had the same issue even with the bento boxes. |
this happens to me when i call scripts with #!/usr/bin/env bash instead of #!/bin/bash s.vm.provision :shell, path: "scripts/sbin/bootstrap.sh" if the shebang in this bootstrap.sh file is #!/usr/bin/env bash then i can reproduce the above error with Inappropriate ioctl for device on my MBP |
I had the "mesg: ttyname failed: Inappropriate ioctl for device" issue with Vagrant 1.9.1 but it was fixed by upgrading to 1.9.4, in case anyone is googling this. |
Nope, 1.9.7, still happening |
Vagrant.configure("2") do |config|
+ config.ssh.shell="bash"
config.vm.box = "ubuntu/xenial64"
config.vm.provider "virtualbox" do |v|
v.customize [ "modifyvm", :id, "--memory", 2048 ]
v.customize [ "modifyvm", :id, "--cpus", 2 ]
end solves this for me on mac os x. |
Hello,
i still get "==> default: mesg: ttyname failed: Inappropriate ioctl for device" everytime vagrant starts a provision-script. I have the latest vagrant-version 1.8.5 on Mac OS X El Capitan.
Can I solve this?
Thanks!
The text was updated successfully, but these errors were encountered: