Re: [atomic-devel] Docker-1.10 to docker-1.9 rollback.

[Daniel J Walsh <dwalsh redhat com>]

On 12/01/2015 05:40 AM, Antonio Murdaca wrote:
>
> ----- Messaggio originale -----
> | Da: "Antonio Murdaca" <amurdaca redhat com>
> | A: "Daniel J Walsh" <dwalsh redhat com>
> | Cc: atomic-devel projectatomic io
> | Inviato: Martedì, 1 dicembre 2015 10:20:38
> | Oggetto: Re: [atomic-devel] Docker-1.10 to docker-1.9 rollback.
> | 
> | 
> | 
> | ----- Messaggio originale -----
> | | Da: "Daniel J Walsh" <dwalsh redhat com>
> | | A: atomic-devel projectatomic io
> | | Inviato: Lunedì, 30 novembre 2015 21:15:49
> | | Oggetto: [atomic-devel] Docker-1.10 to docker-1.9 rollback.
> | | 
> | | When you upgrade to docker-1.10, your container images json data gets
> | | rewritten with UUID based on the content in the images.  This will take
> | | a while, depending on the number and size of images.  One potential
> | | problem is rollback.
> | 
> | One thing which might help here is that the rewrite of the images json is
> | not destructive so old images json will be still around after the migration.
> | Haven't heard anything about Docker officially supporting this kind of
> | compatibility with old code but it files still get around it could be
> | something which we could implement on our side based on the docker version
> | running maybe (just throwing ideas).
>
> I found what could cause this break. I'm still checking but the rollback to
> 1.9 it's working for me iff I compile docker 1.10 w/o the exprimental flag. 
> This means specifically userns isn't enabled and the directory tree under
> /var/lib/docker doesn't have "0.0" (which is for userns)
> Instead, if you upgrade and rollback with 1.10 w/o userns everything is working
> fine because the graph/ dir is directly inside /var/lib/docker (and not
> /var/lib/docker/0.0). I'll see if I can write a quick patch for this because
> the migration to userns is breaking the rollback (at least for me)
> Dan, can you check if you're running 1.10 with userns and what's inside
> /var/lib/docker for you?
>
> | 
> | | 
> | | When I updated a docker to docker-1.10 (In devel, Rawhide) my images get
> | | updated.  Now if I rollback to docker-1.9 I notice my containers are
> | | disappearing.
> | | 
> | | docker ps -a
> | | CONTAINER ID        IMAGE               COMMAND
> | | CREATED             STATUS                      PORTS               NAME
> | | dc8ba4c69222        fedora              "bash"              13 minutes
> | | ago      Exited (0) 13 minutes ago                       fervent_rosalind
> | | 1e1a4d59c375        fedora              "bash"              3 hours
> | | ago         Exited (0) 3 hours ago                          amazing_yonath
> | | 
> | | Rollback to docker-1.9
> | | 
> | | [root dhcp-10-19-62-196 docker]# docker ps -a
> | | CONTAINER ID        IMAGE               COMMAND
> | | CREATED             STATUS                      PORTS               NAMES
> | | 
> | | Nothing.
> | | 
> | | I create a container. (Using docker-1.9
> | | 
> | | I update to docker-1.10 again
> | | 
> | | docker ps -a
> | | CONTAINER ID        IMAGE               COMMAND
> | | CREATED             STATUS                      PORTS               NAMES
> | | 6073b1c7c08f        fedora              "bash"              11 minutes
> | | ago      Exited (0) 11 minutes ago                       boring_shockley
> | | dc8ba4c69222        fedora              "bash"              13 minutes
> | | ago      Exited (0) 13 minutes ago                       fervent_rosalind
> | | 1e1a4d59c375        fedora              "bash"              3 hours
> | | ago         Exited (0) 3 hours ago                          amazing_yonath
> | | 
> | | Rollback to docker-1.9
> | | 
> | | [root dhcp-10-19-62-196 docker]# docker ps -a
> | | CONTAINER ID        IMAGE               COMMAND
> | | CREATED             STATUS                      PORTS               NAMES
> | | 6073b1c7c08f        fedora              "bash"              13 minutes
> | | ago      Exited (0) 13 minutes ago                       boring_shockley
> | | 
> | | Might be a bug, but this is something we need to understand in order to
> | | figure out what happens if a atomic host upgrades and rolls back.
> | | 
> | | 
> | 
> | 
I am not running with expermental or user namespace.   But I do see
issues with
containers created while in docker-1.10 and then dropping back to docker-9

ls /var/lib/docker
containers    graph  linkgraph.db  repositories-devicemapper  trust
devicemapper  image  network       tmp                        volumes

 ls /var/lib/docker/containers/
1e1a4d59c375752f5ef794a1c7ad4c3231c78da4cad24028d2cb8a54734d0147
6073b1c7c08f2b01d4b040535fe6235f7066ab3d06aa3537d579055f828b2979
d5a8ffb2727416684d18675a424cc713d705f9e7d73d1a134412fad385ad3435
dc8ba4c6922250483259fecc1a564c3aff28a3b7f88d4d3a34dc9223c406b825

 docker ps -a
CONTAINER ID        IMAGE               COMMAND            
CREATED             STATUS                        PORTS               NAMES
d5a8ffb27274        fedora              "bash"              16 hours
ago        Exited (137) 55 minutes ago                       drunk_colden
6073b1c7c08f        fedora              "bash"              17 hours
ago        Exited (0) 17 hours ago                           boring_shockley


docker version
Client:
 Version:         1.9.1
 API version:     1.21
 Package version: docker-1.10.0-6.git39f99b6.fc24.x86_64
 Go version:      go1.5.1
 Git commit:      6ec29ef
 Built:           Mon Nov 30 20:09:34 UTC 2015
 OS/Arch:         linux/amd64

Server:
 Version:         1.9.1
 API version:     1.21
 Package version: docker-1.10.0-6.git39f99b6.fc24.x86_64
 Go version:      go1.5.1
 Git commit:      6ec29ef
 Built:           Mon Nov 30 20:09:34 UTC 2015
 OS/Arch:         linux/amd64