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

[proxy] entrypoint and dns not configured with --with-ipam #744

Closed
errordeveloper opened this issue May 27, 2015 · 3 comments
Closed

[proxy] entrypoint and dns not configured with --with-ipam #744

errordeveloper opened this issue May 27, 2015 · 3 comments
Assignees
Milestone

Comments

@errordeveloper
Copy link
Contributor

Looks like proxy should care about withIPAM flag in proxy/create_container_interceptor.go, and it currently doesn't.

Anyways, what user sees is this:

> docker run busybox cat /etc/resolv.conf 
nameserver 10.0.2.3
> docker run -e WEAVE_CIDR= busybox cat /etc/resolv.conf
nameserver 172.17.42.1
@rade rade changed the title [proxy] nameservers are not set when IPAM is enabled [proxy] entrypoint and dns not configured with --with-ipam May 27, 2015
@rade
Copy link
Member

rade commented May 27, 2015

So presumably you ran the proxy with --with-ipam --with-dns?

The more serious issue here is that the entrypoint isn't being set.

@rade rade added this to the 0.11.1 milestone May 27, 2015
@errordeveloper
Copy link
Contributor Author

@rade yes, forgot to mention, I did path both --with-ipam and --with-dns.

@paulbellamy
Copy link
Contributor

Ah yes, the --with-ipam flag is assigning the IP on start, but not setting the entrypoint. Same bug in execs also. Thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants