tsuru-bootstrap error

21 views
Skip to first unread message

Julio Lima

unread,
Oct 2, 2017, 2:46:19 PM10/2/17
to tsuru
Hi

I was trying to install tsuru by tsuru-bootstrap and I've got the following error:
==> default: Cloning into 'tsuru-dashboard'...
==> default: ~/tsuru-dashboard ~ ~
==> default: HEAD is now at ec9bdae Merge pull request #137 from raphaabrasil/
new-login-page
==> default: Already up-to-date.
==> default: Warning: Permanently added '192.168.50.4' (ECDSA) to the list of known hosts.
==> default: remote: HEAD is now at ec9bdae... Merge pull request #137 from raphaabrasil/new-login-page
==> default: remote: Error in scheduler after previous errors (unable to start node containers: API error (400): {"message":"Conflict. The container name \"/big-sibling\" is already in use by container \"600267ae6ffb46bad94553a76a19ed9df334c6faa95dbcf766a184db44a127ae\". You have to remove (or rename) that container to be able to reuse that name."}
==> default: remote:
==> default: remote: [node containers] failed to create container in http://127.0.0.1:2375 [theonepool]
==> default: remote: github.com/tsuru/tsuru/provision/docker/nodecontainer.ensureContainersStarted.func1
==> default: remote:     /home/travis/gopath/src/github.com/tsuru/tsuru/provision/docker/nodecontainer/nodecontainer.go:96
==> default: remote: github.com/tsuru/tsuru/provision/docker/nodecontainer.ensureContainersStarted.func2
==> default: remote:     /home/travis/gopath/src/github.com/tsuru/tsuru/provision/docker/nodecontainer/nodecontainer.go:104
==> default: remote: runtime.goexit
==> default: remote:     /home/travis/.gimme/versions/go1.8.3.linux.amd64/src/runtime/asm_amd64.s:2197) trying to create container: error in scheduler: No nodes found with one of the following metadata: pool=theonepool
==> default: To git@192.168.50.4:tsuru-dashboard.git
==> default:  ! [remote rejected] master -> master (pre-receive hook declined)
==> default: error: failed to push some refs to 'g...@192.168.50.4:tsuru-dashboard.git'
The SSH command responded with a non-zero exit status. Vagrant
assumes that
this means the command failed. The output for this command
should be
in the log above. Please read the output to determine what
went wrong
.


I'm using virtualbox as provider.

Any ideas on what is going on?

Thanks!
Julio

Guilherme Garnier

unread,
Oct 19, 2017, 9:45:03 AM10/19/17
to tsuru
Hi Julio. Could you try installing with tsuru installer? https://docs.tsuru.io/stable/experimental/installer.html#installer
Reply all
Reply to author
Forward
0 new messages