Why doesn't port forwarding work consistently with my Docker instance?












-1















I ssh'd into a server from my laptop. I opened up a port on my laptop to accept incoming traffic from port 9090, and forward it to 9191.



On the server, I created a Docker ball: sudo docker run --network host --runtime=nvidia -it --rm tensorflow/tensorflow:latest-gpu /bin/bash.



Next, on the shell (in Docker), I did this: jupyter notebook --ip=0.0.0.0 --port=9090 --allow-root



Voila! I pointed my browser to http://localhost:9191, and I could see the precious 'lil notebook running.



I exited the Docker ball, quit the ssh process, went home and went to sleep.



Today, I woke up and ssh'd back to the server. I opened up that same port on my laptop as I did the day before.



I accessed a shell in yesterday's Docker image by sudo docker start my_image and then
sudo docker exec -it my_image /bin/bash



But now, when I get on the shell (in the Docker), and type jupyter notebook --ip=0.0.0.0 --port=9090 --allow-root, like I did yesterday, my forwarding no longer works. Why?






docker ssh portforwarding







share|improve this question



























    -1















    I ssh'd into a server from my laptop. I opened up a port on my laptop to accept incoming traffic from port 9090, and forward it to 9191.



    On the server, I created a Docker ball: sudo docker run --network host --runtime=nvidia -it --rm tensorflow/tensorflow:latest-gpu /bin/bash.



    Next, on the shell (in Docker), I did this: jupyter notebook --ip=0.0.0.0 --port=9090 --allow-root



    Voila! I pointed my browser to http://localhost:9191, and I could see the precious 'lil notebook running.



    I exited the Docker ball, quit the ssh process, went home and went to sleep.



    Today, I woke up and ssh'd back to the server. I opened up that same port on my laptop as I did the day before.



    I accessed a shell in yesterday's Docker image by sudo docker start my_image and then
    sudo docker exec -it my_image /bin/bash



    But now, when I get on the shell (in the Docker), and type jupyter notebook --ip=0.0.0.0 --port=9090 --allow-root, like I did yesterday, my forwarding no longer works. Why?






    docker ssh portforwarding







    share|improve this question

























      -1












      -1








      -1








      I ssh'd into a server from my laptop. I opened up a port on my laptop to accept incoming traffic from port 9090, and forward it to 9191.



      On the server, I created a Docker ball: sudo docker run --network host --runtime=nvidia -it --rm tensorflow/tensorflow:latest-gpu /bin/bash.



      Next, on the shell (in Docker), I did this: jupyter notebook --ip=0.0.0.0 --port=9090 --allow-root



      Voila! I pointed my browser to http://localhost:9191, and I could see the precious 'lil notebook running.



      I exited the Docker ball, quit the ssh process, went home and went to sleep.



      Today, I woke up and ssh'd back to the server. I opened up that same port on my laptop as I did the day before.



      I accessed a shell in yesterday's Docker image by sudo docker start my_image and then
      sudo docker exec -it my_image /bin/bash



      But now, when I get on the shell (in the Docker), and type jupyter notebook --ip=0.0.0.0 --port=9090 --allow-root, like I did yesterday, my forwarding no longer works. Why?






      docker ssh portforwarding







      share|improve this question














      I ssh'd into a server from my laptop. I opened up a port on my laptop to accept incoming traffic from port 9090, and forward it to 9191.



      On the server, I created a Docker ball: sudo docker run --network host --runtime=nvidia -it --rm tensorflow/tensorflow:latest-gpu /bin/bash.



      Next, on the shell (in Docker), I did this: jupyter notebook --ip=0.0.0.0 --port=9090 --allow-root



      Voila! I pointed my browser to http://localhost:9191, and I could see the precious 'lil notebook running.



      I exited the Docker ball, quit the ssh process, went home and went to sleep.



      Today, I woke up and ssh'd back to the server. I opened up that same port on my laptop as I did the day before.



      I accessed a shell in yesterday's Docker image by sudo docker start my_image and then
      sudo docker exec -it my_image /bin/bash



      But now, when I get on the shell (in the Docker), and type jupyter notebook --ip=0.0.0.0 --port=9090 --allow-root, like I did yesterday, my forwarding no longer works. Why?






      docker ssh portforwarding




      docker ssh portforwarding






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 15 '18 at 0:40









      Monica HeddneckMonica Heddneck

      95911647




      95911647
























          1 Answer
          1






          active

          oldest

          votes


















          0














          So, if anyone stumbles onto this question, to solve this I ended up starting over.



          STEP 1: ssh

          STEP 2: create Docker this way:
          sudo docker run -p 9090:9090 --runtime=nvidia -it --rm tensorflow/tensorflow:latest-gpu /bin/bash



          The key was the -p 9090:9090 part. I don't know what --network host was or wasn't doing, but getting rid of it was the key.






          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%2f53310859%2fwhy-doesnt-port-forwarding-work-consistently-with-my-docker-instance%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









            0














            So, if anyone stumbles onto this question, to solve this I ended up starting over.



            STEP 1: ssh

            STEP 2: create Docker this way:
            sudo docker run -p 9090:9090 --runtime=nvidia -it --rm tensorflow/tensorflow:latest-gpu /bin/bash



            The key was the -p 9090:9090 part. I don't know what --network host was or wasn't doing, but getting rid of it was the key.






            share|improve this answer




























              0














              So, if anyone stumbles onto this question, to solve this I ended up starting over.



              STEP 1: ssh

              STEP 2: create Docker this way:
              sudo docker run -p 9090:9090 --runtime=nvidia -it --rm tensorflow/tensorflow:latest-gpu /bin/bash



              The key was the -p 9090:9090 part. I don't know what --network host was or wasn't doing, but getting rid of it was the key.






              share|improve this answer


























                0












                0








                0







                So, if anyone stumbles onto this question, to solve this I ended up starting over.



                STEP 1: ssh

                STEP 2: create Docker this way:
                sudo docker run -p 9090:9090 --runtime=nvidia -it --rm tensorflow/tensorflow:latest-gpu /bin/bash



                The key was the -p 9090:9090 part. I don't know what --network host was or wasn't doing, but getting rid of it was the key.






                share|improve this answer













                So, if anyone stumbles onto this question, to solve this I ended up starting over.



                STEP 1: ssh

                STEP 2: create Docker this way:
                sudo docker run -p 9090:9090 --runtime=nvidia -it --rm tensorflow/tensorflow:latest-gpu /bin/bash



                The key was the -p 9090:9090 part. I don't know what --network host was or wasn't doing, but getting rid of it was the key.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 15 '18 at 21:02









                Monica HeddneckMonica Heddneck

                95911647




                95911647
































                    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%2f53310859%2fwhy-doesnt-port-forwarding-work-consistently-with-my-docker-instance%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

                    Florida Star v. B. J. F.

                    Image
                    Florida Star v. B. J. F. From Wikipedia, the free encyclopedia Jump to navigation Jump to search United States Supreme Court case Florida Star v. B. J. F. Supreme Court of the United States Argued March 21, 1989 Decided June 21, 1989 Full case name The Florida Star v. B. J. F. Citations 491 U.S. 524 ( more ) 109 S. Ct. 2603; 105 L. Ed. 2d 443; 1989 U.S. LEXIS 3120; 57 U.S.L.W. 4816; 16 Media L. Rep. 1801 Prior history The Florida Star v. B.J.F., 530 So.2d 286 (1988) Supreme Court of Florida; Florida Star v. B.J.F., 499 So.2d 883 (1986) Fla. Dist. Court of Appeals Holding Florida Stat. § 794.03 is unconstitutional to the extent it makes the truthful reporting of information that was a matter of public record unlawful, as it violates the First Amendment. Court membership Chief Justice William Rehnquist Associate Justices William J. Brennan Jr.  · Byron White Thurgood Marshall  · Harry Blac
                    Read more

                    Error while running script in elastic search , gateway timeout

                    Image
                    0 while running script in elastic search, I got 504 Gateway timeout error. { "query": { "bool": { "filter": { "script": { "script": " doc['creted_date'].date.getMonthOfYear() == 12 " } } } }, "aggs": { "test": { "date_histogram": { "field": "creted_date", "interval": "month", "format": "MMM" }, "aggs": { "cost": { "sum": { "field": "cost" } } }
                    Read more

                    Adding quotations to stringified JSON object values

                    Image
                    0 My stringified object data doesn't include quotation marks around object values, which errors when attempting JSON.parse() : '{ "affiliation": CORPORATE, "userId": 75c35d1c-5d12-4485-8fa8-b2f1551a3e6e }' I need the string to be: '{ "affiliation": "CORPORATE", "userId": "75c35d1c-5d12-4485-8fa8-b2f1551a3e6e" }' I'm using this regex to add quotes to the object keys: var newStr = str.replace(/(['"])?([a-z0-9A-Z_]+)(['"])?:/g, '"$2": '); For instance: '{ affiliation: CORPORATE }' to '{ "affiliation": CORPORATE }' There are only string values in my data, so I don't need to check value types. How can I alter my regex expression to add quotations to
                    Read more