nat process oom-killed

[jnehlmeier]

Description

Using Docker for Mac which uses Linuxkit I noticed that networking inside containers sometimes stop working. Inspecting the console log of Docker for Mac using

cat ~/Library/Containers/com.docker.docker/Data/vms/0/console-ring

reveals that the nat process has been oom-killed:

[440096.569243] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=fdb2d289e1cfce1f2cf7700bd3fa96b7c8a3077588344ba7dfc79106bdcd639a,mems_allowed=0,global_oom,task_memcg=/nat,task=nat,pid=1699,uid=0
[440096.573917] Out of memory: Killed process 1699 (nat) total-vm:5435288kB, anon-rss:4337680kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:9348kB oom_score_adj:1

So maybe you have a memory leak in your code?

Steps to reproduce the issue:

It just happens after some days using Docker for Mac 4.18.0 (104112)

[deitch]

Docker for Mac (d4m) does use linuxkit, but it is just composing containers. I recommend opening an issue with docker.

[jnehlmeier]

@deitch Thanks for your response. Actually I wasn't sure which project is the best to report it. I started here as I assumed the nat process is something linuxkit provides and you might want to verify that there is no memory leak.