-
Notifications
You must be signed in to change notification settings - Fork 88
Open
Description
- This is a bug report
- This is a feature request
- I searched existing issues before opening this one
Expected behavior
can really pull the image success.
Actual behavior
1.I found the image to be built success
2.I use the docker manifest inspect cmd, found the manifest is error

Steps to reproduce the behavior
😭 I am so sorry that I can't copy the text to report the issue, beacuse our company is use inner net to work while has not realized extranet copy 😭
-
Although that, it is successful to push to the docker mirror.
-
In one client to pull the image
$ docker pull docker.das-security.cn/soos/be:2.19-develop
2.19-develop: Pulling from soos/be
801bfaa63ef2: Already exists
5c04d2b8969b: Already exists
bf6244544f6b: Already exists
2ad3570d904e: Already exists
c43670c45341: Already exists
2a7d0bc3cc43: Already exists
dda257cff13a: Already exists
1c3a40aa0bf3: Pulling fs layer
3d034f51e5d0: Pulling fs layer
0792246f88ac: Pulling fs layer
2e37f1ce5ec7: Waiting
error pulling image configuration: unknown blobOutput of docker version:
Output of docker info:
Additional environment details (AWS, VirtualBox, physical, etc.)
Metadata
Metadata
Assignees
Labels
No labels


