dockerhub

I'm using automated build to create docker images for a benchmark suite. In one of the benchmarks, which is web search, I have to use a very big index file (11GB). My image is not being built, and I'm receiving this error : The build has timed out. But when I check the build log, which is very long, in the last line I can see that it has actually built successfully: Successfully built 4c84c7ec04c6 It seems that the worker responsible for creating this image, loses its connection with its master (registry node), while it is still processing and building the image. It's probably due to the fact

When I am pushing new image to repo I would like it to have two tags for example 0.2 and latest . This would allow to always pull latest image version by using latest tag and a specific version by using 0.2 tag for example. Is it possible with docker? Is there any workaround? The only solution I see is to make two separate pushes... You can create multiple tags: docker tag <id> <user>/<image>:0.2 docker tag <id> <user>/<image>:latest and push these. You need to do one push per each version like: docker tag test:latest <repo>/<user>/test:latest docker push <repo>/<user>/test:latest docker tag

I have an off-the-shelf Kubernetes cluster running on AWS, installed with the kube-up script. I would like to run some containers that are in a private Docker Hub repository. But I keep getting a "not found" error: > kubectl get pod NAME READY STATUS RESTARTS AGE maestro-kubetest-d37hr 0/1 Error: image csats/maestro:latest not found 0 22m I've created a secret containing a .dockercfg file. I've confirmed it works by running the script posted here : > kubectl get secrets docker-hub-csatsinternal -o yaml | grep dockercfg: | cut -f 2 -d : | base64 -D > ~/.dockercfg > docker pull csats/maestro

Given a tag `latest`, we want to find out another tag with the same image ID on Docker Hub. Here is how to find out all tags for a repo with the Docker Hub API v2: TOKEN=$(curl -s -H "Content-Type: application/json" -X POST -d '{"username": "'${UNAME}'", "password": "'${UPASS}'"}' https://hub.docker.com/v2/users/login/ | jq -r .token) curl -s -H "Authorization: JWT ${TOKEN}" https://hub.docker.com/v2/repositories/fluent/fluentd/tags/?page_size=100 | jq (See gist.github.com/kizbitz ) Unfortunately, it doesn't contain the image ID but always a `null` value for this key: $ curl -s -H

I am trying to develop a V2 plugin. I am able to to use the 'docker plugin create' and 'docker plugin enable' commands with my plugin configuration. However the 'docker plugin push' command fails with the following error [root@localhost plugin]# docker plugin push adityadani/pxd-plugin Error response from daemon: errors: denied: requested access to the resource is denied unauthorized: authentication required Here is my docker version Client: Version: 1.13.0-rc4 API version: 1.25 Go version: go1.7.3 Git commit: 88862e7 Built: Sat Dec 17 01:34:17 2016 OS/Arch: linux/amd64 Server: Version: 1.13.0

Right now I have multiple components of my application in the same folder linked together with a docker-compose This works really well in development, but when I want to push to production it's kind of fuzzy. If I keep this structure I cannot use only dockerhub to host my images because the docker-compose which links them will be missing. If I use git to pull down my docker-compose, what would be the point of dockerhub? Why not just clone my whole repo and run docker-compose up each time? I could alternatively store each component separately in separate github repos, pushing them up to

I've searched around and can't find a real answer to this. If I create a docker git repo and set up autobuild to my dockerhub account, it will build with a single tag (i.e. latest, or 1.0 or foo) but I can't find any way to add a tag afterwards as you can via command line with a locally built docker image. Pulling down the image and then retagging doesn't work as the autobuild repos are read-only outside of the webui. Being able to manually add a tag to an existing build would satisfy me for now, but being able to script in something to grab the correct tag version would be the best solution.