
Please help me understand the difference between &#39;image&#39; and &#39;build&#39; within docker compose

Difference between &#39;image&#39; and &#39;build&#39; within docker compose

I am using kubernetes on a single machine for testing, I have built a custom image from the nginx docker image, but when I try to use the image in kubernetes I get an image pull error?????


**MY POD YAML**

&lt;!-- begin snippet: js hide: false --&gt;

&lt;!-- language: lang-none --&gt;

    kind: Pod
    apiVersion: v1
    metadata:
      name: yumserver
      labels:
        name: frontendhttp
    spec:
      containers:
        - name: myfrontend
          image: my/nginx:latest
          ports:
            - containerPort: 80
              name: &quot;http-server&quot;
          volumeMounts:
          - mountPath: &quot;/usr/share/nginx/html&quot;
            name: mypd
      imagePullSecrets:
        - name: myregistrykey

      volumes:
        - name: mypd
          persistentVolumeClaim:
           claimName: myclaim-1

&lt;!-- end snippet --&gt;


**MY KUBERNETES COMMAND**

kubectl create -f pod-yumserver.yaml



**THE ERROR**

&lt;!-- begin snippet: js hide: false --&gt;

&lt;!-- language: lang-none --&gt;

    kubectl describe pod yumserver


    Name: yumserver
    Namespace: default
    Image(s):	my/nginx:latest
    Node:		127.0.0.1/127.0.0.1
    Start Time:	Tue, 26 Apr 2016 16:31:42 +0100
    Labels:		name=frontendhttp
    Status:		Pending
    Reason:		
    Message:	
    IP:		172.17.0.2
    Controllers:	&lt;none&gt;
    Containers:
      myfrontend:
        Container ID:	
        Image:		my/nginx:latest
        Image ID:		
        QoS Tier:
          memory:		BestEffort
          cpu:		BestEffort
        State:		Waiting
          Reason:		ErrImagePull
        Ready:		False
        Restart Count:	0
        Environment Variables:
    Conditions:
      Type		Status
      Ready 	False 
    Volumes:
      mypd:
        Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
        ClaimName:	myclaim-1
        ReadOnly:	false
      default-token-64w08:
        Type:	Secret (a secret that should populate this volume)
        SecretName:	default-token-64w08
    Events:
      FirstSeen	LastSeen	Count	From			SubobjectPath			Type		Reason			Message
      ---------	--------	-----	----			-------------			--------	------			-------
      13s		13s		1	{default-scheduler }					Normal		Scheduled		Successfully assigned yumserver to 127.0.0.1
      13s		13s		1	{kubelet 127.0.0.1}					Warning		MissingClusterDNS	kubelet does not have ClusterDNS IP configured and cannot create Pod using &quot;ClusterFirst&quot; policy. Falling back to DNSDefault policy.
      12s		12s		1	{kubelet 127.0.0.1}	spec.containers{myfrontend}	Normal		Pulling			pulling image &quot;my/nginx:latest&quot;
      8s		8s		1	{kubelet 127.0.0.1}	spec.containers{myfrontend}	Warning		Failed			Failed to pull image &quot;my/nginx:latest&quot;: Error: image my/nginx:latest not found
      8s		8s		1	{kubelet 127.0.0.1}					Warning		FailedSync		Error syncing pod, skipping: failed to &quot;StartContainer&quot; for &quot;myfrontend&quot; with ErrImagePull: &quot;Error: image my/nginx:latest not found&quot;

&lt;!-- end snippet --&gt;






kubernetes cannot pull local image

Hi i&#39;m trying `docker push`

    [docker-simple-httpserver]# docker push myregistry/simplehttpserver:latest
    The push refers to a repository [myregistry/simplehttpserver] (len: 1)
    Sending image list
    FATA[0000] Error: Status 403 trying to push repository simplehttpserver: &quot;{\&quot;error\&quot;: \&quot;Unauthorized updating repository images\&quot;}&quot; 


is there a way for me to specify the `username` and `password` on `docker push` command?


Docker: How to authenticate for docker push?

My docker-compose.yml looks like the below and I am trying to follow the compose file from the docker registry documentation [here][1]. When i run docker-compose up I get the below error.

&gt; ERROR: In file &#39;./docker-compose.yml&#39;, service &#39;volumes&#39; must be a
&gt; mapping not an array.

```lang-yaml
registry:
  restart: always
  image: sudarshan/registry
  ports:
    - 5000:5000
environment:
  REGISTRY_HTTP_TLS_CERTIFICATE: /certs/domain.crt
  REGISTRY_HTTP_TLS_KEY: /certs/domain.key
  REGISTRY_AUTH: silly
  REGISTRY_AUTH_SILLY_SERVICE: SILLY_SERVICE
  REGISTRY_AUTH_SILLY_REALM: SILLY_REALM
volumes:
  - /usr/certs:/certs
```


  [1]: https://docs.docker.com/registry/deploying/


My docker version is

&gt; Docker version 1.12.1, build 23cf638

docker-compose version is 

&gt; docker-compose version 1.7.1, build 0a9ab35

Running on Ubuntu 16.04

EDIT:

Also tried

```lang-yaml
registry:
  restart: always
  image: sudarshan/registry
  ports:
    - 5000:5000
environment:
  REGISTRY_HTTP_TLS_CERTIFICATE: /certs/domain.crt
  REGISTRY_HTTP_TLS_KEY: /certs/domain.key
  REGISTRY_AUTH: silly
  REGISTRY_AUTH_SILLY_SERVICE: SILLY_SERVICE
  REGISTRY_AUTH_SILLY_REALM: SILLY_REALM
volumes:
    - /usr/certs:/certs
```

ERROR: In file &#39;./docker-compose.yml&#39;, service &#39;volumes&#39; must be a mapping not an array

I am trying to push an image to a local registry running in minikube but get the below error:

    Successfully built ee84225eb459
    Successfully tagged user/apiserver:0.0.1
    
    $ docker push localhost:5000/user/apiserver:0.0.1

    The push refers to a repository [localhost:5000/user/apiserver]
    An image does not exist locally with the tag: localhost:5000/user/apiserver
 
I have already tried starting minikube with below:

    minikube start --vm-driver xhyve --insecure-registry localhost:5000
    eval $(minikube docker-env)

An image does not exist locally with the tag: while pushing image to local registry

Gitlab provides a `.gitlab-ci.yml` template for building and publishing images to its own registry (click &quot;new file&quot; in one of your project, select `.gitlab-ci.yml` and `docker`). The file looks like this and it works out of the box :)

&lt;!-- language: lang-yaml --&gt;

    # This file is a template, and might need editing before it works on your project.
    # Official docker image.
    image: docker:latest

    services:
      - docker:dind

    before_script:
      - docker login -u &quot;$CI_REGISTRY_USER&quot; -p &quot;$CI_REGISTRY_PASSWORD&quot; $CI_REGISTRY

    build-master:
      stage: build
      script:
        - docker build --pull -t &quot;$CI_REGISTRY_IMAGE&quot; .
        - docker push &quot;$CI_REGISTRY_IMAGE&quot;
      only:
        - master

    build:
      stage: build
      script:
        - docker build --pull -t &quot;$CI_REGISTRY_IMAGE:$CI_COMMIT_REF_SLUG&quot; .
        - docker push &quot;$CI_REGISTRY_IMAGE:$CI_COMMIT_REF_SLUG&quot;
      except:
        - master

But by default, this will publish to gitlab&#39;s registry. How can we publish to [docker hub](https://hub.docker.com/) instead?

How to publish docker images to docker hub from gitlab-ci

I&#39;m using docker registry v1 and I&#39;m interested in migrating to the newer version, v2. But I need some way to get a list of images present on registry; for example with registry v1 I can execute a GET request to `http://myregistry:5000/v1/search?` and the result is:

    {
      &quot;num_results&quot;: 2,
      &quot;query&quot;: &quot;&quot;,
      &quot;results&quot;: [
        {
          &quot;description&quot;: &quot;&quot;,
          &quot;name&quot;: &quot;deis/router&quot;
        },
        {
          &quot;description&quot;: &quot;&quot;,
          &quot;name&quot;: &quot;deis/database&quot;
        }
      ]
    }

But I can&#39;t find on [official documentation][1] something similar to get a list of image on registry. Anybody knows a way to do it on new version v2?
 


  [1]: https://docs.docker.com/registry/spec/api/

How to get a list of images on docker registry v2

So I&#39;m new to ecs/ecr, but it seems like I have to name (with a tag) the image after the repository name in order to push that image to the repository.

So my question is: Is it intended that the user (me) would ONLY be pushing a single image and any associated versions of that image to a single repository in ecr, thus creating ANOTHER repository if i need to push a completely different image?

basically, one repo for nginx, one repo for postgressql, etc.

ECS/ECR: is common practice to have one repository per image (and associated versions)?

How can I create an AWS ECR repository if it doesn&#39;t already exist?

Create AWS ECR repository if it doesn&#39;t exist

I run a private docker registry, and I want to delete all images but the `latest` from a repository. I don&#39;t want to delete the entire repository, just some of the images inside it. The [API docs](https://docs.docker.com/registry/spec/api/) don&#39;t mention a way to do this, but surely it&#39;s possible?

How to delete images from a private docker registry?

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 &quot;2.3&quot; as an argument.
My RUN instruction should look something like:

    RUN yum -y install samplerpm-$arg

where `$arg=2.3`

How to pass arguments to a Dockerfile?

By default, if I issue command: 

    sudo docker pull ruby:2.2.1
it will pull from the docker.io offical site by default.

    Pulling repository docker.io/library/ruby
How do I change it to my private registry. That means if I issue 

    sudo docker pull ruby:2.2.1

it will pull from my own private registry, the output is something like:

    Pulling repository my_private.registry:port/library/ruby


How to change the default docker registry from docker.io to my private registry?

What is the right approach to make my [Amazon ECS](http://docs.aws.amazon.com/AmazonECS/latest/developerguide/Welcome.html) tasks update their Docker images, once said images have been updated in the corresponding registry?

How do I deploy updated Docker images to Amazon ECS tasks?

I&#39;d like to pull the images of CentOS, Tomcat, ... using their sha256 code, like in 

`docker pull myimage@sha256:0ecb2ad60`

But I can&#39;t find the sha256-code to use anywhere.

I checked the DockerHub repository for any hint of the sha256-code, but couldn&#39;t find any. I downloaded the images by their tag 

    docker pull tomcat:7-jre8

and checked the image with `docker inspect` to see if there&#39;s a sha256 code in the metadata, but there is none (adding the sha256 code of the image would probably change the sha256 code).

Do I have to compute the sha256 code of an image myself and use that? 

Where can I find the sha256 code of a docker image?

I have a docker 1.12 running on CentOS. I am trying to add insecure registry to it and things mentioned in documentation just don&#39;t work. The system uses `systemd` so I created a `/etc/systemd/system/docker.service.d/50-insecure-registry.conf` file.

    $ cat /etc/systemd/system/docker.service.d/50-insecure-registry.conf
    [Service]
    Environment=&#39;DOCKER_OPTS=--insecure-registry=&quot;hostname.cloudapp.net:5000&quot;&#39;

After loading daemon and restarting docker service, systemd shows that the environment variable is there 

    $ sudo systemctl show docker | grep Env
    Environment=DOCKER_OPTS=--insecure-registry=&quot;hostname.cloudapp.net:5000&quot;

But when I run `docker info` I don&#39;t see that insecure registry added 

    $ docker info
    ........
    Registry: https://index.docker.io/v1/
    WARNING: bridge-nf-call-iptables is disabled
    WARNING: bridge-nf-call-ip6tables is disabled
    Insecure Registries:
        127.0.0.0/8
   
Pushing images to `hostaneme.cloudapp.net` fails with  

    Pushing application     (hostname.cloudapp.net:5000/application:latest)...
    The push refers to a repository     [hostname.cloudapp.net:5000/mozart_application]
    ERROR: Get https://hostname.cloudapp.net:5000/v1/_ping: http: server gave HTTP response to HTTPS client

Is there something that could be done ? Am I missing something ? 

**UPDATE**

Resolved the issue by adding a file `/etc/docker/daemon.json` with following content

    {
        &quot;insecure-registries&quot; : [ &quot;hostname.cloudapp.net:5000&quot; ]
    }

And then restart docker 

    sudo systemctl daemon-reload
    sudo systemctl restart docker

After that insecure registry `hostname.cloudapp.net:500` works.





Add Insecure Registry to Docker

I cannot find a way of moving docker running containers from one host to another.

Is there any way I can push my containers to repositories like we do for images ?
Currently, I am not using data volumes to store the data associated with applications running inside containers. So some data resides inside containers, which I want to persist before redesigning the setup.


How to move Docker containers between different hosts?

I have a docker image tagged as `me/my-image`, and I have a private repo on the dockerhub named `me-private`.  
When I push my `me/my-image`, I end up always hitting the public repo.

What is the exact syntax to specifically push my image to my private repo? 

How to push a docker image to a private repository

I am trying to run a private repository on aws-ecs-fargate-1.4.0 platform.

For private repository authentication, I have followed the [docs][1] and it was working well.

Somehow after updating existing service many times it goes fail to run the task and complain the error like 

    ResourceInitializationError: unable to pull secrets or registry auth: execution resource retrieval failed: unable to get registry auth from asm: service call has been retried 1 time(s): asm fetching secret from the service for &lt;secretname&gt;: RequestError: ...

I haven&#39;t change the `ecsTaskExecutionRole` and it contains all required policies to fetch secret value.

 1. AmazonECSTaskExecutionRolePolicy
 2. CloudWatchFullAccess
 3. AmazonECSTaskExecutionRolePolicy
 4. GetSecretValue
 5. GetSSMParamters



  [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/private-auth.html

Aws ecs fargate ResourceInitializationError: unable to pull secrets or registry auth

I have written a Dockerfile which looks like this

    FROM ubuntu:12.04
    
    RUN apt-get update
    RUN apt-get install -y wget

Now I&#39;m having a file called `abc.txt` in my host machine. How can I copy it to this container. Is there any step that I can add in Dockerfile which copy from Host to Container.

How to copy file from host to container using Dockerfile

The private registry was worked well based on docker 1.10.3,but I can not pull/push images after the docker updated to 1.12.0.

I had modified the /etc/sysconfig/docker as:

    OPTIONS=&#39;--selinux-enabled=true --insecure-registry=myip:5000&#39;

or
    
    OPTIONS=&#39;--selinux-enabled=true --insecure-registry myip:5000&#39;

but when I exec pull/push,I got this error:
   
    $ docker pull myip:5000/cadvisor
    Using default tag: latest
    Error response from daemon: Get https://myip:5000/v1/_ping: http: server gave HTTP response to HTTPS client

when I change back docker to 1.10.3, it still work well as below:

    $ docker pull myip:5000/cadvisor
    Using default tag: latest
    Trying to pull repository myip:5000/cadvisor ... 
    latest: Pulling from myip:5000/cadvisor
    09d0220f4043: Pull complete 
    a3ed95caeb02: Pull complete 
    151807d34af9: Pull complete 
    14cd28dce332: Pull complete     
    Digest:
    sha256:33b6475cd5b7646b3748097af1224de3eee3ba7cf5105524d95c0cf135f59b47
    Status: Downloaded newer image for myip/cadvisor:latest
Some relative information are listed below:
    
    docker version
    Client:
    Version: 1.12.0
    API version: 1.24
    Go version: go1.6.3
    Git commit: 8eab29e
    Built:

    OS/Arch: linux/amd64

    Server:
    Version: 1.12.0
    API version: 1.24
    Go version: go1.6.3
    Git commit: 8eab29e
    Built:

    OS/Arch: linux/amd64

    docker info
    Containers: 4
    Running: 1
    Paused: 0
    Stopped: 3
    Images: 241
    Server Version: 1.12.0
    Storage Driver: devicemapper
    Pool Name: docker-253:0-6809-pool
    Pool Blocksize: 65.54 kB
    Base Device Size: 107.4 GB
    Backing Filesystem: xfs
    Data file: /dev/loop0
    Metadata file: /dev/loop1
    Data Space Used: 5.459 GB
    Data Space Total: 107.4 GB
    Data Space Available: 34.74 GB
    Metadata Space Used: 9.912 MB
    Metadata Space Total: 2.147 GB
    Metadata Space Available: 2.138 GB
    Thin Pool Minimum Free Space: 10.74 GB
    Udev Sync Supported: true
    Deferred Removal Enabled: false
    Deferred Deletion Enabled: false
    Deferred Deleted Device Count: 0
    Data loop file: /var/lib/docker/devicemapper/devicemapper/data
    WARNING: Usage of loopback devices is strongly discouraged for production use. Use &#39;--storage-opt dm.thinpooldev&#39; to specify a custom block storage device.
    Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
    Library Version: 1.02.107-RHEL7 (2016-06-09)
    Logging Driver: json-file
    Cgroup Driver: cgroupfs
    Plugins:
    Volume: local
    Network: host overlay null bridge
    Swarm: inactive
    Runtimes: runc
    Default Runtime: runc
    Security Options: seccomp
    Kernel Version: 3.10.0-229.el7.x86_64
    Operating System: CentOS Linux 7 (Core)
    OSType: linux
    Architecture: x86_64
    CPUs: 24
    Total Memory: 62.39 GiB
    Name: server_3
    ID: TITS:BL4B:M5FE:CIRO:5SW6:TVIV:HW36:J7OS:WLHF:46T6:2RBA:WCNV
    Docker Root Dir: /var/lib/docker
    Debug Mode (client): false
    Debug Mode (server): true
    File Descriptors: 21
    Goroutines: 32
    System Time: 2016-08-02T10:33:06.414048675+08:00
    EventsListeners: 0
    Registry: https://index.docker.io/v1/
    WARNING: bridge-nf-call-iptables is disabled
    WARNING: bridge-nf-call-ip6tables is disabled
    Insecure Registries:
    127.0.0.0/8

    docker exec &lt;registry-container&gt; registry -version
    registry github.com/docker/distribution v2.2.1

After I restart the docker daemon in debug mode, the daemon logs when reproducing my problem are listed below:

    DEBU[0794] Calling POST /v1.24/images/create?fromImage=10.10.10.40%3A5000%2Fcadvisor&amp;tag=latest 
    DEBU[0794] hostDir: /etc/docker/certs.d/10.10.10.40:5000 
    DEBU[0794] hostDir: /etc/docker/certs.d/10.10.10.40:5000 
    DEBU[0794] Trying to pull 10.10.10.40:5000/cadvisor from https://10.10.10.40:5000 v2 
    WARN[0794] Error getting v2 registry: Get https://10.10.10.40:5000/v2/: http: server gave HTTP response to HTTPS client 
    ERRO[0794] Attempting next endpoint for pull after error: Get https://10.10.10.40:5000/v2/: http: server gave HTTP response to HTTPS client
    DEBU[0794] Trying to pull 10.10.10.40:5000/cadvisor from https://10.10.10.40:5000 v1 
    DEBU[0794] hostDir: /etc/docker/certs.d/10.10.10.40:5000
    DEBU[0794] attempting v1 ping for registry endpoint https://10.10.10.40:5000/v1/
    DEBU[0794] Fallback from error: Get https://10.10.10.40:5000/v1/_ping: http: server gave HTTP response to HTTPS client 
    ERRO[0794] Attempting next endpoint for pull after error: Get https://10.10.10.40:5000/v1/_ping: http: server gave HTTP response to HTTPS client
    ERRO[0794] Handler for POST /v1.24/images/create returned error: Get https://10.10.10.40:5000/v1/_ping: http: server gave HTTP response to HTTPS client 
    DEBU[1201] clean 2 unused exec commands

What&#39;s more, I just run a simple command to launch the private registry for test, anything else is by default:

    docker run -d -p 5000:5000 --restart=always --name registry -v &#39;pwd&#39;/data:/var/lib/registry registry:2

No proxy is configured. In summary, it is only a quiet sample environment for test.


Can not pull/push images after update docker to 1.12

Is there a way I can download a Docker image/container using, for example, Firefox and not using the built-in `docker-pull`.

I am blocked by the company firewall and proxy, and I can&#39;t get a hole through it.

My problem is that I cannot use Docker to get images, that is, Docker save/pull and other Docker supplied functions since it is blocked by a firewall.



How do I download Docker images without using the pull command?

I&#39;m trying to setup a private docker registry using the image taken from:
https://github.com/docker/docker-registry

Just by running:&lt;br&gt;
`docker run -p 5000:5000 registry`

I can pull/push from/to this repository only from localhost, but if i try to access it from another machine (using a private address on the same LAN) it fails with an error message:


    *2014/11/03 09:49:04 Error: Invalid registry endpoint https ://10.0.0.26:5000/v1/&#39;: 
    Get https:// 10.0.0.26:5000/v1/_ping: Forbidden. If this private 
    registry supports only HTTP or HTTPS with an unknown CA certificate,
    please add `--insecure-registry 10.0.0.26:5000` to the daemon&#39;s 
    arguments. In the case of HTTPS, if you have access to the registry&#39;s
    CA certificate, no need for the flag; simply place the CA certificate 
    at /etc/docker/certs.d/10.0.0.26:5000/ca.crt*


What drives me crazy is that I can access it successfully using:
`curl 10.0.0.26:5000 `
and/or `curl 10.0.0.26:5000/v1/search`

I also don&#39;t understand where and how I should pass the `--insecure-registry` flag.

How to get remote access to a private docker-registry?

I made a private registry,curl xx.xx.xx.xx:5000 is ok.
I push an image into docker private registry by doing:
`docker push xx.xx.xx.xx:5000/centos`  
it return:  
`http://xx.xx.xx.xx:5000/v1/repositories/centos/tags/latest`

the question is how to get all images from registry web or command whatever.
I cant find any information from docker registry api.
any one helps ? :)

How to search images from private 1.0 registry in docker?

We updated our private docker registry to the official Registry 2.0. This version can now delete docker images identified by a hashtag (see https://docs.docker.com/registry/spec/api/#deleting-an-image) but I still don&#39;t see a way to cleanup old images.

As our CI server is continously producing new images, I would need a method to delete all images from the private registry which are no longer identified by a named tag.

If there&#39;s no built-in way to achieve this, I think a custom script could possibly work, but I don&#39;t see a v2 API method either to list all stored hashtags of an image.. 

How can I keep my private registry clean? Any hints?


Docker Registry 2.0 - how to delete unused images?

I am new to dockers. When I am running the docker pull sonarqube I am getting the following error.

**Error response from daemon: Get https://registry-1.docker.io/v2/: dial TCP: lookup registry-1.docker.io on 192.168.65.1:53: no such host**

Can you please let me know why I am getting the error and how can I rectify this.

Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.65.1:53: no such host

I am trying to deploy a docker configuration with images on a private docker registry.

Now, every time I execute `docker login registry.example.com`, I get the following error message:

&gt; error getting credentials - err: exit status 1, out: `Cannot autolaunch D-Bus without X11 $DISPLAY`

The only solution I found for non-MacOS users was to run `export $(dbus-launch)` first, but that did not change anything.

I am running Ubuntu Server and tried with both the Ubuntu Docker package and the Docker-CE package.

How can I log in without an X11 session?

docker login fails on a server with no X11 installed

Docker 1.9 allows to pass arguments to a dockerfile. See link: https://docs.docker.com/engine/reference/builder/#arg

How can i pass the same arugments within ENTRYPOINT Instruction??  

My dockerfile has  

&gt; ARG $Version=3.1  
&gt; ENTRYPOINT /tmp/folder-$Version/sample.sh start  

I am getting an error while creating container with above dockerfile.
Please suggest what is the correct way to specify the argument within ENTRYPOINT instruction??






How to pass ARG value to ENTRYPOINT?

I&#39;m trying to push my docker image up into the public docker registry:
    
    $ docker login
    Username (binarybana): 
    WARNING: login credentials saved in /home/jknight/.dockercfg.
    Login Succeeded

    $ docker images
    REPOSITORY              TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
    binarybana/dev-fedora   latest              10c7881fbaca        24 hours ago        1.148 GB
    binarybana/fedoradev    latest              10c7881fbaca        24 hours ago        1.148 GB
    binarybana/fedora-dev   latest              10c7881fbaca        24 hours ago        1.148 GB
    &lt;none&gt;                  &lt;none&gt;              b44397dc4c99        24 hours ago        1.148 GB
    &lt;none&gt;                  &lt;none&gt;              a98c27ba4738        24 hours ago        1.141 GB
    &lt;none&gt;                  &lt;none&gt;              775c74a34add        24 hours ago        1.141 GB
    &lt;none&gt;                  &lt;none&gt;              2be2491d2354        24 hours ago        1.141 GB
    docker.io/fedora        21                  93be8052dfb8        7 days ago          241.3 MB
    
    $ docker push binarybana/dev-fedora
    
    Do you really want to push to public registry? [Y/n]: Y
    The push refers to a repository [docker.io/binarybana/dev-fedora] (len: 0)
    FATA[0001] Repository does not exist: docker.io/binarybana/dev-fedora 

    $ docker push binarybana/fedora-dev
    
    Do you really want to push to public registry? [Y/n]: Y
    The push refers to a repository [docker.io/binarybana/fedora-dev] (len: 0)
    FATA[0002] Repository does not exist: docker.io/binarybana/fedora-dev 


Yet, I&#39;ve already created the repository (viewable [here](https://registry.hub.docker.com/u/binarybana/fedora-dev/)). And I&#39;ve also tried to push to repository names that I haven&#39;t already created (the first try in the example above).

I think the (len: 0) has something to do with it, but I can&#39;t google it. Also I originally created the image from a dockerfile as:

    docker build -t binarybana/fedora-dev .

Thanks.



Docker public registry push fails: Repository does not exist

I&#39;m wondering where Docker&#39;s images are exactly stored to in my local host machine.
Can I share my Docker-Image without using the ```Docker-Hub``` or a ```Dockerfile``` but the &#39;real&#39; Docker-Image? And what is exactly happening when I &#39;push&#39; my Docker-Image to Docker-Hub?


All Docker Registry Solutions on Gang of Coders

Total of 29 Docker Registry Solutions

Difference between 'image' and 'build' within docker compose