Skip to content
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

vagrant up did not complete #9

Closed
matwu37 opened this issue Mar 21, 2015 · 5 comments
Closed

vagrant up did not complete #9

matwu37 opened this issue Mar 21, 2015 · 5 comments

Comments

@matwu37
Copy link

matwu37 commented Mar 21, 2015

Tried multiple times, everytime it stops at setting the name
or port collison

Any idea how to get it work or what causing the problem?

matthew.wu@X205 ~
$ git clone https://github.com/wckr/wocker.git && cd wocker
Cloning into 'wocker'...
remote: Counting objects: 109, done.
remote: Compressing objects: 100% (6/6), done.
remote: Total 109 (delta 1), reused 0 (delta 0), pack-reused 103
Receiving objects: 100% (109/109), 18.00 KiB | 0 bytes/s, done.
Resolving deltas: 100% (45/45), done.
Checking connectivity... done.

matthew.wu@X205 ~/wocker
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'coreos-stable'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'coreos-stable' is up to date...
==> default: Setting the name of the VM: wocker_default_1426897888404_23903

==> default: Fixed port collision for 22 => 2222. Now on port 2200.

P.S. On Windows 7 with cygwin

@ixkaito
Copy link
Member

ixkaito commented Mar 21, 2015

Did you add "wocker.dev 172.17.8.23" to your hosts-file?

@matwu37
Copy link
Author

matwu37 commented Mar 21, 2015

I do have hostsupdater install? Do I still need to do so?
And do it before vagrant up?

@ixkaito
Copy link
Member

ixkaito commented Mar 22, 2015

I don't know well about vagrant-hostsupdater for Windows. I heard it doesn't work well for Windows.

These issues may help you.
agiledivider/vagrant-hostsupdater#11
kalamuna/kalastack#79

However, I think adding "wocker.dev 172.17.8.23" by yourself is the simplest way.

@matwu37
Copy link
Author

matwu37 commented Mar 26, 2015

I am still having problems at this process, after modifying the host file

==> default: Setting the name of the VM: wocker_default_1426897888404_23903

It's just hangs for a long long time, any idea what causing it?

@ixkaito
Copy link
Member

ixkaito commented Apr 1, 2015

Wocker uses CoreOS on Vagrant. Does the official CoreOS Vagrant work for you?

$ git clone https://github.com/coreos/coreos-vagrant.git && cd coreos-vagrant
$ vagrant up

Please try if this finishes without error, and you can $ vagrant ssh after it.
For more information, please see https://coreos.com/docs/running-coreos/platforms/vagrant/.

ixkaito added a commit that referenced this issue Apr 16, 2015
@ixkaito ixkaito closed this as completed Apr 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants