Closed JasonGiedymin closed 11 years ago
I'm handling this issue now.
Did you grab the box from here: http://storage.core-os.net/coreos/amd64-generic/dev-channel/coreos_production_vagrant.box ?
If you see i made the old Vagrant file v1
and the new base box is set to v2 if you vagrant package --output xxxxv2
I'll re-open the issue until you get it working. Close this once your synced up with the new vagrant box using coreos.
Closing, was able to dl the coreos box last night and boot up.
Closed prematurely as I was still loading raring box on vagrant up.
Running into issues wrapped around permissions with the core user. Did you run into anything like this:
_[default] No guest additions were detected on the base box for this VM! Guest additions are required for forwarded ports, shared folders, host only networking, and more. If SSH fails on this machine, please install the guest additions and repackage the box to continue._
_This is not an error message; everything may continue to work properly, in which case you may ignore this message. [default] Configuring and enabling network interfaces... The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed!_
_sed -e '/^#VAGRANT-BEGIN/,/^#VAGRANT-END/ d' /etc/conf.d/net > /tmp/vagrant-network-interfaces_
_Stdout from the command:_
_Stderr from the command:_
_sed: can't read /etc/conf.d/net: No such file or directory_
When I run it, I do get the stdin errors but I got those with the old box too
The cookbooks all install for me when I do vagrant up
If guest ext aren't installed how do we tell exactly if we were to just ssh to the box and poke around? Maybe coreos does needs the guest stuff installed. My guess is that this box is bare and needs extensions installed. But double check.
-Jason
On Aug 31, 2013, at 9:21 AM, automatelife notifications@github.com wrote:
Closed prematurely as I was still loading raring box on vagrant up.
Running into issues wrapped around permissions with the core user. Did you run into anything like this:
[default] No guest additions were detected on the base box for this VM! Guest additions are required for forwarded ports, shared folders, host only networking, and more. If SSH fails on this machine, please install the guest additions and repackage the box to continue.
This is not an error message; everything may continue to work properly, in which case you may ignore this message. [default] Configuring and enabling network interfaces... The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed!
sed -e '/^#VAGRANT-BEGIN/,/^#VAGRANT-END/ d' /etc/conf.d/net > /tmp/vagrant-network-interfaces
Stdout from the command:
Stderr from the command:
sed: can't read /etc/conf.d/net: No such file or directory
— Reply to this email directly or view it on GitHub.
yeah, same for me with the stdin errors.
I think its a bad error description. I think it boils down to not having a "vagrant" user on the coreos box. Are you able to ssh in as vagrant? If so did you manually add that user or was it built into the box?
With the coreos box I was able to ssh into via vagrant ssh
Hm maybe I can do join.me with you in 30?
-Jason
On Aug 31, 2013, at 9:59 AM, automatelife notifications@github.com wrote:
yeah, same for me with the stdin errors.
I think its a bad error description. I think it boils down to not having a "vagrant" user on the coreos box. Are you able to ssh in as vagrant? If so did you manually add that user or was it built into the box?
— Reply to this email directly or view it on GitHub.
yeah that works, gonna run and grab some breakfast real quick. I'll ping ya once I am back.
CoreOS is based on Ubuntu but it is a stripped down version of the OS. This particular OS is geared for one thing, Docker.
:-)