Github messages for voidlinux
 help / color / mirror / Atom feed
From: tetsumaki <tetsumaki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: docker: Use OPTS="-s=overlay2" in case OPTS is not set
Date: Wed, 25 Mar 2020 19:58:12 +0100	[thread overview]
Message-ID: <20200325185812.3G-gPrTnp4dLX-bMRUOScvRNXGxtaYEdxUHjPuAz2dk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19374@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]

New comment by tetsumaki on void-packages repository

https://github.com/void-linux/void-packages/pull/19374#issuecomment-604020277

Comment:
Hello, this merge broke my docker on my dedicated server but not in my computer.

I have commented this line for fix my problem:
[ -n "$OPTS" ] || OPTS="-s=overlay2"

Error:

	2020-03-25T18:49:47.56992 daemon.info: Mar 25 19:49:47 docker: time="2020-03-25T19:49:47.569432179+01:00" level=warning msg="could not use snapshotter overlayfs in metadata plugin" error="/var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.overlayfs does not support d_type. If the backing filesystem is xfs, please reformat with ftype=1 to enable d_type support"

For information, f_type is 0 on my dedicated server:

	$ xfs_info /
	meta-data=/dev/mapper/luks-a7768716-3cd2-4a79-ae9e-a0b829b3d0ac isize=256    agcount=4, agsize=122051776 blks
			 =                       sectsz=512   attr=2, projid32bit=1
			 =                       crc=0        finobt=0, sparse=0, rmapbt=0
			 =                       reflink=0
	data     =                       bsize=4096   blocks=488207104, imaxpct=5
			 =                       sunit=0      swidth=0 blks
	naming   =version 2              bsize=4096   ascii-ci=0, ftype=0
	log      =internal log           bsize=4096   blocks=238382, version=2
			 =                       sectsz=512   sunit=0 blks, lazy-count=1
	realtime =none                   extsz=4096   blocks=0, rtextents=0

I can't format at the moment (mkfs.xfs -n ftype=1)

  parent reply	other threads:[~2020-03-25 18:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19374@inbox.vuxu.org>
2020-03-25 18:48 ` tetsumaki
2020-03-25 18:50 ` tetsumaki
2020-03-25 18:50 ` tetsumaki
2020-03-25 18:51 ` tetsumaki
2020-03-25 18:58 ` tetsumaki [this message]
2020-03-25 19:00 ` tetsumaki
2020-03-25 19:40 ` Anachron
2020-04-24 15:27 ` Piraty
2020-04-24 15:30 ` xtraeme
2020-04-24 21:13 ` Piraty
2020-04-24 21:14 ` Piraty
2020-05-01  0:18 ` sgn
2020-05-01 23:29 ` Piraty

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=20200325185812.3G-gPrTnp4dLX-bMRUOScvRNXGxtaYEdxUHjPuAz2dk@z \
    --to=tetsumaki@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).