Different image ids when pulling on different servers #17749
Comments
|
Hi! Please read this important information about creating issues. If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead. If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information. This is an automated, informational response. Thank you. For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues BUG REPORT INFORMATIONUse the commands below to provide key information from your environment:
Provide additional environment details (AWS, VirtualBox, physical, etc.): List the steps to reproduce the issue: Describe the results you received: Describe the results you expected: Provide additional info you think is important: ----------END REPORT --------- #ENEEDMOREINFO |
|
System information: $ # same on both servers
$ docker version
Client:
Version: 1.9.0
API version: 1.21
Go version: go1.4.3
Git commit: 76d6bc9
Built: Tue Nov 3 19:20:09 UTC 2015
OS/Arch: linux/amd64
Server:
Version: 1.9.0
API version: 1.21
Go version: go1.4.3
Git commit: 76d6bc9
Built: Tue Nov 3 19:20:09 UTC 2015
OS/Arch: linux/amd64
$ # First server
$ docker info
Containers: 0
Images: 30
Server Version: 1.9.0
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 30
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.19.0-32-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 1
Total Memory: 1.657 GiB
Name: c01.<redacted>
ID: <redacted>
WARNING: No swap limit support
$ # second server
$ docker info
Containers: 7
Images: 29
Server Version: 1.9.0
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 43
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.19.0-32-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 1
Total Memory: 1.657 GiB
Name: c02.<redacted>
ID: <redacted>
WARNING: No swap limit support
$ # first server
$ uname -a
Linux c01.<redacted> 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
$ # second server
$ uname -a
Linux c02.<redacted> 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015 x86_64 x86_64 x86_64 GNU/LinuxBoth servers are on google compute engine. Steps for reproducing are in the first post. This problem happened only for first server (c01). First server(c01) seems to have the correct image id, all others have the wrong image id. After removing docker, wiping |
|
I'm seeing similar behavior, but only for users using Docker 1.9 vs. 1.8. Most of us are on Docker 1.8, while a few of us are testing Docker 1.9. We store our images on a private registry running distribution/2.1.1 Users running Docker 1.8 all see the same image ID when pulling, while users running 1.9 see a different-same image ID. For example, all users running 1.8 may pull Example user running 1.8: $ docker version
Client:
Version: 1.8.1
API version: 1.20
Go version: go1.4.2
Git commit: d12ea79
Built: Thu Aug 13 02:49:29 UTC 2015
OS/Arch: darwin/amd64
Server:
Version: 1.8.1
API version: 1.20
Go version: go1.4.2
Git commit: d12ea79
Built: Thu Aug 13 02:49:29 UTC 2015
OS/Arch: linux/amd64
$ docker info
Containers: 22
Images: 338
Storage Driver: aufs
Root Dir: /mnt/sda1/var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 382
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.0.9-boot2docker
Operating System: Boot2Docker 1.8.1 (TCL 6.3); master : 7f12e95 - Thu Aug 13 03:24:56 UTC 2015
CPUs: 1
Total Memory: 996.2 MiB
Name: default
ID: XWDR:NDLK:7CBQ:N7PL:OEAP:KIUU:IMXV:2SNN:ITJC:VZIX:MZ7O:SVJP
Debug mode (server): true
File Descriptors: 11
Goroutines: 36
System Time: 2015-11-23T16:23:43.918742631Z
EventsListeners: 0
Init SHA1:
Init Path: /usr/local/bin/docker
Docker Root Dir: /mnt/sda1/var/lib/docker
Labels:
provider=virtualbox
$ uname -a
Darwin ip-10-100-0-28.us-west-2.compute.internal 14.5.0 Darwin Kernel Version 14.5.0: Wed Jul 29 02:26:53 PDT 2015; root:xnu-2782.40.9~1/RELEASE_X86_64 x86_64Example user running 1.9 $ docker version
Client:
Version: 1.9.0
API version: 1.21
Go version: go1.4.3
Git commit: 76d6bc9
Built: Tue Nov 3 19:20:09 UTC 2015
OS/Arch: darwin/amd64
Server:
Version: 1.9.0
API version: 1.21
Go version: go1.4.3
Git commit: 76d6bc9
Built: Tue Nov 3 19:20:09 UTC 2015
OS/Arch: linux/amd64
$ docker info
Containers: 0
Images: 60
Server Version: 1.9.0
Storage Driver: aufs
Root Dir: /mnt/sda1/var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 60
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.1.12-boot2docker
Operating System: Boot2Docker 1.9.0 (TCL 6.4); master : 16e4a2a - Tue Nov 3 19:49:22 UTC 2015
CPUs: 1
Total Memory: 3.859 GiB
Name: default
ID: UEW4:WNAU:FRED:J3JT:6YTY:BZJ4:PJA6:6RBX:444D:B7JT:4ILX:SWBY
Debug mode (server): true
File Descriptors: 13
Goroutines: 20
System Time: 2015-11-23T16:34:48.61314161Z
EventsListeners: 0
Init SHA1:
Init Path: /usr/local/bin/docker
Docker Root Dir: /mnt/sda1/var/lib/docker
Labels:
provider=virtualbox
$ uname -a
Darwin ip-10-100-0-105.us-west-2.compute.internal 15.0.0 Darwin Kernel Version 15.0.0: Sat Sep 19 15:53:46 PDT 2015; root:xnu-3247.10.11~1/RELEASE_X86_64 x86_64 |
|
Images pulled from Having different ID should be harmless and have no effect on pushing/building for example. If you wan't to get the same ID remove image from server1 and redownload. This issue will go away after #17924 |
|
Ok, thanks ! I was afraid that images got corrupted after upgrade, but I verified content and it looks the same. Edit: I was was using the default public registry. |
|
Thanks @tonistiigi. I suspect what happened in my case is that a user using 1.9.0 pushed an image to a v2 registry and a different user pulled this image, re-tagged as "latest", and pushed to the same registry. The result is that users >1.8.2 see the two images as different and download different layers for each. |
|
#17924 Was merged, so I'm closing this issue |
|
Hi Server: Containers: 10 uname -a Server2: Server: Containers: 2 uname -a Image Id, while image is build in Server1 and before pushed to nexus: Sudo docker images output after image is pulled on to server2 from nexus and retagged image also: Pushed tagged image to nexus Pulling image back Now image id differs after pulling back: Looking to know what is causing docker to allocate different new Image Id, to retagged image that i pulled back. |
|
ping @tonistiigi ^^ |
|
@rajeshchowdary143 |
|
Ok, let me lock the conversation on this issue so that new reports of possible bugs are not reported here and don't get lost. If you are running into this issue, and suspect there's a bug at hand, open a new issue and provide the information that's requested in the issue-template that is shown when you open the issue, at least;
For this issue, also provide the registry version and daemon logs (information as requested above #17749 (comment)) |
Hi
I upgraded from lxc-docker-1.7.1 to lxc-docker-1.9.0 on ubuntu 14.04. I'm pulling docker images on every chef provision (check for updated version). I can see docker has the same image id when pulling, but
docker imagessays different image ids.Let me know if I can help with any logs or debug information.
The text was updated successfully, but these errors were encountered: