Answers: <p>This is a known issue with aufs -- see <a href="https://github.com/moby/moby/issues/21950#issuecomment-208881571" rel="nofollow noreferrer">here</a> for context.</p>
  
  <p>Use <code>ADD &lt;tarball_path&gt;</code> and use the overlay driver on the build server. </p>
  
Answers: CC BY-SA 4.0
Answers: 2018-12-03T16:54:20.003Z
Answers: Well that's less handy than I expected, but I think there's everything I need in that thread to make it work until they manage to sort it out.
Answers: Perkins
Answers: CC BY-SA 4.0
Answers: 2018-11-30T19:28:35.590Z
Answers: 2018-11-30T19:36:25.250Z
Answers: 2018-11-30T19:36:25.250Z
Answers: Miranda Edwards
Body: <p>Some background:</p>
  
  <p>I've got an existing build system that creates (among other things) container images.  Due to the nature of their contents, they are suitable for running on practically any containerization toolset one might care to use.  </p>
  
  <p>Now I've got some users who want to load them into Docker.  Ok, that works fine, except that each revision of the container image imports separately.</p>
  
  <p>The users would like to take advantage of the space-saving capabilities of Docker layers to deduplicate data between versions.</p>
  
  <p>I could, of course, instantiate the previous image, and then use rsync or similar to update it and then commit it (and that's what I'll do if I have to) but that seems like an awfully clunky workflow.</p>
  
  <p>The question:</p>
  
  <p>Is there some piece of functionality built into Docker that I'm just not finding that would simplify the process of importing updated image tarballs into an existing image's history?  I can find all kinds of resources about pruning and flattening Docker history, but nothing for those of us who manage our image contents via other systems.</p>
  
Tags: <docker>
Title: Import tarball as next revision
UserDisplayName: Perkins
ThreadText: # Import tarball as next revision
  
  (Asked by: username_0 on 2018-11-30)
  
  Some background:
  
  I've got an existing build system that creates (among other things) container images. Due to the nature of their contents, they are suitable for running on practically any containerization toolset one might care to use.
  
  Now I've got some users who want to load them into Docker. Ok, that works fine, except that each revision of the container image imports separately.
  
  The users would like to take advantage of the space-saving capabilities of Docker layers to deduplicate data between versions.
  
  I could, of course, instantiate the previous image, and then use rsync or similar to update it and then commit it (and that's what I'll do if I have to) but that seems like an awfully clunky workflow.
  
  The question:
  
  Is there some piece of functionality built into Docker that I'm just not finding that would simplify the process of importing updated image tarballs into an existing image's history? I can find all kinds of resources about pruning and flattening Docker history, but nothing for those of us who manage our image contents via other systems.
  
  **Tags:** docker
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-11-30. Score: 1 | Accepted answer
  
  This is a known issue with aufs -- see [here](https://github.com/moby/moby/issues/21950#issuecomment-208881571) for context.
  
  Use `ADD <tarball_path>` and use the overlay driver on the build server.
  
  > **Comments:**
  > **username_0**: Well that's less handy than I expected, but I think there's everything I need in that thread to make it work until they manage to sort it out.  
  
  ---
  
  