#docker-dev

could anyone confirm (I just read gh#7067) that you won't be supporting private repositories on non-root paths any time soon?

Docker - Some registry URLs don't work correctly in Docker image names.: https://github.com/docker/docker/issues/7067

cpuguy83 jpetazzo: I'm also thinking we could affect the machine's workloads if we're doing anything too quickly.

That's one of the reasons why I'm grateful for the new default for pull to only pull the latest image.

erikh: tell me about these dockerfile experiments

tibor erikh: what is the actual problem being solved by START ?

One of the things that makes Dockerfile so awesome is it’s simplicity. It’s incredibly easy to look at it and know exactly what’s happening.

cpuguy83: agree

Certainly some optimizations can/should be made

cpuguy83: hey, i'm not saying START is the way to go

cpuguy83: i actually need to show a PoC without introspection

Also one of the reasons I hate Chef. It’s ridiculous to figure out what is coming from where, when your stuff is going to run, or even just write a cookbook.

cpuguy83: just with an api to commit --change, and better quoting on dockerfile

tibor: is there an issue/pr with this info?

chance: not yet, just gists, and docker-dev conversations

we're still experimenting, but will get a proposal out soon hopefully

The builder should definitely be using public API’s.

cpuguy83: yes

cpuguy83: i'll think about this more this weekend, but rest assured, the goal is to make it better, not worse :)

cpuguy83: that's why we're coming up with experiments and trying to attack them in every way we can

so what exactly is 'START' supposed to accomplish?

chance: sorry

chance: so basically

chance: the idea was to have an api from within a container

chance: a daemon api*

interesting

that way the container can build itself

step by step

and produce an image

so that's using introspection

and then you could use any language

bash or anything

to build your image

and you could have all dockerfile instructions