CODEWITHSUNDEEP
macosdockerdocker-run
Xameer
Xameer

Reputation: 31247

Unable to find docker image locally

I was following this post - the reference code is on GitHub. I have cloned the repository on my local.

The project has got a react app inside it. I'm trying to run it on my local following step 7 on the same post:

docker run -p 8080:80 shakyshane/cra-docker

This returns:

Unable to find image 'shakyshane/cra-docker:latest' locally
docker: Error response from daemon: pull access denied for shakyshane/cra-docker, repository does not exist or may require 'docker login'.
See 'docker run --help'.

I tried login to docker again but looks like since it belongs to @shakyShane I cannot access it.

I idiotically tried npm start too but it's not a simple react app running on node - it's in the container and containers are not controlled by npm

Looks like docker pull shakyshane/cra-docker:latest throws this:

Error response from daemon: pull access denied for shakyshane/cra-docker, repository does not exist or may require 'docker login'

So the question is how do I run this docker image on my local mac machine?

Upvotes: 119

Views: 399719

Answers (15)

eliasfern4ndes
eliasfern4ndes

Reputation: 1

1 - find your container:

sudo docker ps -a

2 - start your container:

sudo docker start <your_container>

Upvotes: 0

Mathix420
Mathix420

Reputation: 1287

Since Docker 23.0, docker build has become an alias for docker buildx build.

You might be using a custom builder instance.

Set the builder instance to default with this command and run your build command again.

docker buildx use default

Upvotes: 0

Xameer
Xameer

Reputation: 31247

Well this is illogical but still sharing so future people like me don't get stuck.

The problem was that I was trying to run a docker image which doesn't exist.

I needed to build the image:

docker build . -t xameeramir/cra-docker

And then run it:

docker run -p 8080:80 xameeramir/cra-docker

Upvotes: 74

Be_Young
Be_Young

Reputation: 1

At first, i build image on mac-m1-pro with this command docker build -t hello_k8s_world:0.0.1 ., when is run this image the issue appear.

After read Master Yi's answer, i realize the crux of the matter and rebuild my images like this docker build --platform=arm64 -t hello_k8s_world:0.0.1 .

Finally，it worked.

Upvotes: 0

Hritik Rajendra Akolkar
Hritik Rajendra Akolkar

Reputation: 25

Use -d

sudo docker run -d -p 8000:8000 rasa/duckling

learn about -d here

sudo docker run --help

Upvotes: 0

xMilos
xMilos

Reputation: 2018

Posting my solution since non of the above worked. Working on macbook M1 pro.

The issue I had is that the image was built as arm/64. And I was running the command:

docker run --platform=linux/amd64 ...

So I had to build the image for amd/64 platform in order to run it.

Command below:

docker buildx build --platform=linux/amd64 ...

In conclusion your docker image platform and docker run platform needs to be the same from what I experienced.

Upvotes: 55

Adham
Adham

Reputation: 21

In my case, I didn't realise there was a difference between docker run and docker start, and I kept using the run command when I should've been using the start command.

FYI, run is for building and creating the docker container, start is to just start a stopped container

Upvotes: 2

Israel Camacho Rivera
Israel Camacho Rivera

Reputation: 31

The simplest answer can be the correct one!.. make sure you have permissions to execute the command, use:

sudo docker run -p 8080:80 shakyshane/cra-docker

Upvotes: 2

Leila Talebzadeh
Leila Talebzadeh

Reputation: 101

In my case, the docker image did exist on the system and still I couldn't run the container locally, so I used the exact image ID instead of image name and tag, like this:

docker run myContainer c29150c8588e

Upvotes: 10

Clintm
Clintm

Reputation: 4877

This just happened to me because my local docker vm on macos ran out of disk space.

I just deleted some old images using docker image prune and it started working correctly again.

Upvotes: 3

Ninad Pingale
Ninad Pingale

Reputation: 7069

In my case, my image had TAG specified with it and I was not using it.

REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
testimage          testtag            189b7354c60a        13 hours ago        88.3MB

Unable to find image 'testimage:latest' locally for this command docker run testimage

So specifying tag like this - docker run testimage:testtag worked for me

Upvotes: 42

codester
codester

Reputation: 117

In my case, I saw this error when I had logged in to the dockerhub in my docker desktop. The repo I was pulling was local to my enterprise. Once i logged out of dockerhub, the pull worked.

Upvotes: 2

Julian Macagno
Julian Macagno

Reputation: 11

The problem is you are trying to run an imagen that does not exists. If you are executing a Dockerfile, the image was not created until Dockerfile pass with no errors; so when Dockerfile tries to run the image, it can't find it. Be sure you have no errors in the execution of your scripts.

Upvotes: 1

Cryptc
Cryptc

Reputation: 3595

I received this error message when I typed the name/character wrong. That is, "name1\name2" instead of "name1/name2" (wrong slash).

Upvotes: 8

Richard Barber
Richard Barber

Reputation: 6431

shakyshane/cra-docker Does not exist in that user's repo https://hub.docker.com/u/shakyshane/

Upvotes: 1

Related Questions