docker-py: How to get exit code returned by process running inside container?
My python script uses docker-py to launch a docker container as follows:
client = docker.from_env()
result = client.containers.run(
image="my-prog-image:latest",
command=["/etc/my-prog/configs.ini"],
auto_remove=True,
network_mode="host",
)
As documented docker-py: containers, the client.containers.run(...) method returns container. How can I retrieve exit code returned by my-prog running inside container?
docker dockerpy
asked Jan 2 at 3:45
duong_dajgjaduong_dajgja
1,71411636
add a comment |
My python script uses docker-py to launch a docker container as follows:
client = docker.from_env()
result = client.containers.run(
image="my-prog-image:latest",
command=["/etc/my-prog/configs.ini"],
auto_remove=True,
network_mode="host",
)
As documented docker-py: containers, the client.containers.run(...) method returns container. How can I retrieve exit code returned by my-prog running inside container?
docker dockerpy
asked Jan 2 at 3:45
duong_dajgjaduong_dajgja
1,71411636
add a comment |
My python script uses docker-py to launch a docker container as follows:
client = docker.from_env()
result = client.containers.run(
image="my-prog-image:latest",
command=["/etc/my-prog/configs.ini"],
auto_remove=True,
network_mode="host",
)
As documented docker-py: containers, the client.containers.run(...) method returns container. How can I retrieve exit code returned by my-prog running inside container?
docker dockerpy
asked Jan 2 at 3:45
duong_dajgjaduong_dajgja
1,71411636
My python script uses docker-py to launch a docker container as follows:
client = docker.from_env()
result = client.containers.run(
image="my-prog-image:latest",
command=["/etc/my-prog/configs.ini"],
auto_remove=True,
network_mode="host",
)
As documented docker-py: containers, the client.containers.run(...) method returns container. How can I retrieve exit code returned by my-prog running inside container?
docker dockerpy
docker dockerpy
asked Jan 2 at 3:45
duong_dajgjaduong_dajgja
1,71411636
asked Jan 2 at 3:45
duong_dajgjaduong_dajgja
1,71411636
asked Jan 2 at 3:45
duong_dajgjaduong_dajgja
1,71411636
asked Jan 2 at 3:45
duong_dajgjaduong_dajgja
1,71411636
asked Jan 2 at 3:45
duong_dajgjaduong_dajgja
1,71411636
1,71411636
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
result.wait() should wait for the container to run to completion, then return its exit code.
However, you'll probably hit some trouble with this since you specify auto_remove=True but do not specify detach=True. run() without detach=True will run the container to completion, then the auto_remove=True option will delete the container, and at that point the status code doesn't exist any more. You might split these steps up explicitly:
client = docker.from_env()
container = client.containers.run(
image="my-prog-image:latest",
command=["/etc/my-prog/configs.ini"],
detach=True,
)
result = container.wait()
container.remove()
(In Docker CLI terms, you've done docker run --rm ... and then are trying to find the container's result with docker ps -a, but the container is gone; I suggest changing it to docker run -d ... without --rm, checking the docker ps output, and then manually docker rm the container. Actually, there's even a docker wait CLI command but it's rarely used.)
answered Jan 2 at 11:12
David MazeDavid Maze
14.7k31328
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fstackoverflow.com%2fquestions%2f54000979%2fdocker-py-how-to-get-exit-code-returned-by-process-running-inside-container%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
result.wait() should wait for the container to run to completion, then return its exit code.
However, you'll probably hit some trouble with this since you specify auto_remove=True but do not specify detach=True. run() without detach=True will run the container to completion, then the auto_remove=True option will delete the container, and at that point the status code doesn't exist any more. You might split these steps up explicitly:
client = docker.from_env()
container = client.containers.run(
image="my-prog-image:latest",
command=["/etc/my-prog/configs.ini"],
detach=True,
)
result = container.wait()
container.remove()
(In Docker CLI terms, you've done docker run --rm ... and then are trying to find the container's result with docker ps -a, but the container is gone; I suggest changing it to docker run -d ... without --rm, checking the docker ps output, and then manually docker rm the container. Actually, there's even a docker wait CLI command but it's rarely used.)
answered Jan 2 at 11:12
David MazeDavid Maze
14.7k31328
add a comment |
result.wait() should wait for the container to run to completion, then return its exit code.
However, you'll probably hit some trouble with this since you specify auto_remove=True but do not specify detach=True. run() without detach=True will run the container to completion, then the auto_remove=True option will delete the container, and at that point the status code doesn't exist any more. You might split these steps up explicitly:
client = docker.from_env()
container = client.containers.run(
image="my-prog-image:latest",
command=["/etc/my-prog/configs.ini"],
detach=True,
)
result = container.wait()
container.remove()
(In Docker CLI terms, you've done docker run --rm ... and then are trying to find the container's result with docker ps -a, but the container is gone; I suggest changing it to docker run -d ... without --rm, checking the docker ps output, and then manually docker rm the container. Actually, there's even a docker wait CLI command but it's rarely used.)
answered Jan 2 at 11:12
David MazeDavid Maze
14.7k31328
add a comment |
result.wait() should wait for the container to run to completion, then return its exit code.
However, you'll probably hit some trouble with this since you specify auto_remove=True but do not specify detach=True. run() without detach=True will run the container to completion, then the auto_remove=True option will delete the container, and at that point the status code doesn't exist any more. You might split these steps up explicitly:
client = docker.from_env()
container = client.containers.run(
image="my-prog-image:latest",
command=["/etc/my-prog/configs.ini"],
detach=True,
)
result = container.wait()
container.remove()
(In Docker CLI terms, you've done docker run --rm ... and then are trying to find the container's result with docker ps -a, but the container is gone; I suggest changing it to docker run -d ... without --rm, checking the docker ps output, and then manually docker rm the container. Actually, there's even a docker wait CLI command but it's rarely used.)
answered Jan 2 at 11:12
David MazeDavid Maze
14.7k31328
result.wait() should wait for the container to run to completion, then return its exit code.
However, you'll probably hit some trouble with this since you specify auto_remove=True but do not specify detach=True. run() without detach=True will run the container to completion, then the auto_remove=True option will delete the container, and at that point the status code doesn't exist any more. You might split these steps up explicitly:
client = docker.from_env()
container = client.containers.run(
image="my-prog-image:latest",
command=["/etc/my-prog/configs.ini"],
detach=True,
)
result = container.wait()
container.remove()
(In Docker CLI terms, you've done docker run --rm ... and then are trying to find the container's result with docker ps -a, but the container is gone; I suggest changing it to docker run -d ... without --rm, checking the docker ps output, and then manually docker rm the container. Actually, there's even a docker wait CLI command but it's rarely used.)
answered Jan 2 at 11:12
David MazeDavid Maze
14.7k31328
answered Jan 2 at 11:12
David MazeDavid Maze
14.7k31328
answered Jan 2 at 11:12
David MazeDavid Maze
14.7k31328
answered Jan 2 at 11:12
David MazeDavid Maze
14.7k31328
14.7k31328
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f54000979%2fdocker-py-how-to-get-exit-code-returned-by-process-running-inside-container%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
