mirror of
https://github.com/moby/moby.git
synced 2022-11-09 12:21:53 -05:00
Merge pull request #33129 from vieux/builder-report-2017-05-07
Add dev report for may 8th
This commit is contained in:
commit
4836b0ab85
3 changed files with 92 additions and 1 deletions
|
@ -22,7 +22,7 @@ We are almost done, it should be merged soon.
|
|||
|
||||
Slack works great for synchronous communication, but we need to place for async discussion. A mailing list is currently being setup.
|
||||
|
||||
#### Find a good and non-confusing home for the remaining monolith
|
||||
### Find a good and non-confusing home for the remaining monolith
|
||||
|
||||
Lots of discussion and progress made on this topic, see [here](https://github.com/moby/moby/issues/32871). The work will start this week.
|
||||
|
||||
|
|
34
reports/2017-05-08.md
Normal file
34
reports/2017-05-08.md
Normal file
|
@ -0,0 +1,34 @@
|
|||
# Development Report for May 08, 2017
|
||||
|
||||
## Daily Meeting
|
||||
|
||||
A daily meeting is hosted on [slack](https://dockercommunity.slack.com) every business day at 9am PST on the channel `#moby-project`.
|
||||
During this meeting, we are talking about the [tasks](https://github.com/moby/moby/issues/32867) needed to be done for splitting moby and docker.
|
||||
|
||||
## Topics discussed last week
|
||||
|
||||
### The CLI split
|
||||
|
||||
The Docker CLI was succesfully moved to [https://github.com/docker/cli](https://github.com/docker/cli) last week thanks to @tiborvass
|
||||
The Docker CLI is now compiled from the [Dockerfile](https://github.com/moby/moby/blob/a762ceace4e8c1c7ce4fb582789af9d8074be3e1/Dockerfile#L248)
|
||||
|
||||
### Mailing list
|
||||
|
||||
Discourse is available at [forums.mobyproject.org](https://forums.mobyproject.org/) thanks to @thaJeztah. mailing-list mode is enabled, so once you register there, you will received every new threads / messages via email. So far, 3 categories were created: Architecture, Meta & Support. The last step missing is to setup an email address to be able to start a new thread via email.
|
||||
|
||||
### Find a place for `/pkg`
|
||||
|
||||
Lots of discussion and progress made on this [topic](https://github.com/moby/moby/issues/32989) thanks to @dnephin. [Here is the list](https://gist.github.com/dnephin/35dc10f6b6b7017f058a71908b301d38) proposed to split/reorganize the pkgs.
|
||||
|
||||
### Find a good and non-confusing home for the remaining monolith
|
||||
|
||||
@cpuguy83 is leading the effort [here](https://github.com/moby/moby/pull/33022). It's still WIP but the way we are experimenting with is to reorganise directories within the moby/moby.
|
||||
|
||||
## Componentization
|
||||
|
||||
So far only work on the builder, by @tonistiigi, happened regarding the componentization effort.
|
||||
|
||||
### builder
|
||||
|
||||
The builder dev report can be found [here](builder/2017-05-07.md)
|
||||
|
57
reports/builder/2017-05-08.md
Normal file
57
reports/builder/2017-05-08.md
Normal file
|
@ -0,0 +1,57 @@
|
|||
# Development Report for May 08, 2017
|
||||
|
||||
|
||||
### Quality: Dependency interface switch
|
||||
|
||||
Proposal for [switching the dependency interface](https://github.com/moby/moby/issues/32904) for current builder package. That should fix the current problems with data leakage and conflicts caused by daemon state cleanup scripts.
|
||||
|
||||
Merged as part of this effort:
|
||||
|
||||
- [Move dispatch state to a new struct](https://github.com/moby/moby/pull/32952)
|
||||
- [Cleanup unnecessary mutate then revert of b.runConfig](https://github.com/moby/moby/pull/32773)
|
||||
|
||||
In review:
|
||||
- [Refactor builder probe cache and container backend](https://github.com/moby/moby/pull/33061)
|
||||
- [Expose GetImage interface for builder](https://github.com/moby/moby/pull/33054)
|
||||
|
||||
### Merged: docker build --iidfile
|
||||
|
||||
[`docker build --iidfile` to capture the ID of the build result](https://github.com/moby/moby/pull/32406). New option can be used by the CLI applications to get back the image ID of build result. API users can use the `Aux` messages in progress stream to also get the IDs for intermediate build stages, for example to share them for build cache.
|
||||
|
||||
### New feature: Long running session
|
||||
|
||||
PR for [adding long-running session between daemon and cli](https://github.com/moby/moby/pull/32677) that enables advanced features like incremental context send, build credentials from the client, ssh forwarding etc.
|
||||
|
||||
@simonferquel proposed a [grpc-only version of that interface](https://github.com/moby/moby/pull/33047) that should simplify the setup needed for describing new features for the session. Looking for design reviews.
|
||||
|
||||
The feature also needs to be reworked after CLI split.
|
||||
|
||||
### buildkit
|
||||
|
||||
Not much progress [apart from some design discussion](https://github.com/moby/moby/issues/32925). Next step would be to open up a repo.
|
||||
|
||||
### Proposals for new Dockerfile features that need design feedback:
|
||||
|
||||
[Add IMPORT/EXPORT commands to Dockerfile](https://github.com/moby/moby/issues/32100)
|
||||
|
||||
[Add `DOCKEROS/DOCKERARCH` default ARG to Dockerfile](https://github.com/moby/moby/issues/32487)
|
||||
|
||||
[Add support for `RUN --mount`](https://github.com/moby/moby/issues/32507)
|
||||
|
||||
[DAG image builder](https://github.com/moby/moby/issues/32550)
|
||||
|
||||
[Option to export the hash of the build context](https://github.com/moby/moby/issues/32963) (new)
|
||||
|
||||
[Allow --cache-from=*](https://github.com/moby/moby/issues/33002#issuecomment-299041162) (new)
|
||||
|
||||
If you are interested in implementing any of them, leave a comment on the specific issues.
|
||||
|
||||
### Other new builder features currently in code-review:
|
||||
|
||||
[Allow builds from any git remote ref](https://github.com/moby/moby/pull/32502)
|
||||
|
||||
[Fix a case where using FROM scratch as NAME would fail](https://github.com/moby/moby/pull/32997)
|
||||
|
||||
### Backlog:
|
||||
|
||||
[Build secrets](https://github.com/moby/moby/pull/30637) will be brought up again in next maintainer's meeting to evaluate how to move on with this, if any other proposals have changed the objective and if we should wait for swarm secrets to be available first.
|
Loading…
Reference in a new issue