Date: Mon, 04 Sep 2023 19:01:48 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 273569] sysutils/docker [Patch] PAX cannot encode Devminor Message-ID: <bug-273569-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273569 Bug ID: 273569 Summary: sysutils/docker [Patch] PAX cannot encode Devminor Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: joneum@FreeBSD.org Reporter: adam.labuznik@gmail.com Assignee: joneum@FreeBSD.org Flags: maintainer-feedback?(joneum@FreeBSD.org) Created attachment 244637 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D244637&action= =3Dedit Two concatenated patches made with makepatch Currently, the docker port is completely unusable on ZFS, because the docker client mandates the use of the PAX tar format, which causes the following issue: ERRO[0000] Can't add file /usr/home/hackerman/Desktop/Docker/i4industry_v2/= src to tar: archive/tar: cannot encode header: Format specifies PAX; and PAX ca= nnot encode Devminor=3D4294902015 I wasn't able to replicate this issue in my own GO tar utility, but switchi= ng to ext solved it. A rather naive solution is just to replace it with FormatGNU like in the pa= tch (it seems to work, based on a quick testing). I assume most FreeBSD people = use ZFS, in which case any patch is better than none. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273569-7788>