Yeah that allocator should be lazy... If any of you feel like looking at
it, assign to yourself. Otherwise I will do it.

On Thursday, March 28, 2013, Jérôme Petazzoni wrote:

This is probably caused by the IP address allocator. It puts all the
available addresses in a pool when docker starts. I thought that it might
be noticeable with a /8 but I'm surprised that a /16 would cause problems.

Can you please try with different subnet sizes and report the memory usage
of the docker daemon?
On Mar 28, 2013 4:07 AM, "Tamás Gulácsi" <notifications@github.com<javascript:_e({}, 'cvml', 'notifications@github.com');>>
wrote:

If the lxcbr0 interface is configured to 10.65.26.1, for example (
10.65.0.0/16).
If it is 192.168.13.13, then its ok.

—
Reply to this email directly or view it on GitHub<
https://github.com/dotcloud/docker/issues/231>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/231#issuecomment-15598820
.

Docker eats up all memory #231

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions