Bug 1126775
Summary: | `docker load` clears `DockerVersion` and prevents push the tagged image to internal registry | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Guohua Ouyang <gouyang> |
Component: | docker | Assignee: | Václav Pavlín <vpavlin> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | atomic-bugs <atomic-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 | CC: | dwalsh, gouyang, leiwang, lsu, mjenner, sct |
Target Milestone: | rc | Keywords: | Extras |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-01-07 21:35:23 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Guohua Ouyang
2014-08-05 09:01:08 UTC
*** Bug 1126778 has been marked as a duplicate of this bug. *** Docker registry rejects any docker image that has a version less then 0.10.0. Which is causing this problem. BTW Why are we marking these as private. I would like to open a discussion with Docker about this bug. Not sure if there is a good way to fix this other then allowing the user to specify the version of the image. (In reply to Daniel Walsh from comment #3) > Docker registry rejects any docker image that has a version less then > 0.10.0. Which is causing this problem. > > BTW Why are we marking these as private. I would like to open a discussion > with Docker about this bug. Not sure if there is a good way to fix this > other then allowing the user to specify the version of the image. I marked this as private because there are private IP addresses mentioned in the bug description. I am not sure what the fix is for this. Since the tar ball has no json files to identify the docker version used to create the tar ball. Allowing the user to specify the docker version seems like it is easily spoofed or mistake prone. Adding the docker version of the tool that does the load is also wrong. (In reply to Daniel Walsh from comment #5) > I am not sure what the fix is for this. Since the tar ball has no json > files to identify the docker version used to create the tar ball. Allowing > the user to specify the docker version seems like it is easily spoofed or > mistake prone. Adding the docker version of the tool that does the load is > also wrong. There is an json file in the tar ball, and there has the key “DockerVersion". # cat 26ac5f9b5cf6d6948f31691f06416381ac70317f3ca45ee7c0b44d91df88e760/json {"Architecture":"amd64","Author":"","Comment":"Imported from -","Config":null,"Container":"","ContainerConfig":{"AttachStderr":false,"AttachStdin":false,"AttachStdout":false,"Cmd":null,"CpuShares":0,"Cpuset":"","Domainname":"","Entrypoint":null,"Env":null,"ExposedPorts":null,"Hostname":"","Image":"","Memory":0,"MemorySwap":0,"NetworkDisabled":false,"OnBuild":null,"OpenStdin":false,"PortSpecs":null,"StdinOnce":false,"Tty":false,"User":"","Volumes":null,"WorkingDir":""},"Created":"2014-07-17T17:25:57.019509969Z","DockerVersion":"1.0.0","Id":"26ac5f9b5cf6d6948f31691f06416381ac70317f3ca45ee7c0b44d91df88e760","Os":"linux","Parent":"","Size":139874178} Ok, then it is a bug. Sorry I just thought this was a flat tar of a directory. Ouyang, I am thinking that the problem is in the creation of rhel-server-docker-7.0-22.1.x86_64.tar.gz. We need to create a new one of these using the latest docker. (In reply to Daniel Walsh from comment #8) > Ouyang, I am thinking that the problem is in the creation of > rhel-server-docker-7.0-22.1.x86_64.tar.gz. We need to create a new one of > these using the latest docker. agree on this. I tested that saving a tar ball from the latest base rhel image, and loaded it on a clean environment, `DockerVersion` is there and could be pushed to internal registry. So is this still a bug in docker load or is this something else? (From Dan's latest comment it looks like he changed his mind and thinks its,a bug in the creation of the tar. (?)) Yes this is a problem with the image and the docer version used to create it. We need to make sure we have a clean image(s) with the correct data set. Lets reassign this to Vacek. Fixed in docker-1.2 |