Actions
Bug #18843
closedbump containerd
Story points:
-
Release:
Release relationship:
Auto
Updated by Ward Vandewege almost 3 years ago
- Status changed from New to In Progress
Updated by Ward Vandewege almost 3 years ago
ready for review at 1788b8971976780fdaba83a835bcf790ecd64c0f on branch 18843-bump-containerd
Updated by Tom Clegg almost 3 years ago
LGTM
Related notes:
containerd v1.2.3 // indirect
in go.mod means we import a non-module package (i.e., a package that does not have go.mod) which imports containerd, which means we have to decide which version to use, and we have decided to use v1.2.3.
go mod why -m
shows the path from go.mod to an indirect dependency:
$ go mod why -m github.com/containerd/containerd # github.com/containerd/containerd git.arvados.org/arvados.git/cmd/arvados-package github.com/docker/docker/client github.com/docker/docker/errdefs github.com/containerd/containerd/errdefs
We are using a prerelease version of docker/docker (aka moby/moby), possibly because they have/had a small versioning dumpster fire
$ go mod graph | grep github.com/docker/docker git.arvados.org/arvados.git github.com/docker/docker@v17.12.0-ce-rc1.0.20210128214336-420b1d36250f+incompatible
Currently go get github.com/docker/docker
would upgrade this to v20.10.12+incompatible
Updated by Ward Vandewege almost 3 years ago
- % Done changed from 0 to 100
- Status changed from In Progress to Resolved
Applied in changeset arvados-private:commit:arvados|242b29b301e9817c70dd29ef7255872cf5d13aa4.
Actions