Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Unpin docker and move to latest version #407

Closed
jodh-intel opened this issue Mar 21, 2019 · 4 comments
Closed

Unpin docker and move to latest version #407

jodh-intel opened this issue Mar 21, 2019 · 4 comments
Assignees

Comments

@jodh-intel
Copy link
Contributor

#374 pinned docker to the last known good version of docker that supported device-mapper. However, as shown in #373 (comment), docker has released a number of new versions.

Undo the pinning and switch strategy to simply make a note to users that if they wish to use a feature such as device-mapper, they will need to look at alternative configurations.

@jodh-intel jodh-intel self-assigned this Mar 21, 2019
@ganeshmaharaj
Copy link

The two alternate device mapper / lvm solutions for containerd are.

  1. https://github.com/firecracker-microvm/firecracker-containerd/tree/master/snapshotter/cmd/devmapper
  2. https://github.com/ganeshmaharaj/lvm-snapshotter

Both of them are for containerd. devicemapper will currently pending merging into containerd upstream repo via containerd/containerd#3022.
crio supports a similar LVM /devicemapper snapshotter.

It would be nice to tell the user that if they wish to use a block backend for docker they can run the stand-alone versions of the snapshotter until the backend lands after which they can use devicemapper / lvm as their backends.

jodh-intel added a commit to jodh-intel/documentation that referenced this issue Mar 22, 2019
Don't force Docker to be kept at version 18.06 (to ensure devicemapper
is available). This feature won't be re-added by Docker and remaining on
an old version of Docker is not good from a security perspective.

Replace the pinning with a note pointing users at an issue which
provides details of alternatives to devicemapper.

Fixes kata-containers#407.

Signed-off-by: James O. D. Hunt <[email protected]>
@jodh-intel
Copy link
Contributor Author

Thanks @ganeshmaharaj - I've added a note to all the docker install guides on #409 pointing back at this issue so users can find details on alternatives.

@ganeshmaharaj
Copy link

A latest update from docker engineering team. They are currently working to make docker use containerd to as the default storage handler. Refer to comment docker/for-linux#452 (comment). Hopefully the two changes referenced there will land soon. We will keep an eye on those and update once they land in mainstream docker.

@zeigerpuppy
Copy link
Contributor

looks like it's fixed in docker-ce 19.03.1 and upwards. I haven't tested yet on my Devuan box...

docker/for-linux#452 (comment)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants