From: Piraty <Piraty@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: docker: Fix runit service
Date: Tue, 05 May 2020 11:07:34 +0200 [thread overview]
Message-ID: <20200505090734.zEalI2bndF6k2ELtXD3HW3ge5Zo_gKJ_mTVYvcRbO-U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21254@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
New comment by Piraty on void-packages repository
https://github.com/void-linux/void-packages/pull/21254#issuecomment-623942555
Comment:
because this came up in IRC again, here is my (naive) explanation.
### Explanation
- #19374 was clearly a user configuration issue. The user should have cleaned up like the error message indicates.
- by adding `-s=overlay2` to the service run file this switched (probably quite a few) users that were using a different storage driver before (such as devicemapper, probably old docker installs that defaulted to sth else than overlay2) to overlay2 storage driver
- now by my revert (7e4ec0a6a9ecb96b0f8a8364e19f465f9dca29ee) those users end up with two configured storage drivers (their old one and overlay2). thus docker daemon fail demanding to explicitly set the one to use clean up `/var/lib/docker` (just like the original author of #19374)
### how to fix
if you are affected,
- either clean up `/var/lib/docker` (remove all sotage driver dirs what are oboslete). might require migration of existing containers
- or put `OPTS="-s=STORAGEDRIVER"` (for example devimapper if that was used before) in `/etc/sv/docker/conf`
prev parent reply other threads:[~2020-05-05 9:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 20:09 [PR PATCH] " beanpole135
2020-04-22 20:14 ` Piraty
2020-04-22 20:18 ` beanpole135
2020-04-22 23:02 ` Piraty
2020-04-22 23:02 ` [PR PATCH] [Closed]: " Piraty
2020-04-22 23:38 ` beanpole135
2020-04-24 15:22 ` Piraty
2020-04-24 15:25 ` Piraty
2020-04-25 9:16 ` Piraty
2020-04-25 9:18 ` Piraty
2020-04-25 9:18 ` Piraty
2020-04-27 12:45 ` beanpole135
2020-05-01 23:27 ` [PR PATCH] [Closed]: " Piraty
2020-05-05 9:07 ` Piraty [this message]
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=20200505090734.zEalI2bndF6k2ELtXD3HW3ge5Zo_gKJ_mTVYvcRbO-U@z \
--to=piraty@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).