1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
|
OCI Image Builder
==========================
[](https://goreportcard.com/report/github.com/openshift/imagebuilder)
[](https://godoc.org/github.com/openshift/imagebuilder)
[](https://travis-ci.org/openshift/imagebuilder)
[](http://webchat.freenode.net/?channels=%23openshift-dev)
Please test your images (and add to our conformance suite)!
This library supports using the Dockerfile syntax to build OCI & Docker
compatible images, without invoking a container build command such as `buildah bud` or `docker build`. It is intended to give
clients more control over how they build container images, including:
* Instead of building one layer per line, run all instructions in the
same container
* Set HostConfig settings like network and memory controls that
are not available when running container builds
* Mount external files into the build that are not persisted as part of
the final image (i.e. "secrets")
* If there are no RUN commands in the Dockerfile, the container is created
and committed, but never started.
The final image should be 99.9% compatible with regular container builds,
but bugs are always possible.
Future goals include:
* Output OCI compatible images
* Support other container execution engines, like runc or rkt
* Better conformance testing
* Windows support
## Install and Run
To download and install the library and the binary, set up a Golang build environment and with `GOPATH` set run:
```
$ go get -u github.com/openshift/imagebuilder/cmd/imagebuilder
```
The included command line takes one argument, a path to a directory containing a Dockerfile. The `-t` option
can be used to specify an image to tag as:
```
$ imagebuilder [-t TAG] DIRECTORY
```
To mount a file into the image for build that will not be present in the final output image, run:
```
$ imagebuilder --mount ~/secrets/private.key:/etc/keys/private.key path/to/my/code testimage
```
Any processes in the Dockerfile will have access to `/etc/keys/private.key`, but that file will not be part of the committed image.
You can also customize which Dockerfile is run, or run multiple Dockerfiles in sequence (the FROM is ignored on
later files):
```
$ imagebuilder -f Dockerfile:Dockerfile.extra .
```
will build the current directory and combine the first Dockerfile with the second. The FROM in the second image
is ignored.
## Code Example
```go
f, err := os.Open("path/to/Dockerfile")
if err != nil {
return err
}
defer f.Close()
e := builder.NewClientExecutor(o.Client)
e.Out, e.ErrOut = os.Stdout, os.Stderr
e.AllowPull = true
e.Directory = "context/directory"
e.Tag = "name/of-image:and-tag"
e.AuthFn = nil // ... pass a function to retrieve authorization info
e.LogFn = func(format string, args ...interface{}) {
fmt.Fprintf(e.ErrOut, "--> %s\n", fmt.Sprintf(format, args...))
}
buildErr := e.Build(f, map[string]string{"arg1":"value1"})
if err := e.Cleanup(); err != nil {
fmt.Fprintf(e.ErrOut, "error: Unable to clean up build: %v\n", err)
}
return buildErr
```
Example of usage from OpenShift's experimental `dockerbuild` [command with mount secrets](https://github.com/openshift/origin/blob/26c9e032ff42f613fe10649cd7c5fa1b4c33501b/pkg/cmd/cli/cmd/dockerbuild/dockerbuild.go)
## Run conformance tests (very slow):
```
go test ./dockerclient/conformance_test.go -tags conformance
```
|
