dockerhub

I've deployed a private docker image registry on an AWS EC2 Ubuntu 14.04 instance. The registry is secured using Let's Encrypt certificate. Unfortunately, I'm getting net/http: TLS handshake timeout for docker push operations that take longer than 300s: This is the output of the time'd command: [luqo33@home-pc containers]$ time docker push <my-registry-domain:5000>/nginx The push refers to a repository [<my-registry-domain:5000>/nginx] dda5a806f0b0: Layer already exists ec35cfccb7f7: Layer already exists 94c1a232bb3f: Layer already exists 6d6b9812c8ae: Layer already exists 695da0025de6:

I have a EC2 server running Docker and I'd like to add the following to the User Data so my private Dockerhub images will be pulled/run when the server starts up, like so: #!/bin/bash sudo docker run -p 3333:3333 -d --name Hello myusername/hello But I'm unsure as to how to go about authenticating in order to gain access to the private repo myusername/hello . With Github you create and upload a deploy key, does Dockerhub offer a similar deploy key option? AJB UPDATE: Figured out an even better way that doesn't involve baking your creds into an image at all. See the following question for

Due to build time restrictions on Docker Hub, I decided to split the Dockerfile of a time-consuming automated build into 3 files. Each one of those "sub-builds" finishes within Docker Hub's time limits. I have now the following setup within the same repository: | branch | dockerfile | tag | | ------ | ------------------ | ------ | | master | /step-1.Dockerfile | step-1 | | master | /step-2.Dockerfile | step-2 | | master | /step-3.Dockerfile | step-3 | The images build on each other in the following order: step-1.Dockerfile : FROM ubuntu step-2.Dockerfile : FROM me/complex-image:step-1 step-3

I'm using Travis CI for building docker images from Dockerfiles and then pushing them to the Docker Hub on success. I've created an MD file describing the image and how to use it. I want to have the same description on the Docker Hub in the full description section. As I may update the description in the future, I want to have Travis CI automatically update the description based on the MD file in the repository with the new image. Anyone knows how to do this? Since the Docker Hub does not expose any API , the only way to send stuff to the Docker Hub remotely is with the docker push command,

I would like to always pull a specific version, rather than just the latest. A random example: https://registry.hub.docker.com/u/aespinosa/jenkins/builds_history/9511/ I am doing this because I only want to deploy versions that I have audited. Is this currently possible? Or am I forced to fork them and make my own? The way I do it is to tag each build docker build -t $NAMESPACE/$APP_NAME:$BUILD_SHA1 . docker tag $NAMESPACE/$APP_NAME:$SHA1 $DOCKER_REGISTRY/$NAMESPACE/$APP_NAME:$SHA1 docker push $DOCKER_REGISTRY/$NAMESPACE/$APP_NAME:$SHA1 and then you pull the specific tag docker pull $DOCKER

I've been trying to pull in a private (custom) MySQL image from my Docker Hub repository to the gitlab-ci.yml pipeline as a service. I have added a before_script that tries to log in to dockerhub with my username and password (CI variables). There's no output in the failed build log suggesting whether the login to Docker Hub was successful or otherwise but I'm assuming not because the pulling of my image fails with the following message (edit: or it's never even attempted because gitlab tries to get the services before it runs the before script?): repository does not exist or may require