podman/vendor/github.com/fsouza/go-dockerclient
Miloslav Trmač d3f59bedb3 Update c/image to v4.0.1 and buildah to 1.11.3
This requires updating all import paths throughout, and a matching
buildah update to interoperate.

I can't figure out the reason for go.mod tracking
	github.com/containers/image v3.0.2+incompatible // indirect
((go mod graph) lists it as a direct dependency of libpod, but
(go list -json -m all) lists it as an indirect dependency),
but at least looking at the vendor subdirectory, it doesn't seem
to be actually used in the built binaries.

Signed-off-by: Miloslav Trmač <mitr@redhat.com>
2019-10-04 20:18:23 +02:00
..
internal migrate to go-modules 2019-06-24 13:20:59 +02:00
.gitignore migrate to go-modules 2019-06-24 13:20:59 +02:00
.travis.yml Update c/image to v4.0.1 and buildah to 1.11.3 2019-10-04 20:18:23 +02:00
AUTHORS Update c/image to v4.0.1 and buildah to 1.11.3 2019-10-04 20:18:23 +02:00
DOCKER-LICENSE Use buildah commit and bud in podman 2018-04-27 20:51:07 +00:00
LICENSE migrate to go-modules 2019-06-24 13:20:59 +02:00
Makefile Update c/image to v4.0.1 and buildah to 1.11.3 2019-10-04 20:18:23 +02:00
README.md Update c/image to v4.0.1 and buildah to 1.11.3 2019-10-04 20:18:23 +02:00
appveyor.yml Update c/image to v4.0.1 and buildah to 1.11.3 2019-10-04 20:18:23 +02:00
auth.go Update c/image to v4.0.1 and buildah to 1.11.3 2019-10-04 20:18:23 +02:00
change.go Use buildah commit and bud in podman 2018-04-27 20:51:07 +00:00
client.go Update c/image to v4.0.1 and buildah to 1.11.3 2019-10-04 20:18:23 +02:00
client_unix.go migrate to go-modules 2019-06-24 13:20:59 +02:00
client_windows.go migrate to go-modules 2019-06-24 13:20:59 +02:00
container.go Update c/image to v4.0.1 and buildah to 1.11.3 2019-10-04 20:18:23 +02:00
distribution.go Use buildah commit and bud in podman 2018-04-27 20:51:07 +00:00
env.go vendor: update everything 2019-01-11 13:38:11 +01:00
event.go migrate to go-modules 2019-06-24 13:20:59 +02:00
exec.go migrate to go-modules 2019-06-24 13:20:59 +02:00
go.mod Update c/image to v4.0.1 and buildah to 1.11.3 2019-10-04 20:18:23 +02:00
go.sum Update c/image to v4.0.1 and buildah to 1.11.3 2019-10-04 20:18:23 +02:00
image.go Update c/image to v4.0.1 and buildah to 1.11.3 2019-10-04 20:18:23 +02:00
misc.go migrate to go-modules 2019-06-24 13:20:59 +02:00
network.go Update c/image to v4.0.1 and buildah to 1.11.3 2019-10-04 20:18:23 +02:00
plugin.go migrate to go-modules 2019-06-24 13:20:59 +02:00
registry_auth.go migrate to go-modules 2019-06-24 13:20:59 +02:00
signal.go Use buildah commit and bud in podman 2018-04-27 20:51:07 +00:00
swarm.go Use buildah commit and bud in podman 2018-04-27 20:51:07 +00:00
swarm_configs.go Use buildah commit and bud in podman 2018-04-27 20:51:07 +00:00
swarm_node.go Use buildah commit and bud in podman 2018-04-27 20:51:07 +00:00
swarm_secrets.go Use buildah commit and bud in podman 2018-04-27 20:51:07 +00:00
swarm_service.go migrate to go-modules 2019-06-24 13:20:59 +02:00
swarm_task.go Use buildah commit and bud in podman 2018-04-27 20:51:07 +00:00
system.go migrate to go-modules 2019-06-24 13:20:59 +02:00
tar.go vendor: update everything 2019-01-11 13:38:11 +01:00
tls.go migrate to go-modules 2019-06-24 13:20:59 +02:00
volume.go vendor: update everything 2019-01-11 13:38:11 +01:00

README.md

go-dockerclient

Travis Build Status AppVeyor Build status GoDoc

This package presents a client for the Docker remote API. It also provides support for the extensions in the Swarm API.

This package also provides support for docker's network API, which is a simple passthrough to the libnetwork remote API.

For more details, check the remote API documentation.

Difference between go-dockerclient and the official SDK

Link for the official SDK: https://docs.docker.com/develop/sdk/

go-dockerclient was created before Docker had an official Go SDK and is still maintained and relatively active because it's still used out there. New features in the Docker API do not get automatically implemented here: it's based on demand, if someone wants it, they can file an issue or a PR and the feature may get implemented/merged.

For new projects, using the official SDK is probably more appropriate as go-dockerclient lags behind the official SDK.

When using the official SDK, keep in mind that because of how the its dependencies are organized, you may need some extra steps in order to be able to import it in your projects (see #784 and moby/moby#28269).

Example

package main

import (
	"fmt"

	docker "github.com/fsouza/go-dockerclient"
)

func main() {
	client, err := docker.NewClientFromEnv()
	if err != nil {
		panic(err)
	}
	imgs, err := client.ListImages(docker.ListImagesOptions{All: false})
	if err != nil {
		panic(err)
	}
	for _, img := range imgs {
		fmt.Println("ID: ", img.ID)
		fmt.Println("RepoTags: ", img.RepoTags)
		fmt.Println("Created: ", img.Created)
		fmt.Println("Size: ", img.Size)
		fmt.Println("VirtualSize: ", img.VirtualSize)
		fmt.Println("ParentId: ", img.ParentID)
	}
}

Using with TLS

In order to instantiate the client for a TLS-enabled daemon, you should use NewTLSClient, passing the endpoint and path for key and certificates as parameters.

package main

import (
	"fmt"

	docker "github.com/fsouza/go-dockerclient"
)

func main() {
	const endpoint = "tcp://[ip]:[port]"
	path := os.Getenv("DOCKER_CERT_PATH")
	ca := fmt.Sprintf("%s/ca.pem", path)
	cert := fmt.Sprintf("%s/cert.pem", path)
	key := fmt.Sprintf("%s/key.pem", path)
	client, _ := docker.NewTLSClient(endpoint, cert, key, ca)
	// use client
}

If using docker-machine, or another application that exports environment variables DOCKER_HOST, DOCKER_TLS_VERIFY, DOCKER_CERT_PATH, DOCKER_API_VERSION, you can use NewClientFromEnv.

package main

import (
	"fmt"

	docker "github.com/fsouza/go-dockerclient"
)

func main() {
	client, _ := docker.NewClientFromEnv()
	// use client
}

See the documentation for more details.

Developing

All development commands can be seen in the Makefile.

Commited code must pass:

Running make test will check all of these. You can reformat the code with make fmt.

Modules

go-dockerclient supports Go modules.

If you're using dep, you can check the releases page for the latest release fully compatible with dep.

With other vendoring tools, users might need to specify go-dockerclient's dependencies manually.

Using with Docker 1.9 and Go 1.4

There's a tag for using go-dockerclient with Docker 1.9 (which requires compiling go-dockerclient with Go 1.4), the tag name is docker-1.9/go-1.4.

The instructions below can be used to get a version of go-dockerclient that compiles with Go 1.4:

% git clone -b docker-1.9/go-1.4 https://github.com/fsouza/go-dockerclient.git $GOPATH/src/github.com/fsouza/go-dockerclient
% git clone -b v1.9.1 https://github.com/docker/docker.git $GOPATH/src/github.com/docker/docker
% go get github.com/fsouza/go-dockerclient