Skip to content
This repository has been archived by the owner on Oct 13, 2023. It is now read-only.

Conversation

thaJeztah
Copy link
Member

@thaJeztah thaJeztah commented Oct 18, 2018

backport of moby#38019 for 18.09

PR is based on top of #85 to get a clean cherry-pick; only the last commit is new

The `devicemapper` storage driver is deprecated in favor of `overlay2`, and will
be removed in a future release. Users of the `devicemapper` storage driver are
recommended to migrate to a different storage driver, such as `overlay2`, which
is now the default storage driver.

The `devicemapper` storage driver facilitates running Docker on older (3.x) kernels
that have no support for other storage drivers (such as overlay2, or AUFS).

Now that support for `overlay2` is added to all supported distros (as they are
either on kernel 4.x, or have support for multiple lowerdirs backported), there
is no reason to continue maintenance of the `devicemapper` storage driver.

Signed-off-by: Sebastiaan van Stijn <[email protected]>
(cherry picked from commit 06fcabb)
Signed-off-by: Sebastiaan van Stijn <[email protected]>
The `overlay` storage driver is deprecated in favor of the `overlay2` storage
driver, which has all the benefits of `overlay`, without its limitations (excessive
inode consumption). The legacy `overlay` storage driver will be removed in a future
release. Users of the `overlay` storage driver should migrate to the `overlay2`
storage driver.

The legacy `overlay` storage driver allowed using overlayFS-backed filesystems
on pre 4.x kernels. Now that all supported distributions are able to run `overlay2`
(as they are either on kernel 4.x, or have support for multiple lowerdirs
backported), there is no reason to keep maintaining the `overlay` storage driver.

Signed-off-by: Sebastiaan van Stijn <[email protected]>
(cherry picked from commit 31be4e0)
Signed-off-by: Sebastiaan van Stijn <[email protected]>
Discourage users from using deprecated storage-drivers
by skipping them when automatically selecting a storage-
driver.

This change does not affect existing installations, because
existing state will take precedence.

Users can still use deprecated drivers by manually configuring
the daemon to use a specific driver.

Signed-off-by: Sebastiaan van Stijn <[email protected]>
(cherry picked from commit b72db8b)
@thaJeztah thaJeztah added this to the 18.09.0 milestone Oct 18, 2018
@thaJeztah
Copy link
Member Author

ping @andrewhsu @mavenugo @mataneja

@thaJeztah
Copy link
Member Author

Windows failure is not related;

13:36:06 --- FAIL: TestJSONFileLoggerWithOpts (0.01s)
13:36:06 	jsonfilelog_test.go:187: open C:\Users\ContainerAdministrator\AppData\Local\Temp\docker-logger-273827513\container.log.1: The process cannot access the file because it is being used by another process.
13:36:06 FAIL
13:36:06 coverage: 62.1% of statements
13:36:06 FAIL	github.com/docker/docker/daemon/logger/jsonfilelog	0.271s

@mavenugo
Copy link

@thaJeztah the recommendation for the 18.09 release is to just set the deprecation notice and not to make any logic change (including automatic detection). IDK if the proposed change will satisfy that recommendation.

@thaJeztah
Copy link
Member Author

#85 (the PR that this one is built on top off) only adds the deprecation warnings (in logs, and in the output of docker info)

@thaJeztah thaJeztah modified the milestones: 18.09.0, 18.09.1 Nov 8, 2018
@thaJeztah thaJeztah modified the milestones: 18.09.1, 18.09.2 Jan 24, 2019
@thaJeztah thaJeztah modified the milestones: 18.09.2, 18.09.3 Feb 11, 2019
@thaJeztah
Copy link
Member Author

Closing this one for now

@thaJeztah thaJeztah closed this Feb 25, 2019
@thaJeztah thaJeztah deleted the 18.09_backport_skip_deprecated_drivers_in_autoselect branch March 24, 2022 23:33
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants