Build docker image from layers











up vote
0
down vote

favorite












I have a big docker image I need to copy to a remote machine.
I build the image on my local machine with an unchanging base image, so only the last few layers change.
I would like to have that base image on the remote machine and only copy the changed top layers to the remote machine whenever they change. I cannot build the image on the remote using its dockerfile because the necessary source files are not present on the remote.



I can separate the image into its layers using undocker, but how do I reassemble the image from its layers on the remote machine?






docker







share|improve this question


















  • 1




    why you done push your image to dockerhub then acces to remote server and pull it ?
    – Truong Dang
    Nov 8 at 7:32










  • If you really don't have a registry available, I wonder if it would work to docker save the image, unpack the tarball, rsync that to the remote system, rebuild the tarball, and docker load the result. That won't be fast in Docker time, but it would probably save network I/O.
    – David Maze
    Nov 8 at 11:11















up vote
0
down vote

favorite












I have a big docker image I need to copy to a remote machine.
I build the image on my local machine with an unchanging base image, so only the last few layers change.
I would like to have that base image on the remote machine and only copy the changed top layers to the remote machine whenever they change. I cannot build the image on the remote using its dockerfile because the necessary source files are not present on the remote.



I can separate the image into its layers using undocker, but how do I reassemble the image from its layers on the remote machine?






docker







share|improve this question


















  • 1




    why you done push your image to dockerhub then acces to remote server and pull it ?
    – Truong Dang
    Nov 8 at 7:32










  • If you really don't have a registry available, I wonder if it would work to docker save the image, unpack the tarball, rsync that to the remote system, rebuild the tarball, and docker load the result. That won't be fast in Docker time, but it would probably save network I/O.
    – David Maze
    Nov 8 at 11:11













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I have a big docker image I need to copy to a remote machine.
I build the image on my local machine with an unchanging base image, so only the last few layers change.
I would like to have that base image on the remote machine and only copy the changed top layers to the remote machine whenever they change. I cannot build the image on the remote using its dockerfile because the necessary source files are not present on the remote.



I can separate the image into its layers using undocker, but how do I reassemble the image from its layers on the remote machine?






docker







share|improve this question













I have a big docker image I need to copy to a remote machine.
I build the image on my local machine with an unchanging base image, so only the last few layers change.
I would like to have that base image on the remote machine and only copy the changed top layers to the remote machine whenever they change. I cannot build the image on the remote using its dockerfile because the necessary source files are not present on the remote.



I can separate the image into its layers using undocker, but how do I reassemble the image from its layers on the remote machine?






docker




docker






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 8 at 7:17









warakawa

351413




351413








  • 1




    why you done push your image to dockerhub then acces to remote server and pull it ?
    – Truong Dang
    Nov 8 at 7:32










  • If you really don't have a registry available, I wonder if it would work to docker save the image, unpack the tarball, rsync that to the remote system, rebuild the tarball, and docker load the result. That won't be fast in Docker time, but it would probably save network I/O.
    – David Maze
    Nov 8 at 11:11














  • 1




    why you done push your image to dockerhub then acces to remote server and pull it ?
    – Truong Dang
    Nov 8 at 7:32










  • If you really don't have a registry available, I wonder if it would work to docker save the image, unpack the tarball, rsync that to the remote system, rebuild the tarball, and docker load the result. That won't be fast in Docker time, but it would probably save network I/O.
    – David Maze
    Nov 8 at 11:11








1




1




why you done push your image to dockerhub then acces to remote server and pull it ?
– Truong Dang
Nov 8 at 7:32




why you done push your image to dockerhub then acces to remote server and pull it ?
– Truong Dang
Nov 8 at 7:32












If you really don't have a registry available, I wonder if it would work to docker save the image, unpack the tarball, rsync that to the remote system, rebuild the tarball, and docker load the result. That won't be fast in Docker time, but it would probably save network I/O.
– David Maze
Nov 8 at 11:11




If you really don't have a registry available, I wonder if it would work to docker save the image, unpack the tarball, rsync that to the remote system, rebuild the tarball, and docker load the result. That won't be fast in Docker time, but it would probably save network I/O.
– David Maze
Nov 8 at 11:11












2 Answers
2






active

oldest

votes

















up vote
0
down vote













I've never worked with undocker tool so I can't comment on this, but in my understanding image in docker is a "sealed package" ready for distribution in one way or another.



So copying part of the image sounds to me like distributing a part of the package.



I can understand that overhead of big image on the other hand (probably you're looking for faster copying), but it contradicts the docker "ideology" (take image "as is" and work with it)



So, probably the most straightforward option is preparing the sources (those are in the "last few layers") as a distributable package without docker, copying them to the remote machine and then building the image on the remote machine out of a base image and this distributable package



This allows overcoming a workaround of "the necessary source files are not present on the remote" as you say






share|improve this answer




























    up vote
    0
    down vote



    accepted










    I have switched to using a Docker registry, and updating my image with docker pull, which I think is the proper way to solve this problem, since it will only download the changed layers.
    This article also helped me reduce the size of my images.






    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',
      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%2f53203000%2fbuild-docker-image-from-layers%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      0
      down vote













      I've never worked with undocker tool so I can't comment on this, but in my understanding image in docker is a "sealed package" ready for distribution in one way or another.



      So copying part of the image sounds to me like distributing a part of the package.



      I can understand that overhead of big image on the other hand (probably you're looking for faster copying), but it contradicts the docker "ideology" (take image "as is" and work with it)



      So, probably the most straightforward option is preparing the sources (those are in the "last few layers") as a distributable package without docker, copying them to the remote machine and then building the image on the remote machine out of a base image and this distributable package



      This allows overcoming a workaround of "the necessary source files are not present on the remote" as you say






      share|improve this answer

























        up vote
        0
        down vote













        I've never worked with undocker tool so I can't comment on this, but in my understanding image in docker is a "sealed package" ready for distribution in one way or another.



        So copying part of the image sounds to me like distributing a part of the package.



        I can understand that overhead of big image on the other hand (probably you're looking for faster copying), but it contradicts the docker "ideology" (take image "as is" and work with it)



        So, probably the most straightforward option is preparing the sources (those are in the "last few layers") as a distributable package without docker, copying them to the remote machine and then building the image on the remote machine out of a base image and this distributable package



        This allows overcoming a workaround of "the necessary source files are not present on the remote" as you say






        share|improve this answer























          up vote
          0
          down vote










          up vote
          0
          down vote









          I've never worked with undocker tool so I can't comment on this, but in my understanding image in docker is a "sealed package" ready for distribution in one way or another.



          So copying part of the image sounds to me like distributing a part of the package.



          I can understand that overhead of big image on the other hand (probably you're looking for faster copying), but it contradicts the docker "ideology" (take image "as is" and work with it)



          So, probably the most straightforward option is preparing the sources (those are in the "last few layers") as a distributable package without docker, copying them to the remote machine and then building the image on the remote machine out of a base image and this distributable package



          This allows overcoming a workaround of "the necessary source files are not present on the remote" as you say






          share|improve this answer












          I've never worked with undocker tool so I can't comment on this, but in my understanding image in docker is a "sealed package" ready for distribution in one way or another.



          So copying part of the image sounds to me like distributing a part of the package.



          I can understand that overhead of big image on the other hand (probably you're looking for faster copying), but it contradicts the docker "ideology" (take image "as is" and work with it)



          So, probably the most straightforward option is preparing the sources (those are in the "last few layers") as a distributable package without docker, copying them to the remote machine and then building the image on the remote machine out of a base image and this distributable package



          This allows overcoming a workaround of "the necessary source files are not present on the remote" as you say







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 8 at 7:31









          Mark Bramnik

          11.2k32445




          11.2k32445
























              up vote
              0
              down vote



              accepted










              I have switched to using a Docker registry, and updating my image with docker pull, which I think is the proper way to solve this problem, since it will only download the changed layers.
              This article also helped me reduce the size of my images.






              share|improve this answer

























                up vote
                0
                down vote



                accepted










                I have switched to using a Docker registry, and updating my image with docker pull, which I think is the proper way to solve this problem, since it will only download the changed layers.
                This article also helped me reduce the size of my images.






                share|improve this answer























                  up vote
                  0
                  down vote



                  accepted







                  up vote
                  0
                  down vote



                  accepted






                  I have switched to using a Docker registry, and updating my image with docker pull, which I think is the proper way to solve this problem, since it will only download the changed layers.
                  This article also helped me reduce the size of my images.






                  share|improve this answer












                  I have switched to using a Docker registry, and updating my image with docker pull, which I think is the proper way to solve this problem, since it will only download the changed layers.
                  This article also helped me reduce the size of my images.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 29 at 6:00









                  warakawa

                  351413




                  351413






























                      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.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • 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%2f53203000%2fbuild-docker-image-from-layers%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







                      -

                      這個網誌中的熱門文章

                      Tangent Lines Diagram Along Smooth Curve

                      圖片
                      7 1 I am trying to replicate a diagram and have a minimal example. I don't know how to add additional tangents between the specified points and preserve smoothness. documentclass{article} usepackage{tikz} usetikzlibrary{calc,intersections} begin{document} begin{tikzpicture} % Axes draw [->, name path=x] (-1,0) -- (11,0) node [right] {$x$}; draw [->] (0,-1) -- (0,6) node [above] {$y$}; % Origin node at (0,0) [below left] {$0$}; % Points coordinate (start) at (1,-0.8); coordinate (c1) at (3,3); coordinate (c2) at (5.5,1.5); coordinate (c3) at (8,4); coordinate (end) at (10.5,-0.8); % show the points foreach n in {start,c1,c2,c3,end} fill [black] (n) circle (2pt) node [below] {}; % join the coordinates draw [thick,name path=curve] (start) to[out=70,in=180] (c1) to[out=0,in=180]
                      閱讀完整內容

                      Yusuf al-Mu'taman ibn Hud

                      圖片
                      Main article: Taifa of Zaragoza Al-Mu'taman Ruler of Zaragoza Reign 1081–1085 Predecessor Ahmad al-Muqtadir Successor Al-Mustain II Born Zaragoza Died 1085 Full name Yusuf ibn Ahmad al-Mu'taman ibn Hūd House Banu Hud Yusuf ibn Ahmad al-Mu'taman ibn Hūd (Arabic: المؤتمن بالله يوسف إبن أحمد إبن هود ‎, al-Mutaman bi l-Lah , died c. 1085) was the third king of the Banu Hud dynasty who ruled over the Taifa of Zaragoza from 1081 to 1085. Yusuf al-Mutaman reigned during the height of power of Muslim Zaragoza , following the thriving period of his father Ahmad al-Muqtadir. He continued his father's efforts and created around him a court of intellectuals, living in the beautiful palace of Aljafería, nicknamed as "the palace of joy". Al-Mu'taman was also a scholarly king and a patron of science, philosophy and arts. As an example of a wise king, he knew astrology, philosophy, and especially mathematics, a discipline in which
                      閱讀完整內容

                      Zucchini

                      圖片
                      This article is about the vegetable. For other uses, see Zucchini (disambiguation). Zucchini (courgette) A striped and a uniform color zucchini Genus Cucurbita Species Cucurbita pepo Origin 19th century northern Italy The zucchini ( / z uː ˈ k iː n i / , American English) or courgette ( / k ʊər ˈ ʒ ɛ t / , British English) is a summer squash which can reach nearly 1 metre (100 cm; 39 in) in length, but is usually harvested when still immature at about 15 to 25 cm (6 to 10 in). [1] A zucchini is a thin-skinned cultivar of what in Britain and Ireland is referred to as a marrow. [2] [3] In South Africa, a zucchini is known as a baby marrow. Along with certain other squashes and pumpkins, the zucchini belongs to the species Cucurbita pepo . It can be dark or light green. A related hybrid, the golden zucchini, is a deep yellow or orange color. [4] In a culinary context, the zucchini is treated as a vegetable; it is usually cooked and presented as a savory dish o
                      閱讀完整內容