dockerhub

Unable to run docker image created from ISO

喜夏-厌秋 提交于 2019-12-07 19:03:28
问题 Here i am trying to create docker image from ubuntu 14.04 ISO file, knowing ubuntu 14.04 is already available in docker hub. Because later i have to create docker images for Suse10 and Suse11[sp1 64bit] which is not available in docker hub. I was able to create docker image from ubuntu 14.04 ISO with below commands # mkdir rootfs # mount -o loop /path/to/iso rootfs # tar -C rootfs -c . | docker import - newubuntu With above image gets successfully created , i can do docker images it gets

How do I make a Docker hub use the same image for “latest” and “vX.Y”?

核能气质少年 提交于 2019-12-07 13:31:00
问题 Docker Hub builds a Syncthing image for me from this source repo. I tagged the latest commit v0.13.5, but Docker built it twice: once for latest and once for v0.13.5. Why? Shouldn't it be able to figure out the source is the same? Am I just doing something dumb in my Dockerfile, breaking caching? Is there some way I need to hint to Docker Hub that this should really be two images with the same checksum but different tags? I'm thinking of the two Docker image tags latest and v0.13.5 like two

Creating a Docker Image for a Github Project

◇◆丶佛笑我妖孽 提交于 2019-12-07 09:11:44
问题 I have a GitHub project, (that I am working with (I didn't create it)), called OpenRefine, which I would like to encapsulate in a Docker image, such that other people can then pull that Docker image from the "Docker Hub" and have OpenRefine installed on their fundamental interactive Docker entity, viz. Image. I want to then upload it to a repository that I can share with others. It would be good if it had a name and not a crazy hash value. Is it that I just create a "docker file" a text files

Unable to run docker image created from ISO

﹥>﹥吖頭↗ 提交于 2019-12-06 06:09:41
Here i am trying to create docker image from ubuntu 14.04 ISO file, knowing ubuntu 14.04 is already available in docker hub. Because later i have to create docker images for Suse10 and Suse11[sp1 64bit] which is not available in docker hub. I was able to create docker image from ubuntu 14.04 ISO with below commands # mkdir rootfs # mount -o loop /path/to/iso rootfs # tar -C rootfs -c . | docker import - newubuntu With above image gets successfully created , i can do docker images it gets listed root@ubuntu:~# docker images REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE newubuntu latest

How do I make a Docker hub use the same image for “latest” and “vX.Y”?

巧了我就是萌 提交于 2019-12-05 22:43:00
Docker Hub builds a Syncthing image for me from this source repo . I tagged the latest commit v0.13.5, but Docker built it twice: once for latest and once for v0.13.5 . Why? Shouldn't it be able to figure out the source is the same? Am I just doing something dumb in my Dockerfile , breaking caching? Is there some way I need to hint to Docker Hub that this should really be two images with the same checksum but different tags? I'm thinking of the two Docker image tags latest and v0.13.5 like two git tags both pointing to the same commit. Shouldn't Docker Hub work that way too? If someone tries

Creating a Docker Image for a Github Project

倖福魔咒の 提交于 2019-12-05 16:33:19
I have a GitHub project , (that I am working with (I didn't create it)), called OpenRefine, which I would like to encapsulate in a Docker image, such that other people can then pull that Docker image from the "Docker Hub" and have OpenRefine installed on their fundamental interactive Docker entity, viz. Image. I want to then upload it to a repository that I can share with others. It would be good if it had a name and not a crazy hash value. Is it that I just create a "docker file" a text files with a git clone command? but then how to upload that to a repository such as the docker hub? I just

Google Cloud Kubernetes accessing private Docker Hub hosted images

[亡魂溺海] 提交于 2019-12-05 11:58:19
Is it possible, to pull private images from Docker Hub to a Google Cloud Kubernetes cluster? Is this recommended, or do I need to push my private images also to Google Cloud? I read the documentation, but I found nothing that could explain me this clearly. It seems that it is possible, but I don´t know if it's recommended. There is no restriction to use any registry you want. If you just use the image name, (e.g., image: nginx) in pod specification, the image will be pulled from public docker hub registry with tag assumed as :latest As mentioned in the Kubernetes documentation : The image

Docker automated build shows empty Dockerfile

余生长醉 提交于 2019-12-05 09:57:16
I have created a Dockerfile here and set up automated build for it on the docker hub, but nothing seems to happen. The build just shows "pending" and the Dockerfile on docker hub is empty. What am I doing wrong? The Dockerfile on the hub gets updated after the build runs. Also, the pending for the build means it just hasn't run yet. Sometimes it takes a while. Do you have your github account Linked in the Settings section of the Docker repository? You can reach the status page to see if anything is broken here: https://status.docker.com/ . By the way, I have several projects on Docker hub, I

Docker: How do I pull a specific build-id?

吃可爱长大的小学妹 提交于 2019-12-04 16:56:32
问题 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? 回答1: 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

Chain automated builds in the same Docker Hub repository

谁说我不能喝 提交于 2019-12-04 13:28:01
问题 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