Full 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.
Show HN: Containerfactory.io – GitHub repo to docker image
11–15 of 15 posts
Re: Show HN: Containerfactory.io – GitHub repo to docker image
#12Full 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.
Well the code to every part of this is open source so you can check and improve. The hosting part is on 10 digital ocean boxes all with one container on it so the build process is more isolated and anything goes wrong we kill and spawn a fresh box.
Re: Show HN: Containerfactory.io – GitHub repo to docker image
#13Full 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.
Well the code to every part of this is open source so you can check and improve. The hosting part is on 10 digital ocean boxes all with one container on it so the build process is more isolated and anything goes wrong we kill and spawn a fresh box.
Re: Show HN: Containerfactory.io – GitHub repo to docker image
#14Earlier quoted context omitted.
Well the code to every part of this is open source so you can check and improve. The hosting part is on 10 digital ocean boxes all with one container on it so the build process is more isolated and anything goes wrong we kill and spawn a fresh box.
Docker executes builds as root which provides a build the opportunity to escape the container and become root on the host machine. In containerfactory.io's current hosted setup, there are no guarantees that the machine an image is being built on hasn't already been compromised by a previous build. Quay.io has traditionally worked around this problem by patching user namespaces into docker, but they come with their ow…
We build containers from ephemeral t1.micros that only survive long enough to build the single container. I think that's secure enough for most orgs needs.
Re: Show HN: Containerfactory.io – GitHub repo to docker image
#15Earlier 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?
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.
> 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
And applied to YC with it. Unfortunately they weren't accepted. I think it's a great concept.
If you'd like to chat more, my contact info is in my profile.