I cannot run docker:dind as docker:docker even I intuitively should:
[sad#localhost ~]$ docker pull docker
Using default tag: latest
latest: Pulling from library/docker
540db60ca938: Already exists
5a38b3726f4b: Already exists
e5fa5deb3340: Already exists
2b7e0e3b7545: Already exists
493333e9491f: Already exists
28d445cfca76: Already exists
32eb6dfb9227: Already exists
Digest: sha256:ad50b8d78b41dc52f42ab123ce0e3f48c54437ed70ecc2a44c99e889924c8e56
Status: Downloaded newer image for docker:latest
docker.io/library/docker:latest
[sad#localhost ~]$ docker run --privileged -d docker:docker
Unable to find image 'docker:docker' locally
docker: Error response from daemon: manifest for docker:docker not found: manifest unknown: manifest unknown.
See 'docker run --help'.
[sad#localhost ~]$
Is this by design, that I should reference the docker:docker image as docker:dind?
Thank you.
You have to change
docker run --privileged -d docker:docker
into
docker run --privileged -d docker:latest
Related
I'm running Docker on my Synology DS918+ and I'm looking to run the jetbrains/teamcity-server container.
When I run the following command:
sudo docker run teamcity-server -v /volume2/docker/teamcity-server/datadir/:/data/teamcity_server/datadir -v /volume2/docker/teamcity-server/logs/:/opt/teamcity/logs -p 8001:8001 jetbrains/teamcity-server:latest
I get a result back that it can't find the image locally:
Unable to find image 'teamcity-server:latest' locally
docker: Error response from daemon: pull access denied for teamcity-server, repository does not exist or may require 'docker login'.
See 'docker run --help'.
I believe that I have confirmed that I have the image installed locally because when I run the command:
sudo docker images
I get the following result:
REPOSITORY TAG IMAGE ID CREATED SIZE
jetbrains/teamcity-server latest bfe4a2f841c1 2 weeks ago 2.2GB
The correct way is to use --name before the container name (teamcity-server). Otherwise, docker will think that it is the image that you are trying to pull and error out.
sudo docker run --name teamcity-server -v /volume2/docker/teamcity-server/datadir/:/data/teamcity_server/datadir -v /volume2/docker/teamcity-server/logs/:/opt/teamcity/logs -p 8001:8001 jetbrains/teamcity-server:latest
I want run this line:
docker run --name myjenkins1 -v myvoll:/var/jenkins_home -p 8080:8080 -p 50000:50000 jenkins
But result is:
Unable to find image 'jenkins:latest' locally
docker: Error response from daemon: manifest for jenkins:latest not found: manifest unknown: manifest unknown.
See 'docker run --help'.
How can i solve this ...
The jenkins image has been deprecated for over 2 years in favor of the jenkins/jenkins:lts image provided and maintained by the Jenkins Community as part of the project's release process.
Use below image:
docker pull jenkins/jenkins
docker run -p 8080:8080 --name=jenkins-master -d jenkins/jenkins
For more info:
https://hub.docker.com/r/jenkins/jenkins
docker pull jenkins
Will not work as it is deprecated.
DEPRECATED; use "jenkins/jenkins:lts" instead use
docker pull jenkins/jenkins:lts
Use : docker run -p 8080:8080 jenkins/jenkins
Use
docker pull jenkins/jenkins
Not
docker pull jenkins
Jenkins will give an error response if you are trying to use the latest tag.
so you can execute your command as the following :
docker run --name myjenkins1 -v myvoll:/var/jenkins_home -p 8080:8080 -p 50000:50000 jenkins/jenkins
When using new m1 chip macbooks, just pulling the jenkins latest ,will give below error.
docker pull jenkins
Using default tag: latest
Error response from daemon: manifest for jenkins:latest not found: manifest unknown: manifest unknown
solution : docker pull jenkins/jenkins
Type docker search jenkins in the terminal
result
(base) kimseongjung#song-ui-MacBookPro ~ % docker search jenkins
NAME DESCRIPTION STARS OFFICIAL AUTOMATED
jenkins DEPRECATED; ***use "jenkins/jenkins:lts" <-※ here!!!!!!! instead 5548 [OK]
jenkins/jenkins The leading open source automation server 3223
jenkins/jnlp-slave a Jenkins agent which can connect to Jenkins… 151 [OK]
jenkins/inbound-agent
The message says that jenkins is deprecated and that jenkins/jenkins:lts should be used instead.
typing the code below into the terminal will solve the problem.
docker pull jenkins/jenkins:lts
thank you.
You might be running a deprecated code. Use docker compose instead of docker-compose.
docker pull jenkins/jenkins
This works in AWS latest in 2023 without getting any error
The issue happens when entire workflow starts right after Init Containers in Github Actions at actions/checkout#v2.1.0 it spills:
Run actions/checkout#v2.1.0
/usr/bin/docker exec c30dd34bb8ac19329d0971b0808f9a4440b20a31283dbfb70b5249619e3dc894 sh -c "cat /etc/*release | grep ^ID"
Error response from daemon: Container c30dd34bb8ac19329d0971b0808f9a4440b20a31283dbfb70b5249619e3dc894 is not running
Init Containers Log:
Checking docker version
Clean up resources from previous jobs
Create local container network
Starting job container
/usr/bin/docker pull rafal1137/etlraspbian
Using default tag: latest
latest: Pulling from rafal1137/etlraspbian
31994f9482cd: Pulling fs layer
76b671f957fb: Pulling fs layer
2782b509b7bd: Pulling fs layer
31994f9482cd: Verifying Checksum
31994f9482cd: Download complete
2782b509b7bd: Verifying Checksum
2782b509b7bd: Download complete
76b671f957fb: Verifying Checksum
76b671f957fb: Download complete
31994f9482cd: Pull complete
76b671f957fb: Pull complete
2782b509b7bd: Pull complete
Digest: sha256:c7690eb05c396ab1cda53e2d5a79fa3813f6d2ab673ef42eb3f8d94cbde31ac2
Status: Downloaded newer image for rafal1137/etlraspbian:latest
docker.io/rafal1137/etlraspbian:latest
/usr/bin/docker create --name c2c1009c0f8a45debcf7b67d292ec3fc_rafal1137etlraspbian_5d0ed5 --label 5588e4 --workdir /__w/etlegacy/etlegacy --network github_network_4c8199090d9347ee87e039d67b6a0a4a -e "HOME=/github/home" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work":"/__w" -v "/home/runner/runners/2.277.1/externals":"/__e":ro -v "/home/runner/work/_temp":"/__w/_temp" -v "/home/runner/work/_actions":"/__w/_actions" -v "/opt/hostedtoolcache":"/__t" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" --entrypoint "tail" rafal1137/etlraspbian "-f" "/dev/null"
WARNING: The requested image's platform (linux/arm) does not match the detected host platform (linux/amd64) and no specific platform was requested
c30dd34bb8ac19329d0971b0808f9a4440b20a31283dbfb70b5249619e3dc894
/usr/bin/docker start c30dd34bb8ac19329d0971b0808f9a4440b20a31283dbfb70b5249619e3dc894
c30dd34bb8ac19329d0971b0808f9a4440b20a31283dbfb70b5249619e3dc894
/usr/bin/docker ps --all --filter id=c30dd34bb8ac19329d0971b0808f9a4440b20a31283dbfb70b5249619e3dc894 --filter status=running --no-trunc --format "{{.ID}} {{.Status}}"
c30dd34bb8ac19329d0971b0808f9a4440b20a31283dbfb70b5249619e3dc894 Up Less than a second
/usr/bin/docker inspect --format "{{range .Config.Env}}{{println .}}{{end}}" c30dd34bb8ac19329d0971b0808f9a4440b20a31283dbfb70b5249619e3dc894
HOME=/github/home
GITHUB_ACTIONS=true
CI=true
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
Waiting for all services to be ready
Container Used
Tested locally on my pc container seems to work without issues.
I believe the issue is that you're building in linux/arm and Github is using linux/amd64.
The requested image's platform (linux/arm) does not match the detected host platform (linux/amd64) and no specific platform was requested.
Try building the image under linux/amd64 with Docker buildx or, if you're using Docker compose, with Platform option, then push it and try again.
I run the following docker command. I don't understand why it is failed. Could you show me how to debug this? Thanks.
$ docker run -v `pwd`:/share -ti --name aerospike-aql --rm aerospike/aerospike-tools aql --host 192.168.1.191 --no-config-file
Unable to find image 'aerospike/aerospike-tools:latest' locally
latest: Pulling from aerospike/aerospike-tools
6ec7b7d162b2: Pull complete
177617b11d13: Pull complete
10273812b9e3: Pull complete
ac553cdb1df6: Pull complete
d633ea8cb425: Pull complete
1f91817a9ef3: Pull complete
403620a9a728: Pull complete
3a80741c7bbc: Pull complete
Digest: sha256:109801d7e8440dcf53461b13b55eaa96c1f86482209691285a34c6bb2fee4e1d
Status: Downloaded newer image for aerospike/aerospike-tools:latest
Seed: 192.168.1.191
User: None
Config File: None
2021-01-16 02:46:44 WARN Failed to connect to seed 192.168.1.191 3000. AEROSPIKE_ERR_CONNECTION Socket write error: 111, 192.168.1.191:3000
Error -10: Failed to connect
To add to Micah's comment I can suggest running again the server image, and then the command below that is not using the hardcoded host IP 192.168.1.191 but rather pulls it from the settings:
$ docker run --rm -tid --name aerospike -p 3000:3000 -p 3001:3001 -p 3002:3002 -p 3003:3003 aerospike/aerospike-server
$ docker run -v `pwd`:/share -ti --name aerospike-aql --rm aerospike/aerospike-tools aql --host $(docker inspect -f '{{.NetworkSettings.IPAddress }}' aerospike) --no-config-file
I'm trying to mount a folder (/Users/.../src) on mac inside a docker container :
docker run -v /Users/.../src:/sharedVolume/git_src_on_mac -v <DOCKER_MACHINE_NAME> /bin/bash
and it returns the following error:
Unable to find image '<DOCKER_MACHINE_NAME>:latest' locally
docker: Error response from daemon: repository <DOCKER_MACHINE_NAME> not found: does not exist or no pull access.
I'm using docker for mac Version 1.13.1, and here is the output of docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1ea17c622f80 <DOCKER_MACHINE_NAME> "/test/myproject.sh" About an hour ago Up About an hour 0.0.0.0:32783->5000/tcp <DOCKER_MACHINE_NAME>
Does anyone know what is the issue?
(Got the idea from #FaigB comment): I should have used the name of the image (docker image -a) with latest tag
docker run -v /Users/.../src:/sharedVolume/git_src_on_mac -i -t <DOCKER_IMAGE_NAME>:latest /bin/bash