dockerhub

问题 I am trying to create a swarm setup on my laptop. I am running swarm daemon on laptop, and running 2 Ubuntu 14.04 VM as docker node. On one of the nodes I am able to run swarm and I can connect to swarm daemon. I can list the node with docker info and spawn a container on it. But when I try to pull swarm image on another VM node, I get the following error: pensu@pensu-virtual-machine:~$ sudo docker pull swarm Pulling repository swarm FATA[0025] Get https://index.docker.io/v1/repositories

问题 Suppose I have an image me/mystuff:v0.0.1 I find if I push it to the repository: docker push me/mystuff:v0.0.1 latest is not created, and on a pull from another machine it will complain, e.g. ssh me@faraway (faraway) $ docker run -it me/mystuff /bin/bash will result in a not found error for me/mystuff:latest I can add the latest tag and push explicitly to the public repository: docker login me docker tag me/mystuff:v0.0.1 me/mystuff:latest docker push me/mystuff:latest and then from another

问题 Suppose I have an image me/mystuff:v0.0.1 I find if I push it to the repository: docker push me/mystuff:v0.0.1 latest is not created, and on a pull from another machine it will complain, e.g. ssh me@faraway (faraway) $ docker run -it me/mystuff /bin/bash will result in a not found error for me/mystuff:latest I can add the latest tag and push explicitly to the public repository: docker login me docker tag me/mystuff:v0.0.1 me/mystuff:latest docker push me/mystuff:latest and then from another

问题 Suppose I have an image me/mystuff:v0.0.1 I find if I push it to the repository: docker push me/mystuff:v0.0.1 latest is not created, and on a pull from another machine it will complain, e.g. ssh me@faraway (faraway) $ docker run -it me/mystuff /bin/bash will result in a not found error for me/mystuff:latest I can add the latest tag and push explicitly to the public repository: docker login me docker tag me/mystuff:v0.0.1 me/mystuff:latest docker push me/mystuff:latest and then from another

问题 I am planning to deploy an application in my kubernetes-clustering infra. I pushed image to dockerhub repo. How can I pull image from dockerhub? 回答1: One line command to create a Docker registry secret kubectl create secret docker-registry regcred --docker-username=<your-name> --docker-password=<your-pword> --docker-email=<your-email> -n <your-namespace> Then you can use it in your deployment file under spec spec: containers: - name: private-reg-container-name image: <your-private-image>

问题 When we use Docker it's very easy push and pull image in a public repository in our https://hub.docker.com but this repository it's free only for public image(only one can be private). Currently it's possible to execute a reverse engineering of a public image in repository and read the source code of project ? 回答1: You can check how an image was created using docker history <image-name> --no-trunc Update: Check dive which is a very nice tool that allows you to views image layers. 回答2: As

问题 I am creating an image in the docker to the mysql install mode, but it is giving error to start mysql. My Dockerfile The error occurs when processing and line 25 of Dockerfile: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) I found that the error occurs because mysql is not running. The docker print below to rotate the line 22: bin boot dev etc home lib lib64 media mnt opt proc root run sbin scripts srv sys tmp usr var MySQL is stopped. Stack trace

问题 I have a repository that uses git submodules, and I configured the automated build on Docker Hub. At the beginning of the build process, it looks like Docker Hub pulls the repository from the default branch (master), update submodules and then checkout to the particular branch (let's say branch feature-a) that triggered the build. It works fine if feature-a branch has the very same submodules as master, but if the submodules are different (let's say, pull one submodule from a different repo),

问题 I'm trying to create one image for different architectures, namely for amd64 and arm64. The Dockerfile I've created is identical in its contents. When I build from this Dockerfile on my main machine, which is on amd64, the resultant image will run on all other amd64 machines. However, when I attempt to run this image on arm64, I will see exec errors. The main culprit seems to stem from my use of Ubuntu as the base image ( FROM: ubuntu:latest ), which somehow "knows" which architecture on

问题 I am using RUN instruction within a Dockerfile to install a rpm RUN yum -y install samplerpm-2.3 However, I want to pass the value "2.3" as an argument. My RUN instruction should look something like: RUN yum -y install samplerpm-$arg where $arg=2.3 回答1: You are looking for --build-arg and the ARG instruction. These are new as of Docker 1.9. Check out https://docs.docker.com/engine/reference/builder/#arg. This will allow you to add ARG arg to the Dockerfile and then build with docker build -