From: xtraeme <xtraeme@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Latest docker update causes issues on btrfs
Date: Mon, 17 Feb 2020 06:10:08 +0100 [thread overview]
Message-ID: <20200217051008.p9dYG8UTiozuqgSF4P4aLwu-zNv638n9Z8QecKs_U7o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19202@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
Closed issue by kernle32dll on void-packages repository
https://github.com/void-linux/void-packages/issues/19202
Description:
The commit https://github.com/void-linux/void-packages/commit/ec709f9e09458bb1707a4136c1d4635ca11b0e7a did not only update docker, but enforced the `overlay2` storage driver. While this is a fine default, it can actually break docker on `btrfs` file systems.
From the [Dockerd documentation](https://docs.docker.com/engine/reference/commandline/dockerd/#daemon-storage-driver):
> Note: Both overlay and overlay2 are currently unsupported on btrfs or any Copy on Write filesystem and should only be used over ext4 partitions.
Even if not breaking, its an un-intuitive change, if you don't happen to use `overlay2` previously. It took me a good while to understand why all of my images and volumes were gone - which was due to the change of the storage driver.
Its easy to fix locally - just remove the `storage-driver` line from `/etc/docker/daemon.json`. But this should be removed in the package, too - IMO.
next prev parent reply other threads:[~2020-02-17 5:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 11:42 [ISSUE] " kernle32dll
2020-02-17 3:08 ` D-Nice
2020-02-17 4:33 ` xtraeme
2020-02-17 5:10 ` xtraeme [this message]
2020-02-17 13:27 ` kernle32dll
2020-02-17 13:34 ` xtraeme
2020-02-17 13:37 ` kernle32dll
2020-02-17 13:38 ` kernle32dll
2020-02-17 13:42 ` xtraeme
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=20200217051008.p9dYG8UTiozuqgSF4P4aLwu-zNv638n9Z8QecKs_U7o@z \
--to=xtraeme@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).