I am attempting to follow the docker get-started tutorial and have encountered a problem on part 2 under the section
Pull and run the image from the remote repository
The command it says to run is
docker run -p 4000:80 username/repository:tag
I run that:
sudo docker run -p 4000:80 <username>/getting -started:part2
and I get
Unable to find image '<username>/getting-started:part2' locally
docker: Error response from daemon: manifest for <username>/getting-started:part2 not found.
See 'docker run --help'.
âdocker run --helpâ is just a list of command options for run so is no help.
Since I followed the previous instructions in the tutorial I have the repository on docker hub, and can see it there, so the push was successful.
I donât understand what I am doing wrong or why I canât pull it down.
Can anyone see my mistakes or figure out why it canât find the image and the error shows up?
I am using an Amazon Linux 2 machine one AWS EC2, with mobaxterm.
I had the same problem at first, then I checked the spelling. I wrote get-startet instead of get-started. Maybe you have (or had) the same problem. Maybe this post helps some newbies
You are aware that the previous steps to buid, tag an push the image (after a docker login of course) are cruical for the endavor to work. Either one of those steps didnât finish with success OR reponame:tag is not used consistently between the steps.
Faced the same issue.
here is what I did.
Right next to the image you wanted to download, there is a command. something like this.
docker pull oraclelinux
I got the same error.
Error response from daemon: manifest for oraclelinux:latest not found: manifest unknown: manifest unknown
What I did:
Click on View available tags below the command.
choose a image from the list which shows up.
docker pull oraclelinux:8.3
I hope your error is resolved. But for many who are trying to pull the image from the docker hub. The issue is that you havenât pushed anything to that repo. So go to command prompt to your working directory and push that code to your repo using âdocker push docker_id/repo_nameâ or tag your local image to the repo if that is the case.
Hope this resolves the issue.
Uhh this is my first time using Docker and I get Errors in the tutorial? I am literally clicking the command, it copy pastes and it throws an error? on step 2. Are you kidding me with this? Why would I use this program if I cant even get through the supposed âteach me how to use this thingâ step? Now I just have this bad experience to go off of and I have learned nothing
Docker requires some knowledge about Linux or at least some about working with command lines. The commands that you quoted are wrong, because of the missing line breaks. Although you did not tell us where you click on the commands (you canât click on those in the web based tutorial that way), I guess you are trying to use Docker Desktopâs Quick start guide.
Those commands are not running automatically. You need to press enter so you can change to command before running it. It is useful when you donât want that âgetting-startedâ folder in your home folder so you can copy that somewhere else. But now that you mention it, I am not sure that is a feature and not a bug. It was totally logical to me, but when a step contains multiple commands, only the last command will be waiting for an ENTER.
If you just click âNext stepâ, you will insert an other command before executing the previou command. ON the other hand, your error message indicates that you did not even click on âNext Stepâ, because cd getting-started should be the first line and the docker build the second.
So I guess you
started the quick start guide
Clicked on the first commands to insert those into the terminal, as a result you cloned the âgetting-startedâ project from github
Pressed ENTER, so you copied the âgetting-startedâ folder to your home folder.
Clicked on âNext stepâ to get these commanda:
cd getting-started
docker build -t docker101tutorial .
As a result of the previous point, you changed the directory to âgetting-startedâ, but the second line remained in your terminal waiting for an ENTER
You did not press ENTER, nor the âNext stepâ button, but clicked on the same commands again, so you get this the previous line:
which had a line break after âgetting-startedâ so tried to execute the invalid command.
Let us know, if you still have problem, but try to always explain where you get an error message, what you tried to use exactly, so we can try to help, and if it turns out, you found a bug, we can tell you where you can report it, or depending on the issue, report it for you.
Note that, this is a community forum, so most of us are not Docker staff and we donât maintain official tutorials, especially not Docker Desktop, so we canât fix it.
I did something similar, using windows.
After reading everything again I managed to solve:
After logging in (by powershell or docker), still in the path of the previously downloaded âappâ, use:
docker tag getting-started YOUR-USER-NAME/getting-started
