-
Notifications
You must be signed in to change notification settings - Fork 674
weave status <garbage>
produces 404
#1328
Comments
weave status <garbage>
produces 404
I thought that was pretty intuitive. This was not very intuitive: docker |
I don't understand that last comment. What does that have to do with |
I'm on the client talking to the VM's, I've provisioned 3 machines and then connected them. The last one I provisioned was weave-3, how do I go back to weave-1 without going through docker? i guess I can't is the answer. To me, doing a "weave status weave-1" kind of made sense, but to you it probably doesn't. Anyway, probably I would return "this is an invalid argument" rather than a 404 error of which I thought something was happening, since this is normally an http error and not something I would expect in this case. |
What are you trying to do? What does "go back" mean? Do you want to run
should do the trick. |
Yes, I can do that. But what happens when I want to switch VMs, do I have to re-set my env each time to recognize the new host? or is there a way to put all three VMs in my env so I don’t have to swap environments each time. Forgive my naive question.
|
I really struggle to understand what you are trying to do accomplish. When you say "I have to re-set my env each time", what exactly are you referring to? |
Never mind. Just pointing out something as someone new coming to Weave. |
Well, I'd quite like to understand what it is that you are pointing out :) |
instead of showing '404 page not found' Fixes #1328.
instead of showing '404 page not found' Fixes #1328.
I don't think this command exists, but say I have a swarm as setup in the following example:
http://weave.works/guides/weave-and-docker-platform/chapter3/machine-and-swarm-with-weave-proxy.html
And I run
weave status weave-1
or weave statusweave-2
weave returns:
404 page not found
(the last VM I configured was
weave-3
and from there I can issue weave commands directly. )I am aware that this is not the correct command and that I have to go through Docker, but maybe the message should tell me something to that effect.
The text was updated successfully, but these errors were encountered: