tests/update: Add test for docker btrfs storage driver #475
Conversation
Temporary commit to use flatcar/mantle#475 for testing which ships the btrfs backwards compatibility test. Signed-off-by: Thilo Fromm <[email protected]>
This change adds an update test for instances using the docker btrfs storage driver. This storage driver was deprecated in docker release 23 and will be removed in a future release. Docker 23 and above support backwards compatibility if BTRFS storage exists and is populated. Signed-off-by: Thilo Fromm <[email protected]>
t-lo
force-pushed
the
t-lo/add-docker-btrfs-update-compat-test
branch
from
ab96781
to
7bf1323
Compare
| // This test verifies preservation of storage driver "btrfs" for docker. | ||
| // Docker releases before v23 defaulted to btrfs if the docker can only run if the update payload to test is given. | ||
| // The image passed must also be a release lower than or equal to 3760.0.0 | ||
| // because newer versions ship docker 24. | ||
| EndVersion: semver.Version{Major: 3760}, |
There was a problem hiding this comment.
I'm wondering if we should have a separate test that boots the old release (but new enough to be with docker 24) with a config that forces btrfs storage driver, pulls an image and creates a container, so the storage is used. Then drops the config and updates the OS to see if btrfs driver is still used. Similar to this test, but would make sure nothing breaks after a sequence of [old OS with old docker using btrfs storage] -> [newer OS with new docker using inherited btrfs storage] -> [shiny new OS with new docker still using the inherited btrfs storage] (your test checks the first transition, another would test the second transition). Such test would probably need to be minimum 3760.0.0. Or maybe we could drop the EndVersion and make this test work regardless of the docker version.
There was a problem hiding this comment.
I don't think an intermediate update to Docker 24 would make any difference since I don't think docker stores any configuration data, but instead auto-detects whether to use btrfs. The "newest" Docker would need to auto-detect the need to use the btrfs storage driver either way, no matter if it was upgraded from docker 20 or docker 24.
This change adds an update test for instances using the docker btrfs storage driver. This storage driver was deprecated in docker release 23 and will be removed in a future release.
Docker 23 and above support backwards compatibility if BTRFS storage exists and is populated.
This test verifies that instances with btrfs storage don't break on update.