Show HN: Containerfactory.io – GitHub repo to docker image
containerfactory.io
Show HN: Containerfactory.io – GitHub repo to docker image
1–10 of 15 posts
Re: Show HN: Containerfactory.io – GitHub repo to docker image
#2We built this @ Techcrunch disrupt NYC last weekend, spent a few days cleaning it up and decided to opensource & share it with everyone. All feedback is welcome.
Re: Show HN: Containerfactory.io – GitHub repo to docker image
#3How is this different from the build service provided by
registry.hub.docker.com?
Re: Show HN: Containerfactory.io – GitHub repo to docker image
#4How is this different from the build service provided by registry.hub.docker.com?
From what I understand, this tools build a container and push it to the registry for every change, where as when you are using the registry alone, you have to push the images manually?
Am I right?
Re: Show HN: Containerfactory.io – GitHub repo to docker image
#5How is this different from the build service provided by registry.hub.docker.com?
From what I understand, this tools build a container and push it to the registry for every change, where as when you are using the registry alone, you have to push the images manually? Am I right?
The Docker Hub does also have a mode called "Automated Builds" which will pull down the repository, build an image based on the Dockerfile and push it. However, you do have to pick one or the other (you cannot push your own image to a repository configured as an Automated Build).
Re: Show HN: Containerfactory.io – GitHub repo to docker image
#6How is this different from the build service provided by registry.hub.docker.com?
From what I understand, this tools build a container and push it to the registry for every change, where as when you are using the registry alone, you have to push the images manually? Am I right?
This is actually a open source project you can host your self, so have your own version of dockerhub auto build plus we added a way to build repos without dockerfile with assigning default dockerfiles based on language and you can push to any registry you want. Be it dockerhub or quay or your own registry.
Re: Show HN: Containerfactory.io – GitHub repo to docker image
#7Earlier quoted context omitted.
From what I understand, this tools build a container and push it to the registry for every change, where as when you are using the registry alone, you have to push the images manually? Am I right?
The Docker Hub does also have a mode called "Automated Builds" which will pull down the repository, build an image based on the Dockerfile and push it. However, you do have to pick one or the other (you cannot push your own image to a repository configured as an Automated Build).
But you can manually trigger a build when automated builds are enabled, for rare cases when the automated trigger didn't do what you wanted. Works really well in practice.
Re: Show HN: Containerfactory.io – GitHub repo to docker image
#8How is this different from the build service provided by registry.hub.docker.com?
Also does the besides the stuff i mention in the other comment of, pushing to any registry, you can self host and modify, it also builds instantly and streams the logs.
Re: Show HN: Containerfactory.io – GitHub repo to docker image
#9This is huge.
Re: Show HN: Containerfactory.io – GitHub repo to docker image
#10Full Disclosure: I work on Quay.io at CoreOS.
I'm curious how security is handled with containerfactory.io.
We just gave a very detailed presentation on our build system at CoreOS Fest which will be available in video form soon. As a part of this talk, we mentioned all the security implications of building other people's container images.