Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

weave status <garbage> produces 404 #1328

Closed
abuehrle opened this issue Aug 18, 2015 · 8 comments
Closed

weave status <garbage> produces 404 #1328

abuehrle opened this issue Aug 18, 2015 · 8 comments
Assignees
Labels
Milestone

Comments

@abuehrle
Copy link
Contributor

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 status weave-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.

@rade rade changed the title Message on weave status when running a swarm and on a different virtual machine weave status <garbage> produces 404 Aug 18, 2015
@rade rade added the chore label Aug 18, 2015
@abuehrle
Copy link
Contributor Author

I thought that was pretty intuitive. This was not very intuitive:

docker docker-machine config --swarm weave-1 info

@rade
Copy link
Member

rade commented Aug 18, 2015

I don't understand that last comment. What does that have to do with weave status?

@abuehrle
Copy link
Contributor Author

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.

@rade
Copy link
Member

rade commented Aug 18, 2015

how do I go back to weave-1

What are you trying to do? What does "go back" mean? Do you want to run weave status on weave-1?

DOCKER_CLIENT_ARGS="$(docker-machine config weave-1)" weave status

should do the trick.

@abuehrle
Copy link
Contributor Author

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.

On Aug 18, 2015, at 4:20 PM, Matthias Radestock [email protected] wrote:

how do I go back to weave-1

What are you trying to do? What does "go back" mean? Do you want to run weave status on weave-1?

DOCKER_CLIENT_ARGS="$(docker-machine config weave-1)" weave status
should do the trick.


Reply to this email directly or view it on GitHub #1328 (comment).

@rade
Copy link
Member

rade commented Aug 18, 2015

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?

@abuehrle
Copy link
Contributor Author

Never mind. Just pointing out something as someone new coming to Weave.

@rade
Copy link
Member

rade commented Aug 18, 2015

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 :)

@rade rade self-assigned this Aug 20, 2015
rade added a commit that referenced this issue Aug 20, 2015
instead of showing '404 page not found'

Fixes #1328.
@rade rade removed the in progress label Aug 20, 2015
rade added a commit that referenced this issue Aug 20, 2015
instead of showing '404 page not found'

Fixes #1328.
@awh awh closed this as completed in #1335 Aug 20, 2015
@rade rade modified the milestone: 1.1.0 Aug 29, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants