View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007275 | CentOS-7 | -OTHER | public | 2014-06-29 10:45 | 2014-07-01 18:18 |
Reporter | rob.olmos | Assigned To | |||
Priority | normal | Severity | text | Reproducibility | N/A |
Status | new | Resolution | open | ||
Platform | boot2docker v1.0.1 | OS | CentOS | OS Version | 7 |
Summary | 0007275: Docker tarball naming implies it's a Docker image | ||||
Description | The Docker tarball CentOS-7-20140625-x86_64-docker_01.img.tar.xz contains "img", which to me and it looks like a couple others[1] believe it's a Docker image. When attempting to "docker load" the file an error is reported: /mnt/sda1/tmp/docker-import-006962537/repo/dev/json: no such file or directory However, when using "docker import" the tarball imports fine. I'm thinking instead of "img" the word "snap" could be used so as not to imply a docker image. | ||||
Additional Information | [1] A couple commenters at http://seven.centos.org/2014/06/docker-image-for-centos-7qa-now-available/ Also the blog post and devel announcement uses the word "image". | ||||
Tags | No tags attached. | ||||
abrt_hash | |||||
URL | |||||
The naming for this is consistent with the docker documentation, (and even retweeted without comment by docker developers). Please elaborate on your argument a bit more, as this seems a bit of a stretch. | |
Having discussed this with the docker devs, they state that what we have is in no uncertain terms, an image. However there certainly is potential for some confusion. They recommend (and I agree) the addition of a readme in that directory to clarify usage. We'll work at addressing that in the next update for the images. |
|
Thanks for checking with the devs. I started a thread on docker-users[1] asking for clarification but no replies yet. I like the idea of a readme to help clarify. 1. https://groups.google.com/forum/#!topic/docker-user/IMY0c9ooStM |
|