kjuulh/dagger
Archived
1
0
Fork 0
Code Issues 1 Pull Requests 1 Projects Releases Wiki Activity

automatically start/upgrade buildkitd

Browse Source 
- Automatically start a buildkit daemon if no BUILDKIT_HOST is
  provided (and if not already started)
- Customization of BUILDKIT_HOST is still possible, just like before
- Automatically upgrade the managed daemon to the version used by dagger
  if necessary
- Add CI test to make sure the managed buildkit and the vendored
  buildkit versions match

Signed-off-by: Andrea Luzzardi <aluzzardi@gmail.com>
This commit is contained in:
Andrea Luzzardi
2021-03-02 16:14:53 -08:00
parent 50e8b8c07d
commit 14ff14ea4f
5 changed files with 184 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@@ -74,15 +74,7 @@ $ make
$ cp ./cmd/dagger/dagger /usr/local/bin
```
3. Run [buildkitd](https://github.com/moby/buildkit) on your local machine. The simplest way to do this is using [Docker](https://docker.com): `docker run -d --name buildkitd --privileged moby/buildkit:latest`
On a machine with Docker installed, run:
```
$ docker run -d --name buildkitd --privileged moby/buildkit:latest
```
4. Compute a test configuration
3. Compute a test configuration
Currently `dagger` can only do one thing: compute a configuration with optional inputs, and print the result.