Bug 1342060
| Summary: | Post http:///var/run/docker.sock/v1.22/images/load: write unix /var/run/docker.sock: broken pipe | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Alex Jia <ajia> |
| Component: | atomic | Assignee: | smahajan <smahajan> |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.4 | CC: | dwalsh |
| Target Milestone: | rc | Keywords: | Extras |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-04 09:06:05 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
Alex Jia
2016-06-02 11:14:51 UTC
I just tested it out on a RHEL7 VM and this works for me. Your usecase only involve images (no volumes or containers) so basically it's just `docker save/load` under the atomic wrapper. So I don't see a reason why it is blowing up. I don't think this has anything to do with `atomic storage export` or `import`, there is something else wrong in the setup. Here is the output on my machine: a) $$ cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.2 (Maipo) b) $$ rpm -q docker atomic kernel docker-1.10.3-46.el7.11.x86_64 atomic-1.10.5-7.el7.x86_64 kernel-3.10.0-327.el7.x86_64 kernel-3.10.0-327.18.2.el7.x86_64 kernel-3.10.0-327.28.2.el7.x86_64 c) docker pull some images. $$ docker images REPOSITORY TAG IMAGE ID CREATED SIZE docker.io/fedora latest 11a5107645d4 5 days ago 204.4 MB docker.io/centos latest 970633036444 3 weeks ago 196.7 MB registry.access.redhat.com/rhel7/rhel latest 4a6b6e1a17d7 3 weeks ago 201.6 MB d) $$ atomic storage export --dir /tmp Exporting image: sha256:4a6b6 Exporting image: sha256:11a51 Exporting image: sha256:97063 Exporting volumes atomic export completed successfully e) docker rmi $(docker images -aq) $$ docker images REPOSITORY TAG IMAGE ID CREATED SIZE f) atomic storage import --dir /tmp Importing image: sha256:4a6b6 Importing image: sha256:11a51 Importing image: sha256:97063 Importing volumes atomic import completed successfully Would you like to cleanup (rm -rf /tmp) the temporary directory [y/N] N Please restart docker daemon for the changes to take effect g) systemctl restart docker $$ docker images REPOSITORY TAG IMAGE ID CREATED SIZE docker.io/fedora latest 11a5107645d4 5 days ago 204.4 MB docker.io/centos latest 970633036444 3 weeks ago 196.7 MB registry.access.redhat.com/rhel7/rhel latest 4a6b6e1a17d7 3 weeks ago 201.6 MB Shishir Lets stat that this works in the current release. It works well on atomic-1.10.5-7.el7.x86_64. Moving to VERIFIED status per Comment 4. Just a record for updating testing steps. 1. docker pull some images to the local 2. atomic storage export 3. systemctl stop docker 4. atomic storage reset 5. systemctl start docker 6. atomic storage import 7. atomic images to check if previous exported images are imported successfully Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2628.html |