14215ed5a1
Currently builder.Backend is implemented by daemonbuilder.Docker{} for
the daemon. This registration happens in the API/server code. However,
this is too implementation specific. Ideally we should be able to specify
that docker daemon (or any other) is implementing the Backend and abstract
the implementation details. So we should remove package daemonbuilder
dependency in build_routes.go
With this change, daemonbuilder.Docker is nothing more than the daemon.
A follow on change will remove the daemonbuilder package and move relevant
methods under daemon, so that API only knows about the backend.
Also cleanup code in api/client/build.go. docker cli always performs build
context tar download for remoteURLs and sends an empty remoteContext. So
remove relevant dead code.
Signed-off-by: Anusha Ragunathan <anusha@docker.com>
|
||
|---|---|---|
| .. | ||
| command | ||
| parser | ||
| bflag.go | ||
| bflag_test.go | ||
| builder.go | ||
| dispatchers.go | ||
| envVarTest | ||
| evaluator.go | ||
| internals.go | ||
| internals_unix.go | ||
| internals_windows.go | ||
| shell_parser.go | ||
| shell_parser_test.go | ||
| support.go | ||
| wordsTest | ||