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

weaveproxy --rewrite-inspect changes docker logs response on unknown container #1523

Closed
bboreham opened this issue Oct 12, 2015 · 1 comment
Closed

weaveproxy --rewrite-inspect changes docker logs response on unknown container #1523

bboreham opened this issue Oct 12, 2015 · 1 comment
Assignees
@paulbellamy
Labels
bug [component/proxy]
Milestone
1.1.2

Comments

@bboreham
Copy link
Contributor 

$ weave launch-router
dd99f2b7fe06ea4fb31a7d31fa43d97b8f6ee2772e8a05e8ae783289a18e63e7
$ weave launch-proxy --rewrite-inspect
4ee8b32c1c05ada648cc00419170faeaa15121ded77ec8dcb68a93ce9457fe70
$ docker logs nosuchcontainer
Error response from daemon: no such id: nosuchcontainer
$ eval `weave env`
$ docker logs nosuchcontainer
Error response from daemon: invalid character 'o' in literal null (expecting 'u')

(same result on weave 1.1.1 and current master)
@rade rade added the bug label Oct 12, 2015
@rade rade added this to the 1.1.2 milestone Oct 12, 2015
@rade
Copy link
Member

rade commented Oct 14, 2015

This does indeed only happen when --rewrite-inspect is specified. Weird.

@paulbellamy paulbellamy mentioned this issue Oct 14, 2015
Merged
@rade rade assigned bboreham and paulbellamy and unassigned bboreham Oct 14, 2015
@rade rade closed this as completed in 0d2ff55 Oct 15, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@paulbellamy paulbellamy

Labels
bug [component/proxy]
Projects
None yet
Milestone
1.1.2
Development

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