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

[Antonio Murdaca <amurdaca redhat com>]

----- 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.
| | 
| | 
| 
|