Awesome

docker

The Docker Engine

Maintainers

• The Core Planners: chef-core-planners@chef.io

Type of Package

Binary package

Use as Dependency

Binary packages can be set as runtime or build time dependencies. See Defining your dependencies for more information.

The docker plan only provides users access to the standalone docker binaries. It is provided with the intention that any user's who need to run docker will write their own plan that depends on this package and provide their own runtime management.

Docker is a complex piece of software with multiple ways in which it can be configured to run. As such we provide this package to enable you to wrap and automate your preferred deployment style.

To add core/docker as a depdendency, you can add one of the following to your plan file.

Buildtime Dependency

pkg_build_deps=(core/docker)

Runtime Dependency

pkg_deps=(core/docker)

Use as Tool

Installation

To install this plan, you should run the following commands to first install, and then link the binaries this plan creates.

hab pkg install core/docker --binlink

will add the following binaries to the PATH:

• /bin/containerd-shim
• /bin/docker-init
• /bin/dockerd
• /bin/docker-proxy
• /bin/ctr
• /bin/docker
• /bin/containerd
• /bin/runc

For example:

$ hab pkg install core/docker --binlink
» Installing core/docker
☁ Determining latest version of core/docker in the 'stable' channel
→ Found newer installed version (core/docker/19.03.8/20200612100826) than remote version (core/docker/19.03.8/20200505084334)
→ Using core/docker/19.03.8/20200612100826
★ Install of core/docker/19.03.8/20200612100826 complete with 0 new packages installed.
» Binlinking containerd-shim from core/docker/19.03.8/20200612100826 into /bin
★ Binlinked containerd-shim from core/docker/19.03.8/20200612100826 to /bin/containerd-shim
» Binlinking docker-init from core/docker/19.03.8/20200612100826 into /bin
★ Binlinked docker-init from core/docker/19.03.8/20200612100826 to /bin/docker-init
» Binlinking dockerd from core/docker/19.03.8/20200612100826 into /bin
★ Binlinked dockerd from core/docker/19.03.8/20200612100826 to /bin/dockerd
» Binlinking docker-proxy from core/docker/19.03.8/20200612100826 into /bin
★ Binlinked docker-proxy from core/docker/19.03.8/20200612100826 to /bin/docker-proxy
» Binlinking ctr from core/docker/19.03.8/20200612100826 into /bin
★ Binlinked ctr from core/docker/19.03.8/20200612100826 to /bin/ctr
» Binlinking docker from core/docker/19.03.8/20200612100826 into /bin
★ Binlinked docker from core/docker/19.03.8/20200612100826 to /bin/docker
» Binlinking containerd from core/docker/19.03.8/20200612100826 into /bin
★ Binlinked containerd from core/docker/19.03.8/20200612100826 to /bin/containerd
» Binlinking runc from core/docker/19.03.8/20200612100826 into /bin
★ Binlinked runc from core/docker/19.03.8/20200612100826 to /bin/runc

Using an example binary

You can now use the binary as normal. For example:

/bin/docker --help or docker --help

$ docker --help

Usage:  docker [OPTIONS] COMMAND

A self-sufficient runtime for containers

Options:
      --config string      Location of client config
                           files (default "/root/.docker")
  -c, --context string     Name of the context to use to
                           connect to the daemon
...
...