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

weave launch-proxy -H unix:///*.sock only works for mounted dirs (e.g. /var/run/weave) #1579

Closed
paulbellamy opened this issue Oct 23, 2015 · 1 comment
Closed

weave launch-proxy -H unix:///*.sock only works for mounted dirs (e.g. /var/run/weave) #1579

paulbellamy opened this issue Oct 23, 2015 · 1 comment
Assignees
@paulbellamy
Labels
chore [component/proxy]
Milestone
1.4.0

Comments

@paulbellamy
Copy link
Contributor

We only mount /var/run/weave into the proxy container, so only sockets under that dir will work, at the moment.
@rade rade changed the title weave launch-proxy -H unix:///foo.sock does not mount /foo.sock weave launch-proxy -H unix:///*.sock only works for mounted dirs (e.g. /var/run/weave) Oct 23, 2015
@rade rade added the chore label Oct 23, 2015
@paulbellamy paulbellamy mentioned this issue Oct 23, 2015
Merged
@rade rade mentioned this issue Oct 23, 2015
Closed
@rade rade modified the milestone: 1.3.0 Oct 29, 2015
@rade
Copy link
Member

rade commented Nov 16, 2015

Due to the dangers of mounting /var/run we should warn when the users specifies a -H that points there, with a suggestion of alternatives, e.g. "create a symlink to /var/run/weave/weave.sock".

@awh awh closed this as completed in #1580 Nov 17, 2015
@bboreham bboreham mentioned this issue Dec 16, 2015
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@paulbellamy paulbellamy

Labels
chore [component/proxy]
Projects
None yet
Milestone
1.4.0
Development

No branches or pull requests
3 participants
@rade @paulbellamy @awh