docker fork/exec /proc/self/exe: cannot allocate memory
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
After a few days, docker fails with errors
docker[8927]: level=error msg="Error running exec in container: execcantrun: Cannot run exec command 34a26 in container 4972e576: [8] System error: fork/exec /proc/self/exe: cannot allocate memoryn"
Docker 1.9.1 (upgrade is not an option)
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 34763 9.3 0.8 10680004 535208 ? Ssl Mar13 1334:17 /usr/bin/docker daemon -H fd:// --insecure-registry=0.0.0.0/0 --log-level=warn --ip-forward=false
See VSZ is almost 10G
free -m
total used free shared buffers cached
Mem: 63012 60128 2883 816 1 6775
-/+ buffers/cache: 53351 9660
Swap: 8191 7581 610
If I restart docker service, the issue goes away until reoccurrence after a few days.
After docker restart, VSZ is around 2G
root 27144 2.4 0.0 1786272 44432 ? Ssl 17:44 4:47 /usr/bin/docker daemon -H fd:// --insecure-registry=0.0.0.0/0 --log-level=warn --ip-forward=false
Anyone seen it or suggestion?
docker fork
edited Mar 24 '17 at 9:02
ilkkachu
63.4k10104181
asked Mar 24 '17 at 2:28
J HJ H
3091310
add a comment |
After a few days, docker fails with errors
docker[8927]: level=error msg="Error running exec in container: execcantrun: Cannot run exec command 34a26 in container 4972e576: [8] System error: fork/exec /proc/self/exe: cannot allocate memoryn"
Docker 1.9.1 (upgrade is not an option)
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 34763 9.3 0.8 10680004 535208 ? Ssl Mar13 1334:17 /usr/bin/docker daemon -H fd:// --insecure-registry=0.0.0.0/0 --log-level=warn --ip-forward=false
See VSZ is almost 10G
free -m
total used free shared buffers cached
Mem: 63012 60128 2883 816 1 6775
-/+ buffers/cache: 53351 9660
Swap: 8191 7581 610
If I restart docker service, the issue goes away until reoccurrence after a few days.
After docker restart, VSZ is around 2G
root 27144 2.4 0.0 1786272 44432 ? Ssl 17:44 4:47 /usr/bin/docker daemon -H fd:// --insecure-registry=0.0.0.0/0 --log-level=warn --ip-forward=false
Anyone seen it or suggestion?
docker fork
edited Mar 24 '17 at 9:02
ilkkachu
63.4k10104181
asked Mar 24 '17 at 2:28
J HJ H
3091310
add a comment |
After a few days, docker fails with errors
docker[8927]: level=error msg="Error running exec in container: execcantrun: Cannot run exec command 34a26 in container 4972e576: [8] System error: fork/exec /proc/self/exe: cannot allocate memoryn"
Docker 1.9.1 (upgrade is not an option)
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 34763 9.3 0.8 10680004 535208 ? Ssl Mar13 1334:17 /usr/bin/docker daemon -H fd:// --insecure-registry=0.0.0.0/0 --log-level=warn --ip-forward=false
See VSZ is almost 10G
free -m
total used free shared buffers cached
Mem: 63012 60128 2883 816 1 6775
-/+ buffers/cache: 53351 9660
Swap: 8191 7581 610
If I restart docker service, the issue goes away until reoccurrence after a few days.
After docker restart, VSZ is around 2G
root 27144 2.4 0.0 1786272 44432 ? Ssl 17:44 4:47 /usr/bin/docker daemon -H fd:// --insecure-registry=0.0.0.0/0 --log-level=warn --ip-forward=false
Anyone seen it or suggestion?
docker fork
edited Mar 24 '17 at 9:02
ilkkachu
63.4k10104181
asked Mar 24 '17 at 2:28
J HJ H
3091310
After a few days, docker fails with errors
docker[8927]: level=error msg="Error running exec in container: execcantrun: Cannot run exec command 34a26 in container 4972e576: [8] System error: fork/exec /proc/self/exe: cannot allocate memoryn"
Docker 1.9.1 (upgrade is not an option)
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 34763 9.3 0.8 10680004 535208 ? Ssl Mar13 1334:17 /usr/bin/docker daemon -H fd:// --insecure-registry=0.0.0.0/0 --log-level=warn --ip-forward=false
See VSZ is almost 10G
free -m
total used free shared buffers cached
Mem: 63012 60128 2883 816 1 6775
-/+ buffers/cache: 53351 9660
Swap: 8191 7581 610
If I restart docker service, the issue goes away until reoccurrence after a few days.
After docker restart, VSZ is around 2G
root 27144 2.4 0.0 1786272 44432 ? Ssl 17:44 4:47 /usr/bin/docker daemon -H fd:// --insecure-registry=0.0.0.0/0 --log-level=warn --ip-forward=false
Anyone seen it or suggestion?
docker fork
docker fork
edited Mar 24 '17 at 9:02
ilkkachu
63.4k10104181
asked Mar 24 '17 at 2:28
J HJ H
3091310
edited Mar 24 '17 at 9:02
ilkkachu
63.4k10104181
asked Mar 24 '17 at 2:28
J HJ H
3091310
edited Mar 24 '17 at 9:02
ilkkachu
63.4k10104181
edited Mar 24 '17 at 9:02
ilkkachu
63.4k10104181
edited Mar 24 '17 at 9:02
ilkkachu
63.4k10104181
63.4k10104181
asked Mar 24 '17 at 2:28
J HJ H
3091310
asked Mar 24 '17 at 2:28
J HJ H
3091310
asked Mar 24 '17 at 2:28
J HJ H
3091310
3091310
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The issue is related to https://github.com/docker/docker/issues/8539 which is resolved in docker 1.10 or later.
There was some issue with docker log driver that resulted in buffer problems specifically for flushing a container's STDOUT.
answered Nov 16 '17 at 0:43
J HJ H
3091310
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f353475%2fdocker-fork-exec-proc-self-exe-cannot-allocate-memory%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The issue is related to https://github.com/docker/docker/issues/8539 which is resolved in docker 1.10 or later.
There was some issue with docker log driver that resulted in buffer problems specifically for flushing a container's STDOUT.
answered Nov 16 '17 at 0:43
J HJ H
3091310
add a comment |
The issue is related to https://github.com/docker/docker/issues/8539 which is resolved in docker 1.10 or later.
There was some issue with docker log driver that resulted in buffer problems specifically for flushing a container's STDOUT.
answered Nov 16 '17 at 0:43
J HJ H
3091310
add a comment |
The issue is related to https://github.com/docker/docker/issues/8539 which is resolved in docker 1.10 or later.
There was some issue with docker log driver that resulted in buffer problems specifically for flushing a container's STDOUT.
answered Nov 16 '17 at 0:43
J HJ H
3091310
The issue is related to https://github.com/docker/docker/issues/8539 which is resolved in docker 1.10 or later.
There was some issue with docker log driver that resulted in buffer problems specifically for flushing a container's STDOUT.
answered Nov 16 '17 at 0:43
J HJ H
3091310
answered Nov 16 '17 at 0:43
J HJ H
3091310
answered Nov 16 '17 at 0:43
J HJ H
3091310
answered Nov 16 '17 at 0:43
J HJ H
3091310
3091310
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f353475%2fdocker-fork-exec-proc-self-exe-cannot-allocate-memory%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
