Guillaume Tardif c2a702c963 Ensure the docker context inspect default is not executed in a different context, that might make it fail.
Following discussion with @simonferquel, this will strengthen the shell out to get default context, in cases the user has damaged his config file current context or there are issues with context synchronisation between windows host & wsl2.
2020-06-13 10:50:56 +02:00
2020-06-02 09:41:57 +02:00
2020-05-14 13:29:11 +02:00
2020-05-13 18:37:41 +02:00
2020-05-29 11:29:28 +02:00
2020-04-24 14:04:27 +02:00
2020-06-02 11:58:29 +02:00
2020-06-08 09:43:19 +02:00

Docker API

Actions Status

Dev Setup

The recommended way is to use the main Makefile that runs everything inside a container.

If you don't have or want to use Docker for building you need to make sure you have all the needed tools installed locally:

  • go 1.14
  • protoc
  • go get github.com/golang/protobuf/protoc-gen-go@v1.4.1
  • go get golang.org/x/tools/cmd/goimports
  • go get github.com/golangci/golangci-lint/cmd/golangci-lint@v1.26.0

And then you can call the same make targets but you need to pass it the builder.Makefile (make -f builder.Makefile).

The new CLI delegates to the classic docker for default contexts ; delegation is done to docker-classic.

  • make classic-link will create a docker-classic link in /usr/local/bin if you don't already have it from Docker Desktop

Building the project

$ make

If you make changes to the .proto files, make sure to make protos to generate go code.

Tests

To run unit tests:

make test

If you need to update a golden file simply do go test ./... -test.update-golden.

Description
Define and run multi-container applications with Docker
Readme Apache-2.0 51 MiB
Languages
Go 97.1%
Dockerfile 2%
Makefile 0.5%
HCL 0.3%