Im new to Docker and followed very simple steps in my Mac(Intel Version). Downloaded Docker and moved to applications. Post that, I have tried docker-compse for almost 10 different images available from docker website. No matter which images, I always end at the error filesystem layer verification failed for digest sha256
I have tried few solutions which are out there. But none have resolved the issue.
Appreciate any help from the community here!
Additional Details -
Mac OS: Catalina 10.15.7
Docker Version: 20.10.16
Docker-compose Version: 1.29.2
Related
I was using version: '3' for the docker-compose, works fine in my host machine (macOS), but when I tried to build the images and run the containers in the server, I got the response
Version in "./docker-compose.dev.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a version of "2" (or "2.0") and place your service definitions under the services key, or omit the version key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/
OS Ubuntu "16.04.6 LTS (Xenial Xerus)" in AWS (ec2)
Docker version 19.03.8
docker-compose version 1.8.0, build unknown
I found a way around and it is to use version 2, How can I solve this?
I recently migrated my dev environment from Windows Home to Pro and as part of the upgrade installed Docker Desktop instead of using Docker Toolbox.
After the upgrade, using the default Docker Desktop instance I kept receiving some variation on the below error.
Error response from daemon: Get https://docker.abc.xyz.net/v1/users/:
x509: certificate is valid for *.xyz.net, xyg.net, not
docker.abc.xyz.net
What could be causing the problem? I have searched around the internet for hours and all the different solutions have no effect. Restarting Docker, uninstall and reinstall.
Can anybody help?
It appears as part of the migration from Docker Toolbox to Docker Desktop a number of entries are leftover in the hosts file on Windows that cause a conflict when Docker is trying to access any external network. The simple fix? Remove these 5 lines from my hosts file
52.3.153.154 index.docker.io
34.200.28.105 registry.docker.io
52.20.146.203 registry-1.docker.io
54.152.209.167 auth.docker.io
52.222.149.24 dseasb33srnrn.cloudfront.net
C:\Users\mites>docker pull busybox
Using default tag: latest
latest: Pulling from library/busybox
no matching manifest for unknown in the manifest list entries
How to solve this ? it occours up on every pull command.
I was running my app on Windows 10 Pro, Docker CE, windows containers when I got this error.
I switched to using linux containers and it resolved this issue for me.
Note: I was using python, reddis in this scenario for my app.
Hope this helps someone.
I had the same problem on my Windows 10 Pro.
While checking the docker logs I found more explanatory log entries:
[09:32:42.958][WindowsDaemon ][Info ] debug: a Windows version 10.0.17763-based image is incompatible with a 10.0.17134 host
[09:32:42.958][WindowsDaemon ][Info ] debug: no matching manifest for unknown in the manifest list entries
The solution was to update my Windows 10 Pro installation to a later version. After that, I was able to pull the image from the repo.
I installed Docker on a Red Hat Enterprise Linux Server 7.5 (Maipo) system:
docker version
Version: 1.13.1
API version: 1.26
Package version: docker-1.13.1-58.git87f2fab.e17.x86_64
OS/Arch: linux/amd64
Now if I try to run a docker image, I get errors similar to this:
docker run docker.io/jupyter/datascience-notebook
tini: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
I have searched for help and have already taken a multitude of possible actions:
libraries seem to be linked correctly
all libraries are up to date
Hello-World example works
I also came across information saying that running containers from docker.io / hub.docker.com under RHEL is not supported - which I don't really get, as main purpose of docker is to enable running programs independent from their OS...?
https://access.redhat.com/solutions/1408853 Does this mean using docker under RHEL does not really provide me with the possibility of easily deploying/sharing a docker-image with non-RHEL users?
Also, does this mean I can only access and use official RHEL-docker images?
https://access.redhat.com/containers/?start=90#/search/
As I wanted to use docker to have ready-to-go environments with R-Python/Jupyter/H2o (and similar), I'm disappointed because I could not find suitable images for RHEL there.
So, my questions would be:
Is it possible to run docker.io / hub.docker.com images under RHEL7.5?
if not, could I share my own created docker images under RHEL7.5 to other users with different OS versions?
Are there other projects / sites to share docker-images for data science purposes on RHEL?
Would you agree that my next step would be: building my own docker-image, adding R/Python/jupyter step by step?
Best regards,
workah0lic
This error message
tini: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
comes from within the container image. It could be a corrupted container image, but the message is also printed when the glibc dynamic linker determines that the kernel features are not sufficient for loading libc.so.6. I looked at the image (digest is sha256:79f929bd0e58fa9cb238dceda48b0c8360e748d09b476b429216c93dac0bd783), and it appears to require kernel 3.2, so the Red Hat Enterprise Linux 7 kernel version of 3.10 should be sufficient.
In fact, I cannot reproduce this problem with kernel-3.10.0-862.6.3.el7.x86_64 and docker-1.13.1-58.git87f2fab.el7.x86_64. You could try to run this command to obtain additional information about dynamic linker behavior:
docker run -e LD_DEBUG=all docker.io/jupyter/datascience-notebook
I have been getting the following problem after getting Docker set-up on a Mac OS using the Docker Toolbox:
Pulling repository docker.io/library/hello-world
Error while pulling image: Get https://index.docker.io/v1/repositories/library/hello-world/images: x509: certificate signed by unknown authority
I have seen some potential solutions to this problem on StackOverflow, but none of them seems to be working for me. For example, I have checked the date, which is set correctly in my case. Does anyone know of a solution for the Docker Toolbox on a Mac OS X?