From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] docker-containerd: bump to version 1.0.1
Date: Sat, 31 Mar 2018 20:51:38 +0200 [thread overview]
Message-ID: <20180331205138.6568882d@windsurf> (raw)
In-Reply-To: <20180311221741.11346-1-charles.hardin@storagecraft.com>
Hello Charles,
On Sun, 11 Mar 2018 15:17:39 -0700, charles.hardin at storagecraft.com
wrote:
> -DOCKER_CONTAINERD_VERSION = 9048e5e50717ea4497b757314bad98ea3763c145
> -DOCKER_CONTAINERD_SITE = $(call github,docker,containerd,$(DOCKER_CONTAINERD_VERSION))
> +DOCKER_CONTAINERD_VERSION = v1.0.1
> +DOCKET_CONTAINERD_COMMIT = 9b55aab90508bd389d7654c4baf173a981477d55
Do we still need the DOCKET_CONTAINERD_COMMIT variable ?
> +DOCKER_CONTAINERD_SITE = $(call github,containerd,containerd,$(DOCKER_CONTAINERD_VERSION))
> DOCKER_CONTAINERD_LICENSE = Apache-2.0
> DOCKER_CONTAINERD_LICENSE_FILES = LICENSE.code
>
> @@ -18,15 +19,25 @@ DOCKER_CONTAINERD_MAKE_ENV = $(HOST_GO_TARGET_ENV) \
> GOPATH="$(DOCKER_CONTAINERD_GOPATH)"
>
> DOCKER_CONTAINERD_GLDFLAGS = \
> - -X github.com/docker/containerd.GitCommit=$(DOCKER_CONTAINERD_VERSION)
> + -X github.com/containerd/containerd.GitCommit=$(DOCKER_CONTAINERD_VERSION)
> +
> +DOCKER_CONTAINERD_BUILD_TAGS =
> +
> +# XXX - Reusing the "docker-engine" config for now
What does that mean ?
> +ifeq ($(BR2_PACKAGE_DOCKER_ENGINE_DRIVER_BTRFS),y)
> +DOCKER_CONTAINERD_DEPENDENCIES += btrfs-progs
> +else
> +DOCKER_CONTAINERD_BUILD_TAGS = no_btrfs
> +endif
> +
>
> ifeq ($(BR2_STATIC_LIBS),y)
> DOCKER_CONTAINERD_GLDFLAGS += -extldflags '-static'
> endif
>
> define DOCKER_CONTAINERD_CONFIGURE_CMDS
> - mkdir -p $(DOCKER_CONTAINERD_GOPATH)/src/github.com/docker
> - ln -s $(@D) $(DOCKER_CONTAINERD_GOPATH)/src/github.com/docker/containerd
> + mkdir -p $(DOCKER_CONTAINERD_GOPATH)/src/github.com/containerd
> + ln -s $(@D) $(DOCKER_CONTAINERD_GOPATH)/src/github.com/containerd/containerd
> mkdir -p $(DOCKER_CONTAINERD_GOPATH)/src/github.com/opencontainers
> ln -s $(RUNC_SRCDIR) $(DOCKER_CONTAINERD_GOPATH)/src/github.com/opencontainers/runc
> endef
> @@ -34,7 +45,9 @@ endef
> define DOCKER_CONTAINERD_BUILD_CMDS
> $(foreach d,ctr containerd containerd-shim,\
> cd $(@D); $(DOCKER_CONTAINERD_MAKE_ENV) $(HOST_DIR)/bin/go build \
> - -v -o $(@D)/bin/$(d) -ldflags "$(DOCKER_CONTAINERD_GLDFLAGS)" ./$(d)$(sep))
> + -tags "$(DOCKER_CONTAINERD_BUILD_TAGS)" \
> + -v -o $(@D)/bin/$(d) -ldflags "$(DOCKER_CONTAINERD_GLDFLAGS)" \
> + github.com/containerd/containerd/cmd/$(d)$(sep))
> endef
All of this no longer applies really well on the current
docker-containerd, which has been converted to the golang-package
infrastructure.
Could you respin your patch series, rebased on master, where
docker-containerd, docker-engine and runc have been converted to the
golang-package infrastructure ?
Thanks a lot!
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-03-31 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 22:17 [Buildroot] [PATCH v2 1/3] docker-containerd: bump to version 1.0.1 charles.hardin at storagecraft.com
2018-03-11 22:17 ` [Buildroot] [PATCH v2 2/3] docker-engine: bump to version 17.12.1-ce charles.hardin at storagecraft.com
2018-03-11 22:17 ` [Buildroot] [PATCH v2 3/3] runc: bump to v1.0.0-rc5 charles.hardin at storagecraft.com
2018-03-31 18:51 ` Thomas Petazzoni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180331205138.6568882d@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.