No Description

Djordje Lukic fe1772b84a Moby backend 5 years ago
.github 35c5073cc0 First e2e tests running locally (with example backend) 5 years ago
azure 13db3437fd ACI Container ids work fine between ps, log & exec, either from single container (docker run) of multi-container compose stack 5 years ago
backend 73529cc264 Refactor example/backend 5 years ago
cli fe1772b84a Moby backend 5 years ago
client 73529cc264 Refactor example/backend 5 years ago
compose 03e418cbbb Add compose up and down 5 years ago
containers ba455916c6 Refactor on services 5 years ago
context 4e9a4185af Add `make lint` and run it on CI 5 years ago
example 73529cc264 Refactor example/backend 5 years ago
moby fe1772b84a Moby backend 5 years ago
server 24c035e822 Add comments on exported items, remove example command 5 years ago
tests 153e7c1e11 Moved sample compose files in test folder 5 years ago
util 3bb4fe163c Add `docker context create` command 5 years ago
.dockerignore cbfcd5cf64 Add dockerignore 5 years ago
.gitignore fcc7582826 Remove non-project path 5 years ago
.golangci.yml 9a2ec752b5 Add ACI compose basic e2e test 5 years ago
Dockerfile 4e9a4185af Add `make lint` and run it on CI 5 years ago
Makefile eb712ac75f Added aci e2e tests, not run in CI since requiring azure login. 5 years ago
README.md 688e7e5deb Implement quiet flag for ps command 5 years ago
builder.Makefile 4e9a4185af Add `make lint` and run it on CI 5 years ago
go.mod fe1772b84a Moby backend 5 years ago
go.sum fe1772b84a Moby backend 5 years ago
setup-dev.sh 5cbfa2778e Use github action to install protoc 5 years ago

README.md

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:

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

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.