Ask questionsfailed to export image: failed to create image: failed to get layer: layer does not exist
<!-- 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.
For more information about reporting issues, see https://github.com/moby/moby/blob/master/CONTRIBUTING.md#reporting-other-issues
The GitHub issue tracker is for bug reports and feature requests. General support for docker can be found at the following locations:
General support for moby can be found at the following locations:
Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST -->
Sometimes when building my images i have this error.
As docker uses subvolumes, i know that sometimes BTRFS just wreck everything and files/subvolumes aren't visible from "users", including "ls" in a shell or, here, Docker.
The problem appears after many build happened.
Also, the cache isn't available for docker to use it.
sudo sync, the docker cache is available and build can continue from where it stopped.
Steps to reproduce the issue:
syncas root, wait for the command to finish
Additional information you deem important (e.g. issue happens only occasionally):
❭ docker version Client: Version: 18.02.0-ce API version: 1.36 Go version: go1.9.4 Git commit: fc4de447b5 Built: Tue Feb 13 15:28:01 2018 OS/Arch: linux/amd64 Experimental: false Orchestrator: swarm Server: Engine: Version: 18.02.0-ce API version: 1.36 (minimum version 1.12) Go version: go1.9.4 Git commit: fc4de447b5 Built: Tue Feb 13 15:28:34 2018 OS/Arch: linux/amd64 Experimental: false
Containers: 673 Running: 1 Paused: 0 Stopped: 672 Images: 1805 Server Version: 18.02.0-ce Storage Driver: btrfs Build Version: Btrfs v4.15 Library Version: 102 Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: 9b55aab90508bd389d7654c4baf173a981477d55 runc version: 9f9c96235cc97674e935002fc3d78361b696a69e init version: 949e6fa Security Options: seccomp Profile: default Kernel Version: 4.15.7-1-ARCH Operating System: Arch Linux OSType: linux Architecture: x86_64 CPUs: 4 Total Memory: 7.643GiB Name: padme ID: SR5W:2GPM:CDIM:OEQD:GPY4:ATIR:L7B5:AMPP:742G:BVKE:ITND:FLYW Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Username: leryan Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false
Additional environment details (AWS, VirtualBox, physical, etc.):
Physical with SSD.
Answer questions fractos
Removing report - this is for BTRFS. Sorry.