Keeping container alive with Docker Python SDK












0















I am using the Docker Sdk for Python to run my container.



I am trying to start a docker container, and then run a command using the api exec_run (I need the exit code).
The exec_run needs to be executed on a started container.



This is my code:



import docker



client = docker.from_env()

container = client.containers.run('e7d8452ce5f5', command="echo starting", detach=True)

container.exec_run("echo execute command")


This raises an exception:



docker.errors.APIError: 409 Client Error: Conflict ("Container b65acd40f589819f490564dcb4e25f3055d85712cb7b2834ede5f2c4d57f2da6 is not running")


I tried running with no command when invoking client.containers.run, same exception..



Seems the container exists when the command is finished, even though in their documentation it is stated that the command run with detach=True is same as the cli docker run -d (when using docker run -d the container stays alive)



Any ideas on how to keep the container alive in order to call exec_run on it?






python docker







share|improve this question























  • Your container stops because the command you use, i.e. echo starting doesn't keep running. Why don't you try with a command like bash or sh?

    – tgogos
    Nov 28 '18 at 11:11






  • 1





    ...or just launching the container with the actual command you want to run?

    – David Maze
    Nov 28 '18 at 11:28











  • Tried running sh -- same thing happens

    – dana racah
    Nov 28 '18 at 11:33











  • I can't launch it with the actual command because I need the exit code and run doesn't return it.. Only exec_run

    – dana racah
    Nov 28 '18 at 11:34






  • 1





    If you try with sh you also need to use the -t and -i options of the docker run command. Not using them will make sh exit immediately too.

    – tgogos
    Nov 28 '18 at 11:43
















0















I am using the Docker Sdk for Python to run my container.



I am trying to start a docker container, and then run a command using the api exec_run (I need the exit code).
The exec_run needs to be executed on a started container.



This is my code:



import docker



client = docker.from_env()

container = client.containers.run('e7d8452ce5f5', command="echo starting", detach=True)

container.exec_run("echo execute command")


This raises an exception:



docker.errors.APIError: 409 Client Error: Conflict ("Container b65acd40f589819f490564dcb4e25f3055d85712cb7b2834ede5f2c4d57f2da6 is not running")


I tried running with no command when invoking client.containers.run, same exception..



Seems the container exists when the command is finished, even though in their documentation it is stated that the command run with detach=True is same as the cli docker run -d (when using docker run -d the container stays alive)



Any ideas on how to keep the container alive in order to call exec_run on it?






python docker







share|improve this question























  • Your container stops because the command you use, i.e. echo starting doesn't keep running. Why don't you try with a command like bash or sh?

    – tgogos
    Nov 28 '18 at 11:11






  • 1





    ...or just launching the container with the actual command you want to run?

    – David Maze
    Nov 28 '18 at 11:28











  • Tried running sh -- same thing happens

    – dana racah
    Nov 28 '18 at 11:33











  • I can't launch it with the actual command because I need the exit code and run doesn't return it.. Only exec_run

    – dana racah
    Nov 28 '18 at 11:34






  • 1





    If you try with sh you also need to use the -t and -i options of the docker run command. Not using them will make sh exit immediately too.

    – tgogos
    Nov 28 '18 at 11:43














0












0








0








I am using the Docker Sdk for Python to run my container.



I am trying to start a docker container, and then run a command using the api exec_run (I need the exit code).
The exec_run needs to be executed on a started container.



This is my code:



import docker



client = docker.from_env()

container = client.containers.run('e7d8452ce5f5', command="echo starting", detach=True)

container.exec_run("echo execute command")


This raises an exception:



docker.errors.APIError: 409 Client Error: Conflict ("Container b65acd40f589819f490564dcb4e25f3055d85712cb7b2834ede5f2c4d57f2da6 is not running")


I tried running with no command when invoking client.containers.run, same exception..



Seems the container exists when the command is finished, even though in their documentation it is stated that the command run with detach=True is same as the cli docker run -d (when using docker run -d the container stays alive)



Any ideas on how to keep the container alive in order to call exec_run on it?






python docker







share|improve this question














I am using the Docker Sdk for Python to run my container.



I am trying to start a docker container, and then run a command using the api exec_run (I need the exit code).
The exec_run needs to be executed on a started container.



This is my code:



import docker



client = docker.from_env()

container = client.containers.run('e7d8452ce5f5', command="echo starting", detach=True)

container.exec_run("echo execute command")


This raises an exception:



docker.errors.APIError: 409 Client Error: Conflict ("Container b65acd40f589819f490564dcb4e25f3055d85712cb7b2834ede5f2c4d57f2da6 is not running")


I tried running with no command when invoking client.containers.run, same exception..



Seems the container exists when the command is finished, even though in their documentation it is stated that the command run with detach=True is same as the cli docker run -d (when using docker run -d the container stays alive)



Any ideas on how to keep the container alive in order to call exec_run on it?






python docker




python docker






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 28 '18 at 11:07









dana racahdana racah

1




1













  • Your container stops because the command you use, i.e. echo starting doesn't keep running. Why don't you try with a command like bash or sh?

    – tgogos
    Nov 28 '18 at 11:11






  • 1





    ...or just launching the container with the actual command you want to run?

    – David Maze
    Nov 28 '18 at 11:28











  • Tried running sh -- same thing happens

    – dana racah
    Nov 28 '18 at 11:33











  • I can't launch it with the actual command because I need the exit code and run doesn't return it.. Only exec_run

    – dana racah
    Nov 28 '18 at 11:34






  • 1





    If you try with sh you also need to use the -t and -i options of the docker run command. Not using them will make sh exit immediately too.

    – tgogos
    Nov 28 '18 at 11:43



















  • Your container stops because the command you use, i.e. echo starting doesn't keep running. Why don't you try with a command like bash or sh?

    – tgogos
    Nov 28 '18 at 11:11






  • 1





    ...or just launching the container with the actual command you want to run?

    – David Maze
    Nov 28 '18 at 11:28











  • Tried running sh -- same thing happens

    – dana racah
    Nov 28 '18 at 11:33











  • I can't launch it with the actual command because I need the exit code and run doesn't return it.. Only exec_run

    – dana racah
    Nov 28 '18 at 11:34






  • 1





    If you try with sh you also need to use the -t and -i options of the docker run command. Not using them will make sh exit immediately too.

    – tgogos
    Nov 28 '18 at 11:43

















Your container stops because the command you use, i.e. echo starting doesn't keep running. Why don't you try with a command like bash or sh?

– tgogos
Nov 28 '18 at 11:11





Your container stops because the command you use, i.e. echo starting doesn't keep running. Why don't you try with a command like bash or sh?

– tgogos
Nov 28 '18 at 11:11




1




1





...or just launching the container with the actual command you want to run?

– David Maze
Nov 28 '18 at 11:28





...or just launching the container with the actual command you want to run?

– David Maze
Nov 28 '18 at 11:28













Tried running sh -- same thing happens

– dana racah
Nov 28 '18 at 11:33





Tried running sh -- same thing happens

– dana racah
Nov 28 '18 at 11:33













I can't launch it with the actual command because I need the exit code and run doesn't return it.. Only exec_run

– dana racah
Nov 28 '18 at 11:34





I can't launch it with the actual command because I need the exit code and run doesn't return it.. Only exec_run

– dana racah
Nov 28 '18 at 11:34




1




1





If you try with sh you also need to use the -t and -i options of the docker run command. Not using them will make sh exit immediately too.

– tgogos
Nov 28 '18 at 11:43





If you try with sh you also need to use the -t and -i options of the docker run command. Not using them will make sh exit immediately too.

– tgogos
Nov 28 '18 at 11:43












1 Answer
1






active

oldest

votes


















1














When you use containers.run() method to start a ontainer,you should use tty parameter and set tty=True and then it will keep the container alive.



import docker

client = docker.from_env()

container = client.containers.run('xxxx', command="/bin/bash", tty=True,detach=True)





share|improve this answer























    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
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53518025%2fkeeping-container-alive-with-docker-python-sdk%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









    1














    When you use containers.run() method to start a ontainer,you should use tty parameter and set tty=True and then it will keep the container alive.



    import docker
    
client = docker.from_env()
    
container = client.containers.run('xxxx', command="/bin/bash", tty=True,detach=True)





    share|improve this answer




























      1














      When you use containers.run() method to start a ontainer,you should use tty parameter and set tty=True and then it will keep the container alive.



      import docker
      
client = docker.from_env()
      
container = client.containers.run('xxxx', command="/bin/bash", tty=True,detach=True)





      share|improve this answer


























        1












        1








        1







        When you use containers.run() method to start a ontainer,you should use tty parameter and set tty=True and then it will keep the container alive.



        import docker
        
client = docker.from_env()
        
container = client.containers.run('xxxx', command="/bin/bash", tty=True,detach=True)





        share|improve this answer













        When you use containers.run() method to start a ontainer,you should use tty parameter and set tty=True and then it will keep the container alive.



        import docker
        
client = docker.from_env()
        
container = client.containers.run('xxxx', command="/bin/bash", tty=True,detach=True)






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 11 at 2:50









        lwzhuolwzhuo

        14614




        14614
































            draft saved

            draft discarded




















































            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53518025%2fkeeping-container-alive-with-docker-python-sdk%23new-answer', 'question_page');
            }
            );

            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







            -

            Popular posts from this blog

            A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

            Image
            0 I found a lot of questions abount appendices and ToC. Many users want appendices to be grouped in an Appendix part, however some problems arise with ToC, hyperref, PDF viewer bookmarks, and so on. There are different solutions which require extra packages, command patching and other extra code, however none of them satisfies me. I almost found an easy way to accomplish a good result, where appendices are added to bookmarks in the right way and hyperref links point to the right page. However, the number of the "Appendix" part page is wrong (it's the number of appendix A). Is there any EASY way to fix that? This is a MWE: documentclass{book} usepackage[nottoc,notlot,notlof]{tocbibind} usepackage{hyperref} begin{document} frontmatter tableofcontents mainmatter part{First} chapter{...
            Read more

            Calculate evaluation metrics using cross_val_predict sklearn

            Image
            1 In the sklearn.model_selection.cross_val_predict page it is stated: Generate cross-validated estimates for each input data point. It is not appropriate to pass these predictions into an evaluation metric. Can someone explain what does it mean? If this gives estimate of Y (y prediction) for every Y (true Y), why can't I calculate metrics such as RMSE or coefficient of determination using these results? python scikit-learn cross-validation share | improve this question edited Nov 28 '18 at 17:52 desertnaut 20.3k 7 43 79 ...
            Read more

            Insert data from modal to MySQL (multiple modal on website)

            Image
            0 I have problem with inserting data to MySQL from modal. My modal: <a href="#" class="badge badge-pill badge-success">6 komentarzy</a> <a href="#" class="badge badge-pill badge-danger">brak komentarzy</a> <a data-toggle="modal" href="#add_desk_comm_{$desk_['desk_id']}" data-target="#add_desk_comm_{$desk_['desk_id']}" class="ediiit">(dodaj)</a> <div class="modal fade" id="add_desk_comm_{$desk_['desk_id']}" tabindex="-1" role="dialog" aria-labelledby="edit_printer" aria-hidden="true"> <div class="modal-dialog" role="document"> ...
            Read more