exports container not getting cleaned up after the build

[b-dean]

When I build, a rocker_exports_XXXXXXX container is left behind. This particularly bad for our build servers to start having a bunch of leftover rocker export containers

version

rocker version 1.3.1 - 5b0d185 (master) 2017-07-10_13:04_GMT

steps to reproduce

Create Rockerfile

FROM centos:6
RUN echo foo > /bar
EXPORT /bar

FROM centos:6
IMPORT bar /baz
RUN cat /baz

run the build:

ben@fakename:~/bug$ rocker build --no-garbage
INFO[0000] FROM centos:6                     
INFO[0000] | Pull image centos:6                        
6: Pulling from library/centos
cd3b990dbbea: Pull complete 
Digest: sha256:7b8315565896cf97fc663c99ae175760aa1db9f7febe2f7a078696c6897604a7
Status: Downloaded newer image for centos:6
INFO[0008] | Image sha256:7ea30                          size=194.3 MB
INFO[0008] RUN echo foo > /bar               
INFO[0008] | Not cached                        
INFO[0008] | Created container 283d971673d6 (image sha256:7ea30) 
INFO[0009] Commit changes                    
INFO[0009] | Result image is sha256:3250a                size=194.3 MB (+4 B)
INFO[0009] | Removing container 283d971673d6            
INFO[0009] EXPORT /bar                       
INFO[0009] | Pull image grammarly/rsync-static:1        
1: Pulling from grammarly/rsync-static
a3ed95caeb02: Pull complete 
84708c6b3b7f: Pull complete 
Digest: sha256:015ae9ca010ea7d7d99f32ea2956728b76fcdcb7bed70dfd935cfeb6650347b1
Status: Downloaded newer image for grammarly/rsync-static:1
INFO[0010] | Create container: rocker_exports_393a75d2a0e6a113579a99ec for exports 
INFO[0010] | Using exports container rocker_exports_393a75d2a0e6a113579a99ec 
INFO[0010] | Created container a34b4da00e1f (image sha256:3250a) 
INFO[0010] | Running in a34b4da00e1f: /opt/rsync/bin/rsync -a --delete-during /bar /.rocker_exports/ 
INFO[0010] | Removing container a34b4da00e1f            
INFO[0010] Commit changes                    
INFO[0010] | Created container d030e6a6234d (image sha256:3250a) 
INFO[0010] | Result image is sha256:1c369                size=194.3 MB (+0 B)
INFO[0010] | Removing container d030e6a6234d            
INFO[0010] Cleaning up                       
INFO[0010] | Remove image sha256:1c369                  
INFO[0010] ====================================         
INFO[0010] FROM centos:6                     
INFO[0010] | Image sha256:7ea30                          size=194.3 MB
INFO[0010] IMPORT bar /baz                   
INFO[0010] | Using exports container rocker_exports_393a75d2a0e6a113579a99ec 
INFO[0010] | Import from rocker_exports_393a75d2a0e6a113579a99ec (0dcdf4a4fe68) 
INFO[0010] | Not cached                        
INFO[0010] | Created container 4985d66e7576 (image sha256:7ea30) 
INFO[0010] | Running in 4985d66e7576: /opt/rsync/bin/rsync -a /.rocker_exports/bar /baz 
INFO[0011] Commit changes                    
INFO[0011] | Result image is sha256:c8d05                size=194.3 MB (+4 B)
INFO[0011] | Removing container 4985d66e7576            
INFO[0011] RUN cat /baz                      
INFO[0011] | Created container 7e25f919911b (image sha256:c8d05) 
foo
INFO[0011] Commit changes                    
INFO[0011] | Result image is sha256:9f8c3                size=194.3 MB (+0 B)
INFO[0011] | Removing container 7e25f919911b            
INFO[0011] Cleaning up                       
INFO[0011] | Remove image sha256:9f8c3                  
INFO[0011] Successfully built sha256:9f8c3 | final size 194.3 MB (+4 B from the base image)

look at the containers left around:

ben@fakename:~/bug$ docker ps -a
CONTAINER ID        IMAGE                      COMMAND                  CREATED             STATUS              PORTS               NAMES
0dcdf4a4fe68        grammarly/rsync-static:1   "/opt/rsync/bin/rs..."   52 seconds ago      Created                                 rocker_exports_393a75d2a0e6a113579a99ec

[ybogdanov]

Thanks for reporting. Unfortunately, we are discontinuing this project. See the notice here: https://github.com/grammarly/rocker/blob/master/README.md

Closing this issue as we are not able to address it. Sorry.