manifest for bitwarden/self-host:beta not found - docker

I can't figure out why simple command to pull docker image for self-host bitwarden results in error:
Command:
docker pull bitwarden/self-host:beta
Result:
Error response from daemon: manifest for bitwarden/self-host:beta not found
Update (Feb-4-2023):
Looks like the issue is spreading, now I can't pull parseplatform/parse-server:latest, however I can pull parseplatform/parse-server:5.4.0 - which was pushed 4 month ago.

Related

Dockerhub image pull error due to image registry unavailable

I cannot pull hello world image and other images just after 15:00 CST today but can do that yesterday and this morning CST.
$docker pull hello-world
Using default tag: latest
Error response from daemon: Get https://registry-1.docker.io/v2/library/hello-world/manifests/latest: Get https://auth.docker.io/token?scope=repository%3Alibrary%2Fhello-world%3Apull&service=registry.docker.io: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
May I know how to fix it?
It is working now...
- $ docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
0e03bdcc26d7: Pull complete
Not sure what happened.

Pulling docker image to Heroku container

I am trying to deploy a Docker Image to Heroku. The image is external and hosted on https://quay.io/repository/mldb/mldb?tab=info.
To run the image, I have created an app on Heroku. The app is called still-dawn-24875.
I log into the heroku container.
Now I am trying to pull the docker image from repository. I am running the following command -
heroku container:pull --verbose --app=still-dawn-24875 mldb
The command is throwing following error -
=== Pulling mldb as registry.heroku.com/still-dawn-24875/mldb
heroku-container-registry docker [ 'pull', 'registry.heroku.com/still-dawn-24875/mldb' ] +0ms
Using default tag: latest
Error response from daemon: manifest for
registry.heroku.com/still-dawn-24875/mldb:latest not found: manifest
unknown: manifest unknown
! 1
I have tried this with another repository on Docker Hub as well. It gives me the same error.
Any idea on what could be the issue and how we can resolve this?

Error response from daemon: manifest error

I am new user of docker and i try to create my first image as a test
https://hub.docker.com/r/abdelmun3m/munemdockertest/
put i get this error while i am trying to pull my image and add code
Using default tag: latest
Error response from daemon: manifest for abdelmun3m/munemdockertest:latest not found
what is the problem !?
There are no images in your repository.
You need to either tag your image with your username as a prefix when building it:
docker build -t abdelmun3m/munemdockertest .
Or tag an existing image:
docker tag <existing image name> abdelmun3m/munemdockertest
then log into docker hub
docker login
and then push that image
docker push abdelmun3m/munemdockertest
See the documentation for more details.

ImagePullBackOff: Kubernetes error with Nexus based Private Registry

I had initially thought this was the same as: Kubernetes imagePullSecrets not working; getting "image not found"
However, even disabling authentication (to avoid the need for secrets) still produces the same error.
So, Kubernetes trying to pull images from Nexus Docker registry keeps producing the kubernetes error:
"Failed to pull image "nexus.mydomain.co.uk/nginx": Error: image nginx:latest not found"
This is also reflected in the Nexus logs:
2016-06-22 14:51:26,929+0000 WARN [qtp556619582-227] docker org.sonatype.nexus.repository.docker.internal.V1Handlers - Error: GET /v1/repositories/nginx/images: 404 - org.sonatype.nexus.repository.docker.internal.V1Exception$ImagesNotFound: images not found
I can't get onto the kube boxes to try a pull, however, when I run "docker pull" from my mac command line all is well and good.

What does HTTP 400 when pulling docker image mean?

I am asking docker to build an ASP.NET 5 beta6 application image for me at Ubuntu 14.04.1 virtual machine:
docker build -t instanceName .
using dockerfile that starts with:
FROM microsoft/aspnet:1.0.0-beta6
It responds with this message:
Sending build context to Docker daemon 124.4 kB
Sending build context to Docker daemon
Step 0 : FROM microsoft/aspnet:1.0.0-beta6
Pulling repository microsoft/aspnet
9424b500cebc: Error pulling image (1.0.0-beta6) from microsoft/aspnet, HTTP code 400
ba249489d0b6: Download complete
19de96c112fc: Download complete
b92a854a78d0: Download complete
63e9265ef57c: Error pulling dependent layers
INFO[0019] Error pulling image (1.0.0-beta6) from microsoft/aspnet, HTTP code 400
It does similar thing when I replace dockerfile definition to just FROM microsoft/aspnet.
What does it mean? If it were 404, I would understand that there is no such image. But "Bad Request"? Can I make the request... better?

Resources