Skip to content
This repository has been archived by the owner on Nov 6, 2023. It is now read-only.

ERROR: filesystem layer verification failed for digest #461

Open
mrdevops1 opened this issue May 9, 2019 · 15 comments
Open

ERROR: filesystem layer verification failed for digest #461

mrdevops1 opened this issue May 9, 2019 · 15 comments

Comments

@mrdevops1
Copy link

Following instructions in labs/windows/windows-containers/MultiContainerApp.md, after git clone https://github.com/dockersamples/dotnet-album-viewer.git at this step:

docker-compose up -d

Output is this:

nanoserver-1809: Pulling from dockersamples/tidb
6a5e981230da: Verifying Checksum
0b269bf5fe5f: Download complete
3e1bb0112f5d: Download complete
e4ea46d8914a: Download complete
b3289cfb42d9: Download complete
ERROR: filesystem layer verification failed for digest sha256:6a5e981230da7b34a25588f20c8b6b5366256ab1e0aadc0b7ecb566855bf4679

Windows 10 version is 1809 Build 17763.475

Docker Version:

Client: Docker Engine - Community
Version: 18.09.2
API version: 1.39
Go version: go1.10.8
Git commit: 6247962
Built: Sun Feb 10 04:12:31 2019
OS/Arch: windows/amd64
Experimental: false

Server: Docker Engine - Community
Engine:
Version: 18.09.2
API version: 1.39 (minimum version 1.24)
Go version: go1.10.6
Git commit: 6247962
Built: Sun Feb 10 04:28:48 2019
OS/Arch: windows/amd64
Experimental: true

Any suggestions to resolve the Error?

Thank you

@HugoScaramal
Copy link

HugoScaramal commented May 24, 2019

Had the same issue.
The only difference from your docker version is that the Server: Docker Engine has Experimental: false.

@evilC
Copy link

evilC commented Jun 12, 2019

Also seeing same thing here
Virtualized Win10 1809, same version as Hugo

@tmbull
Copy link

tmbull commented Sep 12, 2019

FWIW, I was able to work around this issue by changing the db image from dockersamples/tidb:nanoserver-1809 to dockersamples/tidb:nanoserver-sac2016. I don't know what the differences are, but I was able to pull this tag and the demo app started and ran successfully.

@ansariwn
Copy link

ansariwn commented Apr 2, 2020

Please fix this issue, it is still happening on Windows Server 2019.

@robert-lara
Copy link

Same issue here. I have tried running docker system prune -a on the server and desktop I am using for development. Even deleted the package in the gitlab registry, still cannot get around this issue.

@willzhang
Copy link

same at vmware env

(kolla-env) [root@kolla kolla-env]# docker pull registry.cn-shenzhen.aliyuncs.com/kollaimage/centos-binary-nova-libvirt:train
train: Pulling from kollaimage/centos-binary-nova-libvirt
524b0c1e57f8: Already exists 
2617be6e7870: Already exists 
e3a0a51835ff: Already exists 
5aca92fe88d1: Already exists 
d287ade7e595: Already exists 
401200978cd1: Already exists 
84ff0c4e7782: Already exists 
e7f87d129df3: Already exists 
7361f98e01c7: Already exists 
a22b6b56acd9: Already exists 
d44e6f808791: Already exists 
0573bce243ef: Already exists 
c82d02fcebce: Already exists 
94b9bab7943f: Already exists 
e38b3ec1357f: Already exists 
2b1839903372: Already exists 
5ef238ad315c: Already exists 
d88529840b2a: Already exists 
c7df1cc3120f: Already exists 
f497fa369757: Already exists 
e02eb938f823: Already exists 
0237e14f4ff5: Already exists 
9930ba1ac794: Already exists 
120db1951c14: Already exists 
a1ee6d8064dc: Already exists 
3e983884141f: Already exists 
3a6697d5e89f: Already exists 
aaa84eb468cc: Already exists 
55a5a19f23df: Already exists 
e85ef47e6275: Pull complete 
f3b1e3a1242d: Verifying Checksum 
9ff3d88462a1: Download complete 
f32425793517: Download complete 
032d2c8ca45e: Download complete 
filesystem layer verification failed for digest sha256:f3b1e3a1242d93455e13b206f5104cf135974e2636417d3d6956ded116ae7fe1
(kolla-env) [root@kolla kolla-env]# ^C
(kolla-env) [root@kolla kolla-env]# docker info
Client:
 Debug Mode: false

Server:
 Containers: 19
  Running: 19
  Paused: 0
  Stopped: 0
 Images: 26
 Server Version: 19.03.11
 Storage Driver: overlay2
  Backing Filesystem: xfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 3.10.0-1127.10.1.el7.x86_64
 Operating System: CentOS Linux 7 (Core)
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 7.62GiB
 Name: kolla
 ID: NYPM:Q76H:S6PX:2XOQ:HOBP:RG5Q:NUAM:J6RN:Z6XV:OF2F:2C6S:IEPX
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  registry.cn-shenzhen.aliyuncs.com
  127.0.0.0/8
 Live Restore Enabled: false

@rowenstuffer
Copy link

Has anyone solved this? I've tried it both with the original files and after editing the docker file and docker-compose from dockersamples/tidb:nanoserver-1809 to dockersamples/tidb:nanoserver-sac2016 as suggested by @tmbull and still can't run the project.

@gururajn
Copy link

Facing the same issue: ERROR: filesystem layer verification failed for digest sha256:cd5782d88a80967a205b111c575631852578504b977404b8c827716b074c646a, after prune and repeated builds.

@rowenstuffer
Copy link

@gururajn - We did a bunch of research into this and the problem is that the process pulls the wrong nanoserver down. You need "tidb: nanoserver 1809.tar". AlbumViewer doesn't work with later versions of Windows Nanoserver.

You should be able to pull a copy down here:

I'm including a document with all the steps we used to get the whole lab running.
Containers - Updated Docker and West Wind Viewer.docx

@gururajn
Copy link

gururajn commented Jan 19, 2021

Hi @rowenstuffer I'm running "docker-compose -f ./docker-compose.yml up --build" command on my mac. here is my docker info `Client:
Context: default
Debug Mode: false
Plugins:
app: Docker App (Docker Inc., v0.9.1-beta3)
buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)
scan: Docker Scan (Docker Inc., v0.5.0)

Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 2
Server Version: 20.10.2
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 269548fa27e0089a8b8278fc4fc781d7f65a939b
runc version: ff819c7e9184c13b7c2607fe6c30ae19403a7aff
init version: de40ad0
Security Options:
seccomp
Profile: default
Kernel Version: 4.19.121-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 1.944GiB
Name: docker-desktop
ID: YDQE:JGEF:DGKA:TM7L:HZBL:K7FQ:7EHX:4LEK:QX2G:NIMF:JJ6D:AZ2M
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: gateway.docker.internal:3128
HTTPS Proxy: gateway.docker.internal:3129
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false`

ERROR: I am getting is
ERROR: unexpected EOF
`

@rowenstuffer
Copy link

@gururajn - Right. So in the document I linked to, you're at about Item 7 of Step 2. Back way up to Item 2 in Step 2. You need the container with the correct version of Windows and you don't have that. Try to get that by using the links in my first response, then follow from my document at 2.2. I'm not sure what differences there are between Mac and Windows, but that SHA error comes from using an incompatible version of Windows container.

@gururajn
Copy link

gururajn commented Jan 21, 2021

hi @rowenstuffer I have tried the above suggested steps. I cloned repo. git clone https://github.com/dockersamples/dotnet-album-viewer.git and after that docker pull failed with below error.
Pulling db (dockersamples/tidb:nanoserver-1809)...
nanoserver-1809: Pulling from dockersamples/tidb
6a5e981230da: Pulling fs layer
0b269bf5fe5f: Download complete
3e1bb0112f5d: Download complete
e4ea46d8914a: Waiting
b3289cfb42d9: Waiting
ERROR: image operating system "windows" cannot be used on this platform

Looking at the error does tidb:nanoserver-1809 work in iOS platform?

@rowenstuffer
Copy link

Unfortunately, I don't know. I haven't tried this with iOS and don't have access to a system to try. Sorry!

@Dave-Lowndes
Copy link

It's so frustrating to be trying to learn something, following the example you're led to, and having it fail and then eventually finding this long standing report.
If this isn't going to be fixed, please get rid of the tutorial https://github.com/docker/labs/blob/master/windows/windows-containers/MultiContainerApp.md so that more people don't fall down this hole.

@gururajn
Copy link

@Dave-Lowndes thanks for the follow up and updates, I have updated my docker image(3.1) I don't see the above mentioned error. I can able to docker-compose.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants